Re: [OpenSBC] Problem with Remote-Party-ID

[OpenSBC F. <ope...@op...>]

Not sure I got you correctly so feel free to correct me if I am wrong.  Your SoftSwitch complains about CRLF header termination?  If so then it's not compliant to the specs.  As per 3261 ABNF for SIP Messages

---
      generic-message  =  start-line
                             *message-header
                             CRLF
                             [ message-body ]
         start-line       =  Request-Line / Status-Line

   The start-line, each message-header line, and the empty line MUST be
   terminated by a carriage-return line-feed sequence (CRLF).  Note that
   the empty line MUST be present even if the message-body is not.
---


What terminating character is your SoftSwitch expecting?


Joegen

> {quote:title=smitrob wrote:}{quote}
> 
> I am having a problem with the content in the remote party ID. For a 180 ringing message my system sends the following for Remote-Party-ID to the OpenSBC
> 
> bq. {color:#0000ff}Remote-Party-ID:"Test 2"<sip:3035550996@198.133.219.25;user=phone>;screen=yes;party=called;privacy=off;id-type=subscriber{color}
> 
> However the OpenSBC sends the following.
> 
> bq. {color:#0000ff}Remote-Party-ID:"360 Test 2"<sip:3033300996@64.15.100.52;user=phone>;screen=yes;party=called;privacy=off;id-type=subscriber{color}{color:#ff0000}\r\n{color}
> 
> This is according to a tshark trace on the SBC. The same is true for all messages sent in the Message Body (i.e. RPID-Privacy, Content-Length)
> 
> 
> Is there a reason for this?
> 
> 
> I am assuming that the \r\n is a Carrage Return & Line Feed is this correct?  Is there a way to change this? The SBC that I am sending to see this as a malformed message.
> 
> 
> This is running on a Linux System (CentOS) and is running OpenSBC v1.1.5-36
>