<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>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…</div><div><br></div><div>I love it when it's easy.</div><div><br></div><div>Strange, though, the same config on 1.6.2 didn't cause the carriers to barf on it.</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br><span style="font-weight:bold">Date: </span> Tue, 12 Apr 2011 17:12:37 -0400<br><span style="font-weight:bold">To: </span> OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br><span style="font-weight:bold">Subject: </span> [OpenSIPS-Users] codec_exists and its cousins on 1.6.4<br></div><div><br></div><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Hey list,</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div></div></div></span></body></html>