You can try it, but if they shove SST reinvites down your throat despite no indicated support for them from the client, or the client sends SST headers despite no indicated support from the carrier, there are deeper-seated fundamental issues here. -- Sent from my BlackBerry. Please excuse errors and brevity.
Hi Alex Ok, not the 200 ok from the carrier from the initial invite has the supported heard, but it is stripped by the first box that receives it in our system. The carrier still sends the second invite however. Is there any way we can signal to the carrier not to send the second invite -- perhaps using the session-timer = refuse method that Michael mentioned? Thanks again for all the assistance. Will On Thu, Feb 19, 2015 at 3:28 PM, Will Ferrer <will.fer...@switchsoft.com> wrote:
|
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users