[Sipp-users] Possible SIPP Bug (SIP syntax error (Testing SBC))

Dana Jaff Fri, 05 Mar 2010 15:48:29 -0800

Hi,

As a follow up on the issue listed below, I had received many responses (with Thanks) to add a carriage return and line feed (CR/LF) after the last line (#19) that is causing the parsing error sent back from the SBC (400 Bad Request).

When checking my uac XML script, it did have a carriage return and line feed. When contacting and testing with the SBC vendor concerned, we found out that although my XML script contained (CR/LF), SIPP was sending out the initial INVITE request without (CR/LF). This was proven from the Wireshark captures of the initial INVITE. The Hex code for the last line (#19) did not have the code for (CR/LF) which is (0d 0a).

I had tested this same uac script with another SBC vendor and another SIP stack, but did not receive a (400 Bad Request) due to the missing (CR/LF) sent by SIPP.

Conclusion: Some parsers are stricter and more sensitive than others, therefore causing parsing errors when there is no CR/LF after the last line.

Issue: Although the XML script contains CR/LF after the last line, why is SIPP sending out an INVITE that has no CR/LF after the last line, causing parsing errors with some strict parsers ?? Is this an issue just with Linux based SIPP versions or has this been noted on other platforms??

Note: I had also tried adding two line feeds after line #19 but this did not work. I also deleted the line feed that I currently have and added a new one, but this did not work either.

If this is a bug then I would like to bring it to the attention of the SIPP development group. If anyone has any ideas on resloving this, then your feedback is appreciated.

Thanks

Dana Jaff

Systems Engineer Lead
CSC

15000 Conference Center Drive, Chantilly VA 20151
C : 571-338-6315 | O : 703-818-4135 | dj...@csc.com | www.csc.com

From: Dana Jaff [mailto:dj...@csc.com]
Sent: Thursday, February 25, 2010 10:31 PM
To: sipp-users@lists.sourceforge.net
Subject: [Sipp-users] SIP syntax error (Testing SBC)

I am using sipp to test an SBC (Session Border Controler (B2BUA)). The scenario is UAC calls UAS through SBC. The (Invite) sent from UAC to SBC is rejected with a 400 (Bad Request). the 400 message contains (cause=SIP Syntax error). When viewing the debug logs of the SBC, I see an INVITE parsing error on line 19. Line 19 is the last line in the SDP

a=rtpmap:0 PCMU/8000

Does anyone have an idea why the SBC is genarating this parsing error. The INVITE sent from UAC to SBC has the following format:

      INVITE sip:+15711110...@[remote_ip] SIP/2.0
      From: +15712220001 <sip:+15712220...@[local_ip]:[local_port]>;tag=[pid]SIPpTag00[call_number]
      To: <sip:+15711110...@[remote_ip]>
      Call-ID: [call_id]
      CSeq: 1 INVITE
      Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
      Max-Forwards: 70
      Contact: <sip:+15712220...@[local_ip]:[local_port];transport=udp>
      Content-Type: application/sdp
      Content-Length: [len]

      v=0
      o=user1 53655765 2353687637 IN IP[local_ip_type] [local_ip]
      s=-
      c=IN IP[media_ip_type] [media_ip]
      t=0 0
      m=audio [media_port] RTP/AVP 0
      a=rtpmap:0 PCMU/8000

Your feedback is appreciated

Thanks

Dana Jaff

Systems Engineer Lead
CSC

15000 Conference Center Drive, Chantilly VA 20151
Enforcement Security & Intelligence | C : 571-338-6315 | O : 703-818-4135 | dj...@csc.com | www.csc.com

Dana Jaff
CSC

15000 Conference Center Drive, Chantilly VA 20151
Enforcement Security & Intelligence | O : 703-818-4135 | dj...@csc.com | www.csc.com

This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

[Sipp-users] Possible SIPP Bug (SIP syntax error (Testing SBC))

Reply via email to