[SR-Users] in-dialog contact update before dialog being confirmed

Daniel-Constantin Mierla miconda at gmail.com
Thu May 25 17:56:50 CEST 2017


Btw, can you send a pcap with signaling for a call that sends the update
request with a new contact. It should be useful for tracking what dialog
does and enhance it to use the new contact in its structure.

On Thu, May 25, 2017 at 5:19 PM, Daniel-Constantin Mierla <miconda at gmail.com
> wrote:

> Hello,
>
> the responses to a request are routed using Via headers. The Contact is to
> be used for requests within the dialog.
>
> I am not aware of any method defined by specs to update the Via path for
> ongoing transactions -- no traveling with limited available time and I
> haven't looked recently at new specs to actually comment more precisely.
>
> A solution could be to send a CANCEL to previous transaction and then
> initiate a new INVITE as the device is moving from one IP to another.
>
> Cheers,
> Daniel
>
> On Thu, May 25, 2017 at 10:08 AM, Jayesh Nambiar <jayesh1017 at gmail.com>
> wrote:
>
>> Hello Alex,
>> I managed to send the UPDATE method from my endpoint but still the
>> kamailio is not updating the new contact. The UPDATE method is simply loose
>> routed from caller-callee when a network change is detected on the client.
>> Though the UPDATE is relayed and responded back correctly; the subsequent
>> response still goes to the initial contact address.
>> Also when the dialog is established; kamailio correctly updates the
>> contact on Re-Invite but it does not on an UPDATE method.
>>
>> Anything particular to be done in this case. Thanks.
>>
>> - Jayesh
>>
>> On Wed, May 24, 2017 at 3:53 PM, Alex Balashov <abalashov at evaristesys.com
>> > wrote:
>>
>>> Hi Jayesh,
>>>
>>> This is the exact purpose of UPDATE - to update the dialog remote target
>>> before the dialog is established.
>>>
>>> But of course, properly implementing and following it is up to the
>>> endpoints.
>>>
>>> -- Alex
>>>
>>> > On May 24, 2017, at 5:46 AM, Jayesh Nambiar <jayesh1017 at gmail.com>
>>> wrote:
>>> >
>>> > Hello,
>>> > In a user-user based calling on mobile apps, when the call is
>>> connected and the user moves from a Wifi to Mobile data (network change);
>>> the device sends a Re-Invite with new contact information and subsequent
>>> messages go to appropriate changed contact address.
>>> > But when the dialog is in say ringing state; and the caller moves from
>>> one network to another; what would be an appropriate SIP method to trigger
>>> the contact update. My problem is generating a Re-INVITE or an UPDATE
>>> before the call is connected is very difficult.
>>> > What I tried is sending an in-dialog INFO message with new contact
>>> address; which gets relayed to the called party and the response for INFO
>>> is also properly received on the new contact address. But the subsequent
>>> response of the INVITE like a 486 or 200 goes to the original contact only.
>>> > What would be the best way to update the contact address of a client
>>> if I'm maintaining all the dialogs in kamailio.
>>> >
>>> > Thanks,
>>> >
>>> > - Jayesh
>>> > _______________________________________________
>>> > Kamailio (SER) - Users Mailing List
>>> > sr-users at lists.kamailio.org
>>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>> _______________________________________________
>>> Kamailio (SER) - Users Mailing List
>>> sr-users at lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>



-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20170525/9c2ed65e/attachment.html>


More information about the sr-users mailing list