[Freeswitch-users] 183 early media" followed by 180 Ringing From Mobile Carriers

[Tihomir Culjaga]

Hi, im not sure about the callflow you have so i suppose its an incoming call from a carrier to freeswitch and you want to generate an inband ringback to the calling user. In that case you use pre_answer followed by ring_ready. Of course you set ringback var to a tone or wav file so freeswitch can actually generate that inband.

Sent from my iPhone

> On 19 Mar 2018, at 20:41, Jonathan Hunter <hunterj91 at hotmail.com> wrote:
> 
> Hi Guys,
> 
> Sorry to bring this up again but I see it when performing interopt testing with mobile carriers.
> 
> A number of them due to ISUP interworking, have gateways that generate a 183 with SDP, then a 180ringing.
> 
> I understand from ready for example this jira case FreeSWITCHFS-3859 SOFIA "183 early media" followed by "180 Ringing" where this is done by design.
> 
> I just wondered if this position had changed and if there is a configuration parameter/option that can allow any early media message to be sent back to A leg by freeswitch, in particular a 183 with SDP, then a subsequent 180 ringing, as carriers tend to want to see both.
> 
> Many thanks
> 
> Jon
> 
> 
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://confluence.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20180321/d0fdbbbb/attachment-0001.html>