Drew- There's a setting called "Enable100rel" on the Profile1, Profile2, Profile2 configuration page of the GXW4104.
Mine is disabled (and always has been). Inbound calls through my 4104 do not have this "Proxy-Require" statement in the INVITE packet either. I think you probably want to set this option to "No" on whichever profile you're using in your 4104. Hope this helps- sdm > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Dale Worley > Sent: Wednesday, February 18, 2009 4:48 PM > To: Drew Buckman > Cc: [email protected] > Subject: Re: [sipx-users] Inbound Failed > > On Wed, 2009-02-18 at 12:39 -0500, Drew Buckman wrote: > > This is from the syslog of the 4404. Nothing jumped out to > me, but I > > am new to sipx > > > > > > #Detected date/Time Detected host Original syslog message > > 2/18/2009 12:34:10 PM 192.168.1.4 <15> Feb 18 > 12:34:10 192.168.1.4 > > S_LOG: [00:0B:82:1A:BD:00][000][9660000311A][01000108] > fxo_ctl.c 423 > > Port:0 DAA Enabling CID detection, Type: 4 0 > > It helps a great deal if you do not cut-and-paste log entries > into e-mail, but rather save them into text files and attach > them to e-mail. > Generally, cut-and-paste damages the format of log entries > greatly and makes them much harder to work with. > > In your case, as Stephen Miller pointed out, you're receiving > a 420 response from sipX. 420 means that the request > contained a Requires or Proxy-Requires header demanding that > the recipient support a particular extension, but that the > recipient did not support that extension. (For details of > this process, search for "Requires" in RFC 3261.) > > In your case, the log shows this request: > > 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 > > 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 > > You can see the line "Proxy-Require: 100". Unfortunately, > there is no defined extension named "100". It's possible > that the phone is demanding to use the extension "100rel" > (see RFC 3262), but that must be mentioned in a Require > header, not a Proxy-Require header. See the valid list of > "option-tags" (as they are called) at > http://www.iana.org/assignments/sip-parameters (search for > the header "Registry Name: Option Tags"). > > And in any case, a phone would rarely want to use Require, > but would rather use Supported, as that allows the call to be > accepted by a device that does not support the extension in question. > > You should talk to Grandstream support and ask why the phone > includes the demand that the phone support an extension which > does not exist. > Also check to see that the firmware on the phone is > up-to-date, as they may have corrected this problem already. > > Dale > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
