NAT traversal

[Jérôme]

Hello

I'd like to use Cipango as SIP UA and looking for NAT traversal feature. Does Cipango provide any STUN support? Where can I get some information/example about Cipango and NAT traversal?

Thanks in advance

Jérôme

[Thomas]

Hello Jérôme,

We have actually started a proof-of-concept in this area. Would you be interested to test it in advance ?

Regards

> --
> You received this message because you are subscribed to the Google Groups "cipango-users" group.
> To post to this group, send email to cipang...@googlegroups.com.
> To unsubscribe from this group, send email to cipango-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cipango-users?hl=en.

[Jérôme]

Hi

I started to evaluate Cipango and other servers with NAT environment based. For now, I'm using Cipango as proxy/registrar and SIPP as UA for user agents (Alice and Bob). Both of Alice and Bob are behind they respective NAT. I hope to have time to use Cipango on UA side instead of SIPP.

If any work in progress around NAT topic, I'd like to get some information, feedback, conclusion... and would be pleased to contribute to Cipango :)

Thanks.

Jérôme

[Nicolas Trangosi]

Hello Jérôme,
I have set a prototype with STUN client at
    http://www.cipango.org/downloads/stun/

To test it, you need to extract cipango-distribution-2.1-SNAPSHOT.tar.gz and start cipango with the command
    java -jar start.jar --ini=start-cipango.ini etc\cipango-stun-client.xml

Cipango is packaged with the application ua-register. It sends a REGISTER and INVITE at startup with the contact header set with address and port retrived with STUN.

Note: the trace
2011-05-25 14:17:55.890:WARN::EXCEPTION
org.cipango.sip.SipException
        at org.cipango.sip.SipParser.parseNext(SipParser.java:237)
        at org.cipango.sip.SipParser.parse(SipParser.java:124)
        at org.cipango.server.bio.UdpConnector.accept(UdpConnector.java:124)
at startup is due to that two STUN requests are sent and when the second response comes back it is the SIP connector that handling the response and no more the STUN client.

Kind regards,
Nicolas