[OpenSIPS-Users] 183 with SDP causes me grief

[Brett Nemeroff]

Doug,
I had an issue with a carrier playing music in 183s instead of ringback.
This bit of code was useful for me:
http://www.opensips.org/Resources/DocsTutPerl183to180

It's possible with some tweaking it might suit your needs. THe question I'd
have is how do you know if the inband audio is valid or not (maybe it's
ringing properly in 183).

-Brett


On Fri, Oct 29, 2010 at 9:14 AM, Doug <doug at wd.co.za> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20101029/5ee58cbf/attachment.htm