[Freeswitch-users] SIP REFER - URI Parameters

[Phil Dunks]

Hi Anthony.

Thanks for looking at this and exposing the sip_refer_to_params variable.

I’ve updated to head, and can see the change in sofia.c.

Sorry for being dense, but I’ve not had much luck getting the uri params from the REFER to the INVITE.

My dial plan is very simple.

<include>
 <extension name="public_did">
  <condition field="destination_number" expression="(\d+)">
    <action application="set" data="proxy_media=true"/>    		
    <action application="bridge" data="sofia/gateway/${distributor(load-balance ${sofia(profile external gwlist down)})}/$1"/>
   </condition>
 </extension>
</include>

I tried appending ${sip_refer_to_params} to the bridge uri, but no luck. 

It seems the REFER is handled by sofia_handle_sip_i_refer in sofia.c which sets up a blind transfer.

I’ve been staring at sofia.c all morning - but not worked out what I need to do.

Please could you shed some light on how to proceed.

Thanks again,
Phil











From: Anthony Minessale <anthony.minessale at gmail.com>
Subject: Re: [Freeswitch-users] SIP REFER - URI Parameters
Date: 28 February 2014 19:15:11 GMT
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Reply-To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>


Added a patch to expose sip_refer_to_params vars.  See latest HEAD.


On Fri, Feb 28, 2014 at 11:17 AM, Phil Dunks <phil.dunks at netdev.co.uk> wrote:
Hi Guys

I’m trying to use FS (1.5.8b from last week) as an SBC and load-balancer (using mod_distributor).

It is load balancing between several FS conference nodes.

It’s working a treat, apart from one scenario :

Say conference xyz is already running on conf-node-1.

Next incoming call is sent to conf-node-2, pin is collected, and conference xyz is identified as the required conference.

Conf-node-2 checks presence, and sees the conference is already running on conf-node-1, and does a deflect.

We add some query params to the refer-to URI to tell conf-node-1 not to collect the pin, but put the caller straight into the conference.

e.g <action application="deflect" data=“sip:1234 at 10.1.1.2;conf=xyz" />

In the REFER I can see the params :

Refer-To: <sip:1234 at 10.1.1.2;conf=xyz>

But they are not present on the request URI or To header in the INVITE to conf-node-1.

So conf-node-1 requests the PIN again.

Is there any way I can pass this info to the other conference node by using the REFER?

Thanks for your help.

Phil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140303/b561da5c/attachment.html