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

But, what is really surprising is that not only did the call fail, but
sipXtapi hadn't sent a single packet according to Wireshark! Not even a DNS
query. I've attached the PlaceCall.log file generated by the test (and a
capture of the console output in PlaceCall.txt). 

So far, I haven't figured out where things are going wrong. I did find a bug
in the DNS code, but it turned out to be unrelated. I'll send a patch fixing
it in a separate thread.

Stephen C. Steel
C:\test\sipX_new>PlaceCall -i sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED]
.com
Input Devices: 1
        #0: Creative Sound Blaster PCI
Output Devices: 1
        #0: Creative Sound Blaster PCI
<-> Attempt 1 of 1
<-> Placing call to "sip:[EMAIL PROTECTED]" as "sip:[EMAIL PROTECTED]"
<-> Username: (null), passwd: (null), realm: (null) (all required for auth)
EVENT_CATEGORY_LINESTATE::PROVISIONED::PROVISIONED_NORMAL
EVENT_CATEGORY_CALLSTATE::DIALTONE::CAUSE_NORMAL
    hCall=1, hAssociatedCall=0
<-> Type LOCAL, Interface: eth0, Ip 209.146.224.76, Port 5060
<-> Type LOCAL, Interface: eth0, Ip 209.146.224.76, Port 5060
EVENT_CATEGORY_CALLSTATE::DISCONNECTED::CAUSE_BADADDRESS
    hCall=1, hAssociatedCall=0
PlaceCall: Unable to complete call
<-> Shutting down Call
EVENT_CATEGORY_CALLSTATE::DESTROYED::CAUSE_NORMAL
    hCall=1, hAssociatedCall=0

Attachment: PlaceCall.log
Description: Binary data

_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to