Hi Nick. It could be bad formatted or other errors that I cannot fix, i.e. codec names and attributes that do not comply with the RFC. In the cases in which I can’t fix the message, I need to terminated the call.
From: [email protected] [mailto:[email protected]] On Behalf Of Nick Altmann Sent: quinta-feira, 7 de Março de 2013 15:48 To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] b2b terminate_call! Why just not to fix 200 OK? -- Nick 2013/3/7 Jorge Henrique Pinho <[email protected]<mailto:[email protected]>> Hi, I am using opensips with b2b module with topology hiding. I am trying to terminate a call when i receive the 200OK response to a Re-Invite. To accomplish this i am using the 'terminate_call' function defined in b2b_logic module. The dialog is establish and an user sends an in dialog Invite to renegotiate codecs, but the 200OK reply is mal formed. In consequence I need to terminate the call at this stage. To accomplish this I am using the terminate_call function present in b2b_logic module. When I receive the 200OK bad formatted message, I invoke the terminate_call function. The behavior of b2b is this : A ----------------- Opensips (B2B) ------------------------ B A Re-Invite --> | Re-Invite --> B A | 200 OK* <-- B *Bad formatted 200OK A BYE <-- | B A | BYE --> B A | ACK --> B A | BYE --> B It seems that b2b is sending a first BYE to B that was not supposed to. Can you help me fix this? Kind regards Jorge Pinho _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
