Doug, I had a customer with the same issue on another provider. They wrote some creative detection by looking at the c= contact IP address in the SDP. If it was one of the media servers of the provider, they knew they were getting a recording and not real ringback. Otherwise, it was a PSTN gateway or other IP endpoint.
In this case, this provider did not proxy media through an SBC so it wasn't too difficult. I don't know in your case if that is true or not. - Jeff On Oct 29, 2010, at 10:14 AM, 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 > [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
