-us...@lists.sip-router.org
Subject: Re: [SR-Users] SIP re-invite Packets
ReInvites like all in-dialog requests are processed in has_totag()/loose_route
part. Default kamailio.cfg has almost identical part for this purpose.
Main idea is that an initial request (non in-dialog) hasn't T
On Behalf Of Alex
>Balashov
>Sent: Tuesday, July 17, 2018 4:25 PM
>To: Kamailio (SER) - Users Mailing List < sr-users@lists.kamailio.org>
>Cc: sr-us...@lists.sip-router.org
>Subject: Re: [SR-Users] SIP re-invite Packets
>
>On Tue, Jul 17, 2018 at 04:21:25PM +0300, Ali T
Behalf Of Alex Balashov
Sent: Tuesday, July 17, 2018 4:25 PM
To: Kamailio (SER) - Users Mailing List
Cc: sr-us...@lists.sip-router.org
Subject: Re: [SR-Users] SIP re-invite Packets
On Tue, Jul 17, 2018 at 04:21:25PM +0300, Ali Taher wrote:
> Can you please send me a simplified config that suit
On Tue, Jul 17, 2018 at 04:21:25PM +0300, Ali Taher wrote:
> Can you please send me a simplified config that suit my case ?
Try this for a main request route:
---
route {
if(!mf_process_maxfwd_header("10")) {
sl_send_reply("483", "Too Many Hops");
exit;
s On Behalf Of Alex Balashov
Sent: Tuesday, July 17, 2018 3:44 PM
To: Kamailio (SER) - Users Mailing List
Cc: sr-us...@lists.sip-router.org
Subject: Re: [SR-Users] SIP re-invite Packets
Hi,
In-dialog requests must be handled using loose_route(). You can find the proper
boilerplate in the
Hi,
In-dialog requests must be handled using loose_route(). You can find the
proper boilerplate in the stock configuration file:
https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg#L587
To note, your config is not sufficient to handle all aspects of a call
between endpoints in an a
Hello,
I'm using below routing logic to change the 183 reply to 180 and send it
back to the origination.
Noting that Kamailio is listening on 5065.
route{
if (is_method("INVITE")) {
xlog("L_INFO","INSIDE request route $si \n");
insert_hf("X-AUTH-IP: $si\r\n");
}
rout
