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
31 okt 2012 kl. 13:53 skrev Alex Solt alex_solt@hotmail.com:
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 has_totag()
/O
-- * Olle E. Johansson - oej@edvina.net * Kamailio & SIP Masterclass Miami FL December 2012 * http://edvina.net/training/
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 INVITEs) are dealt with further down.
Alex Solt alex_solt@hotmail.com wrote:
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 (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
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?
route { ....
if (has_totag()) { ... if (loose_route()) { // check for re-INVITE
}
// check for new INVITE ???
}
Thanks, AS
From: abalashov@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, 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 INVITEs) are dealt with further down.
Alex Solt alex_solt@hotmail.com wrote:
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 (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Sent from my mobile, and thus lacking in the refinement one might expect from a fully-fledged keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
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
Inside if(loose_route()) will do.
if(has_totag()) { if(loose_route()) { if(is_method("INVITE")) { # It's a reinvite. } } }
On 10/31/2012 09:15 AM, Alex Solt wrote:
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?
route { ....
if (has_totag()) { ... if (loose_route()) { // check for re-INVITE
}
// check for new INVITE ???
}
Thanks, AS
From: abalashov@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, 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 INVITEs) are dealt with further down.
Alex Solt alex_solt@hotmail.com wrote:
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 (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Sent from my mobile, and thus lacking in the refinement one might
expect from a fully-fledged keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
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
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
31 okt 2012 kl. 14:19 skrev Alex Balashov abalashov@evaristesys.com:
Inside if(loose_route()) will do.
The question was "where is the right place
to check the new INVITE?"
Proper answer would be after this block... :-)
/O
if(has_totag()) { if(loose_route()) { if(is_method("INVITE")) { # It's a reinvite. } } }
On 10/31/2012 09:15 AM, Alex Solt wrote:
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?
route { ....
if (has_totag()) { ... if (loose_route()) { // check for re-INVITE
}
// check for new INVITE ???
}
Thanks, AS
From: abalashov@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, 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 INVITEs) are dealt with further down.
Alex Solt alex_solt@hotmail.com wrote:
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 (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Sent from my mobile, and thus lacking in the refinement one might
expect from a fully-fledged keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
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
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
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
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
31 okt 2012 kl. 14:15 skrev Alex Solt alex_solt@hotmail.com:
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?
route { ....
if (has_totag()) { ... if (loose_route()) { // check for re-INVITE
} // check for new INVITE ???
}
A new invite would not have a totag, so you have to check AFTER the block that checks the existence of the to-tag.
Please check the sample configuration you got with Kamailio to learn more!
Regards, /Olle
-- * Olle E. Johansson - oej@edvina.net * Kamailio & SIP Masterclass Miami FL December 2012 * http://edvina.net/training/