Hi All, I have no idea how the SIP headers I pasted in my email got corrupted. Actual messages never had those nested Request URI, From and To header fields. I am attaching a small wireshark trace with the messages. When similar message is sent from a phone PBX responds with 100 Trying. Where as it sends 400 Bad Request for the soft phone. I have no idea what wrong here with my Invite. Once again thanks everyone for taking time on this.
CoolGoose. On Thu, May 14, 2009 at 5:26 AM, Brett Tate <[email protected]> wrote: > Adding " <sip%[email protected] <sip%[email protected]>>" to sip-uri > is causing it to be malformed. > > For instance, the non escaped space before the bracket within the > request-uri is malformed. > > > -----Original Message----- > > From: [email protected] [mailto:sip- > > [email protected]] On Behalf Of cool goose > > Sent: Wednesday, May 13, 2009 7:47 PM > > To: [email protected] > > Subject: [Sip-implementors] 400 Bad Request > > > > Hi Guys, > > > > I am trying to make a call from a soft phone to a physical phone and for > > some reason the PBX responds with 400 Bad Request for the Invite > generated > > by the soft phone. I have no idea whether the Invite violates any SIP > > ABNF. > > Below are the SIP messages both Invite and 400 Bad request. Any help > would > > be greatly appreciated. > > > > INVITE sip:[email protected] <sip%[email protected]> < > sip%[email protected] <sip%[email protected]>> SIP/2.0 > > Via: SIP/2.0/UDP 192.168.5.6:5060;rport;branch=z9hG4bK2f123c8 > > To: <sip:[email protected] <sip%[email protected]> < > sip%[email protected] <sip%[email protected]>>> > > From: "SipTool"<sip:[email protected] <sip%[email protected]> > > <sip%[email protected] <sip%[email protected]>>>;tag=4c75524c > > Call-ID: [email protected] > > Max-Forwards: 70 > > CSeq: 1 INVITE > > Allow: INFO,REFER,NOTIFY,INVITE,ACK,OPTIONS,BYE,CANCEL > > Contact: <sip:[email protected]:5060> > > User-Agent: V5/1.0.5 > > Accept: > > application/dtmf- > > relay,application/sdp,text/plain,message/sipfrag,application/sip > > Content-Type: application/sdp > > Supported: tdialog,replaces,norefersub,histinfo > > Content-Length: 259 > > > > v=0 > > o=ipr1E682261B6 9970982 9970982 IN IP4 192.168.5.6 > > s=- > > c=IN IP4 192.168.5.6 > > t=0 0 > > m=audio 8000 RTP/AVP 18 0 8 101 > > a=rtpmap:0 PCMU/8000 > > a=rtpmap:8 PCMA/8000 > > a=rtpmap:101 telephone-event/8000 > > a=ptime:20 > > a=fmtp:101 0-16 > > > > 400 Bad Request from the PBX. > > > > SIP/2.0 400 Bad Request > > Via: SIP/2.0/UDP 192.168.5.6:5060;rport;branch=z9hG4bK2f123c8 > > From: "SipTool"<sip:[email protected] <sip%[email protected]> > > <sip%[email protected] <sip%[email protected]>>>;tag=4c75524c > > To: <sip:[email protected] <sip%[email protected]> < > sip%[email protected] <sip%[email protected]>>>;tag=e3ef61ca19 > > Call-ID: [email protected] > > CSeq: 1 INVITE > > User-Agent: PBX 2.0 > > Content-Length: 0 > > > > > > Thanks in Advance for your time, > >
_______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
