[OpenSIPS-Users] 183 with SDP causes me grief

[Bogdan-Andrei Iancu]

Hi Doug,

actually you can do it with pure scripting.

For on_reply route, when receiving the 183, you can cancel that branch 
with the t_cancel_branch() function:
       http://www.opensips.org/html/docs/modules/1.6.x/tm.html#id294223

Cancelling the branch will end up with a 487 negative reply in failure 
route -> from there you can continue the routing to a new destination

Regards,
Bogdan

PS: never tried, but I hope it will work ;)

Doug wrote:
> Hi All,
>
> I am hoping you can shed some light into a difficult spot I'm having.
>
> Currently, my one supplier is sending back Early Media (183 + SDP) when 
> there is a problem (such as number not available), instead of a SIP 
> response code. This in turn causes grief, as my system passes this 
> session onto the client.
>
> I wanted to know if its possible in the event of receiving a 183 from 
> this specific supplier, to reply with a CANCEL and then engage a new 
> route, or to send a 50x back to the client.
>
> Based on the above, I am guessing I need to use the b2bua module, 
> however, I don't see a way to identify a reply from the server id with a 
> 183:
>
> I had something like this in mind:
>
> <rules>
> <reply>
> <183>
> <rule id="1">
> <condition>
> <state>1</state>
> <sender>
> <type>server</type>
> <id>server1</id>
> </sender>
> </condition>
> <action>
> <send_reply>
> <code>CANCEL</code>
> <reason></reason>
> </send_reply>
>              ...
> </action>
> </rule>
> </183>
> </reply>
> </rules>
>
>
> Any suggestions if this is possible?
>
> Many thanks
> Doug
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>   


-- 
Bogdan-Andrei Iancu
OpenSIPS Bootcamp
15 - 19 November 2010, Edison, New Jersey, USA
www.voice-system.ro