Stephen C. Steel wrote: > I've been having trouble getting sipXtapi to make outgoing connections from > behind a NAT router using STUN. To keep things simple, I been using the > PlaceCall example included as part of the sipXtapi project (built from the > sipXtapi branch, revision 9792) and trying to connect to the pingtel interop > server. > > Just as a baseline, I thought I'd test using a publicly routable IP address > so NAT and STUN wouldn't be a factor. I could then compare Wireshark > captures both with and without NAT. > > PlaceCall -i sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] > > (where xxx.xxx.xxx.xxx was the actual public IP address). The call failed > with the message: > EVENT_CATEGORY_CALLSTATE::DISCONNECTED::CAUSE_BADADDRESS >
For me, making calls behind NAT works (with wxCommunicator and my provider). However, STUN doesn't work for me right now, I'm seeing icmp port unreachable sent from STUN server. I will have to dig into this. Have a look at what happens in sipxcalllib when you try to connect the call in sipxtapi. Or place a breakpoint at every DISCONNECTED::CAUSE_BADADDRESS pair in sipxcalllib. Hopefully there arent too many. Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
