Thanks for the reply!

Will this really help though? From what I understand of the change that breaks 
the compatibility, it will always send this header in the "200 OK" message (my 
problem is incoming calls to FS). The fix you're describing, isn't it when 
calling from FS to the other end? This way it works either way, it's just when 
the PBX gets this in the 200 OK message with this header that it stops working.

/Peter

-----Ursprungligt meddelande-----
Från: [email protected] 
[mailto:[email protected]] För Kristian Kielhofner
Skickat: den 1 juni 2009 15:20
Till: [email protected]
Ämne: [SPAM] - Re: [Freeswitch-users] Something broken in RTP in latest trunk 
(r13502)?

Peter,

  Ouch.  Your PBX is broken.  It shouldn't do that.

  Luckily FreeSWITCH provides a way to select RPID/PAI/none:

http://wiki.freeswitch.org/wiki/Channel_Variables#SDP_Manipulation

On Mon, Jun 1, 2009 at 5:57 AM, Peter Olsson
<[email protected]> wrote:
> Here is an update for this issue (SFSIP-149). I've raised a jira case for 
> this. It was not a RTP problem, the problem is caused by the new 
> "P-Asserted-Identity:"-header added in r13492. This causes my connected PBX 
> not to ACK/accept the 200 OK sent from FS, and the call is never answered. FS 
> still thinks it's answered though, and starts to send RTP data to the other 
> end.
>
> /Peter
>

-- 
Kristian Kielhofner
http://www.astlinux.org
http://blog.krisk.org
http://www.star2star.com
http://www.submityoursip.com
http://www.voalte.com

_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

!DSPAM:4a23d69e32932135138353!


_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

Reply via email to