[OpenSIPS-Users] codec_exists and its cousins on 1.6.4

Jeff Pyle jpyle at fidelityvoice.com
Tue Apr 12 23:33:41 CEST 2011


Never mind!  Turned out to be an extra \r\n in an append_rf, set once on the variable that the function used, and a second time on the function itself.  As you were…

I love it when it's easy.

Strange, though, the same config on 1.6.2 didn't cause the carriers to barf on it.


- Jeff

From: Jeff Pyle <jpyle at fidelityvoice.com<mailto:jpyle at fidelityvoice.com>>
Reply-To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Date: Tue, 12 Apr 2011 17:12:37 -0400
To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: [OpenSIPS-Users] codec_exists and its cousins on 1.6.4

Hey list,

Has anyone heard of a problem where codec_exists, codec_delete_except_re, codec_move_up, or codec_delete causes an extra blank line to appear between the headers and the SDP in 1.6.4?  I updated from 1.6.2 and I have this now.  Upstream gateways bounce the invites with 400 Bad Request.

I haven't been able to determine exactly which function causes the problem.  I thought I'd ask before I rip apart an otherwise functional config.


- Jeff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20110412/8e564da2/attachment.htm>


More information about the Users mailing list