; ...
>> if (loose_route())
>> {
>> // check for re-INVITE
>>
>> }
>>
>> // check for new INVITE ???
>>
>> }
>>
>>
>> Thanks,
>> AS
>>
>>
>>
>> > From: abalas...@evaristesys.com
>
for new INVITE ???
}
Thanks,
AS
> From: abalas...@evaristesys.com
> Date: Wed, 31 Oct 2012 16:57:04 +0400
> To: sr-users@lists.sip-router.org
> Subject: Re: [SR-Users] statefull proxy Q
>
> Yes. The reinvite is a sequential (in-dialog) request and, like all
sequential requests
31 okt 2012 kl. 14:15 skrev Alex Solt :
> I appreciate for the response.
>
> I am using an old kamailio app. The has_totag() and loos_route() blocks are
> within the route() block. The question is where is the right place to check
> the new INVITE?
> Is it after the has_totag() block?
>
>
>
(loose_route())
{
// check for re-INVITE
}
// check for new INVITE ???
}
Thanks,
AS
> From: abalas...@evaristesys.com
> Date: Wed, 31 Oct 2012 16:57:04 +0400
> To: sr-users@lists.sip-router.org
> Subject: Re: [SR-Users] statefull proxy Q
>
> Yes.
Yes. The reinvite is a sequential (in-dialog) request and, like all sequential
requests, is handles in a different place in the route script than initial
requests.
Sequential requests are processed in the loose_route() section of the main
request route. Initial requests (such as initial INVITE
31 okt 2012 kl. 13:53 skrev Alex Solt :
> Hi,
>
> Is there any function in kamailio that could differentiates between a new
> incoming INVITE message and a re-INVITE message for an existing active call?
Check the default configuration script for how we separate messages in a dialog.
Look for
Hi,
Is there any function in kamailio that could differentiates between a new
incoming INVITE message and a re-INVITE message for an existing active call?
Thanks,
AS
___
SIP Express Router (SER) and Kamailio (
