Hi Drew- You're getting a 420 status back from sipx in response to the INVITE resulting from the inbound PSTN call. A 420 is "bad extension". Scott (Lawrence) or others here may be able to expand on exactly when sipx will return a 420 but I presume it's a case of nothing registered for that extension.
See below for specifics: > This is from the syslog of the 4404. Nothing jumped out to > me, but I am new to sipx The "INVITE" is the start of the relay of the inbound POTS call to the SIP/IP side. It looks like you've got your 4104 configured to forward the inbound call to extension [email protected]. > S_LOG: [00:0B:82:1A:BD:00][000][9660000311A][01000108] 866 sip.c Sess: > 6 INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP > 192.168.1.4:5060;branch=z9hG4bK03e432e00e170fc5 From: > "unknown"<sip:[email protected]>;tag=b6870ae260632435 > To: <sip:[email protected]> Contact: > <sip:192.168.1.4:5060> Supported: replaces, timer, path Call-ID: > [email protected] CSeq: 2123 INVITE User-Agent: > Grandstream GXW4104 (HW 1.1, Ch:6) 1.0.1.8 Proxy-Require: 100 > Max-Forwards: 70 Allow: > INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK > Content-Type: application/sdp Content-Length: 308 v=0 o=system > 8006 8000 IN IP4 192.168.1.4 s=SIP Call c=IN IP4 > 192.168.1.4 t=0 0 m=audio 5028 RTP/AVP 0 8 4 18 3 101 > a=sendrecv a=rtpmap:0 PCMU/8000 > a=rtpmap:8 PCMA/8000 a=rtpmap:4 G723/8000 a=rtpmap:18 G729/8000 > a=rtpmap:3 GSM/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-11 > 2/18/2009 12:34:12 PM 192.168.1.4 <14> Feb 18 12:34:12 192.168.1.4 > S_LOG: [00:0B:82:1A:BD:00][000][9660000311A][01000108] 882 > sip.c INVITE > From="unknown"<sip:[email protected]>;tag=b6870 > ae260632435 > To=<sip:[email protected]> > 2/18/2009 12:34:12 PM 192.168.1.4 <14> Feb 18 12:34:12 192.168.1.4 Here's a SIP 100 status code (from sipx) indicating it's "trying"... > S_LOG: [00:0B:82:1A:BD:00][000][9660000311A][01000108] 1494 > sip.c Received SIP message: 100 Acc:0 > 2/18/2009 12:34:12 PM 192.168.1.4 <14> Feb 18 12:34:12 192.168.1.4 Here's the SIP 420 status code (from sipx) indicating an INVITE to a "bad" extension. > S_LOG: [00:0B:82:1A:BD:00][000][9660000311A][01000108] 1494 > sip.c Received SIP message: 420 Acc:0 > 2/18/2009 12:34:12 PM 192.168.1.4 <14> Feb 18 12:34:12 192.168.1.4 Everything afterwards unravels as things unwind... > S_LOG: [00:0B:82:1A:BD:00][000][9660000311A][01000108] 697 sip.c Sess: > 6 Send SIP message: 3 To 192.168.1.2:5060 > 2/18/2009 12:34:12 PM 192.168.1.4 <15> Feb 18 12:34:12 192.168.1.4 > S_LOG: [00:0B:82:1A:BD:00][000][9660000311A][01000108] 866 sip.c Sess: > 6 ACK sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP > 192.168.1.4:5060;branch=z9hG4bK03e432e00e170fc5 From: > "unknown"<sip:[email protected]>;tag=b6870ae260632435 > To: <sip:[email protected]>;tag=4d9b0fb9 Contact: > <sip:[email protected]:5060> Call-ID: [email protected] > CSeq: 2123 ACK User-Agent: Grandstream GXW4104 (HW 1.1, Ch:6) > 1.0.1.8 Max-Forwards: 70 Allow: > INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK > Content-Length: 0 So, from sipx's perspective, the extension [email protected] is invalid. I would verify sipx knows about this extension (ie you can make internal calls to it, etc). Hope this helps- sdm _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
