3 Jan
2023
3 Jan
'23
8:26 p.m.
Hi All
I have setup kamailio using dispatcher to proxy registrations from the UAC to asterisk
but when asterisk sends an incoming call it does not seem to keep the path header and
therefore kamailio sends 404
is there anyway around this?
Thanks
Sent with [Proton Mail](https://proton.me/) secure email.
3 Jan
3 Jan
8:36 p.m.
Are you using chan_pjsip or chan_sip in Asterisk?
On Jan 3, 2023, at 12:26 PM, nutxase
<nutxase(a)proton.me> wrote:
Hi All
I have setup kamailio using dispatcher to proxy registrations from the UAC to asterisk
but when asterisk sends an incoming call it does not seem to keep the path header and
therefore kamailio sends 404
is there anyway around this?
Thanks
Sent with Proton Mail secure email.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
9:17 p.m.
Using chan_pjsip
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, January 3rd, 2023 at 5:36 PM, Alex Balashov <abalashov(a)evaristesys.com>
wrote:
Are you using chan_pjsip or chan_sip in Asterisk?
On Jan 3, 2023, at 12:26 PM, nutxase
nutxase(a)proton.me wrote:
Hi All
I have setup kamailio using dispatcher to proxy registrations from the UAC to asterisk
but when asterisk sends an incoming call it does not seem to keep the path header and
therefore kamailio sends 404
is there anyway around this?
Thanks
Sent with Proton Mail secure email.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
9:32 p.m.
Path support in upstream PJSIP is broken, from what I'm given to understand. This is a
regression from a capability that was (finally) added to chan_sip in Asterisk 12.
Digium/Sangoma have clearly stated that they have no interest to fix:
https://issues.asterisk.org/jira/browse/ASTERISK-28211
As stated in the comments on that JIRA issue, "There is no timeline." I'm
not sure what the logic is. I think it's something like, "Nobody uses
proxies" ?? Not sure.
Our generally accepted "fix" for this is to hack the Path hop into the Contact
header of the registrant before relaying the REGISTER upstream, so that registrations
appear to Asterisk to come "from" Kamailio. This requires careful management and
stateful reversion of the Contact value (i.e. in the RURI of incoming requests), making it
a brittle and suboptimal solution. But when "there is no timeline", what can you
do?
========
modparam("htable", "htable",
"contacts=>size=18;autoexpire=300;")
request_route {
...
if(method == "REGISTER") {
...
route(CONTACT_SPOOF_ENCODE);
t_on_reply("REGISTER_REPLY_FROM_PBX");
}
else if(src == PBX) {
# Request destined for registrant, e.g. INVITE.
route(CONTACT_SPOOF_DECODE);
}
}
onreply_route[REGISTER_REPLY_FROM_PBX] {
if(!method == "REGISTER")
return;
# If we are channeling a 200 OK for a register, it is very important to
# restore the exact Contact binding registered by the UA, together with
# all of its parameters, so that the UA comes to believe the binding
# has been properly established.
if($rs == 200)
route(CONTACT_SPOOF_DECODE);
}
# This routine gets around the lack of Path support in upstream registrars by
# encoding the original Contact domain as a supplementary parameter and attaching
# it to the Contact binding. This can then be recovered on inbound requests.
route[CONTACT_SPOOF_ENCODE] {
$var(hash_key) = $(ct{s.sha256});
$sht(contacts=>$var(hash_key)) = $ct;
remove_hf("Contact");
append_hf("Contact:
<sip:gateway@$Ri:$Rp;cthash=$var(hash_key)>\r\n");
}
# Use `cthash` parameter to retrieve original contact from `htable` if present,
# and replace. We do this in a contextually sensitive way, extracting `cthash`
# from the Contact header in a reply and from the RURI if it is a request.
route[CONTACT_SPOOF_DECODE] {
$var(ct) = $null;
if(t_is_request_route())
$var(ct) = $ru;
else if(t_is_reply_route())
$var(ct) = $(ct{nameaddr.uri}); # Unbracket the URI field.
if(strempty($(var(ct){param.value,cthash}))) {
if(t_is_request_route())
sl_send_reply("500", "Internal server error - missing
ct");
xlog("L_INFO", "[R-CONTACT-SPOOF-DECODE:$ci] !> Unable to
extract 'cthash' URI parameter\n");
exit;
}
$var(ct_key) = $(var(ct){param.value,cthash});
# Likewise error out if we cannot translate to the real contact, since there's
# no point in sending an adulterated contact to the UA.
if($sht(contacts=>$var(ct_key)) eq $null) {
if(t_is_request_route())
sl_send_reply("500", "Internal server error - cannot map
ct");
xlog("L_INFO", "[R-CONTACT-SPOOF-DECODE:$ci] !> cthash key does
not map to a contact!\n");
exit;
}
if(t_is_request_route())
$ru = $(sht(contacts=>$var(ct_key)){nameaddr.uri});
else {
remove_hf("Contact");
append_hf("Contact: $sht(contacts=>$var(ct_key))\r\n");
}
}
-- Alex
On Jan 3, 2023, at 1:17 PM, nutxase
<nutxase(a)proton.me> wrote:
Using chan_pjsip
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, January 3rd, 2023 at 5:36 PM, Alex Balashov <abalashov(a)evaristesys.com>
wrote:
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Are you using chan_pjsip or chan_sip in
Asterisk?
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: On Jan 3, 2023, at 12:26 PM, nutxase
nutxase(a)proton.me wrote:
Hi All
I have setup kamailio using dispatcher to proxy registrations from the UAC to asterisk
but when asterisk sends an incoming call it does not seem to keep the path header and
therefore kamailio sends 404
is there anyway around this?
Thanks
Sent with Proton Mail secure email.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: 
10:20 p.m.
Interesting workaround Alex, thanks for sharing.
For those who are looking for a less convoluted solution - may I suggest
setting endpoint's *outbound_proxy* value to Kamailio's address, such
as *sip:proxy.mydomain.com
<http://proxy.mydomain.com>\;lr*
Clearly, the above suggested solution doesn't do the trick for all possible
scenarios, mainly because it's static thus not suitable for redundancy, but
it may work for many (that's also probably the logic for Digium to ignore
it for so long).
Regards,
On Tue, Jan 3, 2023 at 1:58 PM Alex Balashov <abalashov(a)evaristesys.com>
wrote:
Path support in upstream PJSIP is broken, from what
I'm given to
understand. This is a regression from a capability that was (finally) added
to chan_sip in Asterisk 12.
Digium/Sangoma have clearly stated that they have no interest to fix:
https://issues.asterisk.org/jira/browse/ASTERISK-28211
As stated in the comments on that JIRA issue, "There is no timeline." I'm
not sure what the logic is. I think it's something like, "Nobody uses
proxies" ?? Not sure.
Our generally accepted "fix" for this is to hack the Path hop into the
Contact header of the registrant before relaying the REGISTER upstream, so
that registrations appear to Asterisk to come "from" Kamailio. This
requires careful management and stateful reversion of the Contact value
(i.e. in the RURI of incoming requests), making it a brittle and suboptimal
solution. But when "there is no timeline", what can you do?
========
modparam("htable", "htable",
"contacts=>size=18;autoexpire=300;")
request_route {
...
if(method == "REGISTER") {
...
route(CONTACT_SPOOF_ENCODE);
t_on_reply("REGISTER_REPLY_FROM_PBX");
}
else if(src == PBX) {
# Request destined for registrant, e.g. INVITE.
route(CONTACT_SPOOF_DECODE);
}
}
onreply_route[REGISTER_REPLY_FROM_PBX] {
if(!method == "REGISTER")
return;
# If we are channeling a 200 OK for a register, it is very important to
# restore the exact Contact binding registered by the UA, together with
# all of its parameters, so that the UA comes to believe the binding
# has been properly established.
if($rs == 200)
route(CONTACT_SPOOF_DECODE);
}
# This routine gets around the lack of Path support in upstream registrars
by
# encoding the original Contact domain as a supplementary parameter and
attaching
# it to the Contact binding. This can then be recovered on inbound
requests.
route[CONTACT_SPOOF_ENCODE] {
$var(hash_key) = $(ct{s.sha256});
$sht(contacts=>$var(hash_key)) = $ct;
remove_hf("Contact");
append_hf("Contact:
<sip:gateway@$Ri:$Rp;cthash=$var(hash_key)>\r\n");
}
# Use `cthash` parameter to retrieve original contact from `htable` if
present,
# and replace. We do this in a contextually sensitive way, extracting
`cthash`
# from the Contact header in a reply and from the RURI if it is a request.
route[CONTACT_SPOOF_DECODE] {
$var(ct) = $null;
if(t_is_request_route())
$var(ct) = $ru;
else if(t_is_reply_route())
$var(ct) = $(ct{nameaddr.uri}); # Unbracket the URI field.
if(strempty($(var(ct){param.value,cthash}))) {
if(t_is_request_route())
sl_send_reply("500", "Internal server error - missing
ct");
xlog("L_INFO", "[R-CONTACT-SPOOF-DECODE:$ci] !> Unable to
extract
'cthash' URI parameter\n");
exit;
}
$var(ct_key) = $(var(ct){param.value,cthash});
# Likewise error out if we cannot translate to the real contact, since
there's
# no point in sending an adulterated contact to the UA.
if($sht(contacts=>$var(ct_key)) eq $null) {
if(t_is_request_route())
sl_send_reply("500", "Internal server error - cannot map
ct");
xlog("L_INFO", "[R-CONTACT-SPOOF-DECODE:$ci] !> cthash key
does
not map to a contact!\n");
exit;
}
if(t_is_request_route())
$ru = $(sht(contacts=>$var(ct_key)){nameaddr.uri});
else {
remove_hf("Contact");
append_hf("Contact: $sht(contacts=>$var(ct_key))\r\n");
}
}
-- Alex
the
sender!
On Jan 3, 2023, at 1:17 PM, nutxase
<nutxase(a)proton.me> wrote:
Using chan_pjsip
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, January 3rd, 2023 at 5:36 PM, Alex Balashov <
abalashov(a)evaristesys.com> wrote:
> Are you using chan_pjsip or chan_sip in Asterisk?
>
>> On Jan 3, 2023, at 12:26 PM, nutxase nutxase(a)proton.me wrote:
>>
>> Hi All
>>
>> I have setup kamailio using dispatcher to proxy registrations from the
UAC
to asterisk
>> but when asterisk sends an incoming call
it does not seem to keep the
path header and therefore kamailio sends 404
>> is there anyway around this?
>>
>> Thanks
>>
>> Sent with Proton Mail secure email.
>>
>> __________________________________________________________
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only
to
the sender!
>> Edit mailing list options or
unsubscribe:
>
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
>
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only
to the
sender!
Edit
mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to Edit mailing list options or unsubscribe:
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
10:27 p.m.
On Jan 3, 2023, at 2:20 PM, Sergiu Pojoga
<pojogas(a)gmail.com> wrote:
Interesting workaround Alex, thanks for sharing.
For those who are looking for a less convoluted solution - may I suggest setting
endpoint's outbound_proxy value to Kamailio's address, such as
sip:proxy.mydomain.com\;lr
Though necessary, it is not sufficient. It'll get the REGISTER to Asterisk, but it
won't cause Asterisk to reach the registrant back via Kamailio.
Or do you mean "endpoint" in the chan_pjsip configuration sense? If so, and if
the flexibility is to do it that way, it should be fine.
In my case, I had phones which registered to Asterisk directly and phones which registered
via Kamailio. Hence the need for, as you say, a convoluted solution. :-)
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
9:41 p.m.
It is my unfortunate duty to tell you that…
https://lists.kamailio.org/pipermail/sr-users/2021-May/112628.html
https://www.mail-archive.com/sr-users@lists.kamailio.org/msg15253.html
On Tue, Jan 3, 2023 at 1:27 PM nutxase <nutxase(a)proton.me> wrote:
Using chan_pjsip
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, January 3rd, 2023 at 5:36 PM, Alex Balashov <
abalashov(a)evaristesys.com> wrote:
the
sender!
Are you using chan_pjsip or chan_sip in
Asterisk?
> On Jan 3, 2023, at 12:26 PM, nutxase nutxase(a)proton.me wrote:
>
> Hi All
>
> I have setup kamailio using dispatcher to proxy registrations from the
UAC to
asterisk
> but when asterisk sends an incoming call it
does not seem to keep the
path header and therefore kamailio sends 404
> is there anyway around this?
>
> Thanks
>
> Sent with Proton Mail secure email.
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only
to the
sender!
Edit
mailing list options or unsubscribe:
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
9:22 p.m.
https://issues.asterisk.org/jira/browse/ASTERISK-28211
3+ yrs and counting since we are waiting on a fix from Digium...
On Tue, Jan 3, 2023 at 1:01 PM Alex Balashov <abalashov(a)evaristesys.com>
wrote:
Are you using chan_pjsip or chan_sip in Asterisk?
On Jan 3, 2023, at 12:26 PM, nutxase
<nutxase(a)proton.me> wrote:
Hi All
I have setup kamailio using dispatcher to proxy registrations from the
UAC to
asterisk
but when asterisk sends an incoming call it does
not seem to keep the
path header and therefore kamailio sends 404
is there anyway around this?
Thanks
Sent with Proton Mail secure email.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the
sender!
Edit mailing list options or unsubscribe:
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
4 Jan
4 Jan
1:53 p.m.
Thanks for the workaround Alex
I do find it pathetic on digiums part that they still havent done anything about it.
Cheers
Sent with [Proton Mail](https://proton.me/) secure email.
------- Original Message -------
On Tuesday, January 3rd, 2023 at 5:26 PM, nutxase <nutxase(a)proton.me> wrote:
Hi All
I have setup kamailio using dispatcher to proxy registrations from the UAC to asterisk
but when asterisk sends an incoming call it does not seem to keep the path header and
therefore kamailio sends 404
is there anyway around this?
Thanks
Sent with [Proton Mail](https://proton.me/) secure email.
4:25 p.m.
Hello,
it seems that this bug apparently does not harm to many people, or the workaround with the
outbound proxy works for most of them.
Nobody from the open source community or other companies did it picked up as well in the
last years.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>
From: nutxase <nutxase(a)proton.me>
Sent: Wednesday, January 4, 2023 11:54 AM
To: sr-users(a)lists.kamailio.org
Subject: [SR-Users] Re: Dispatcher Incoming
Thanks for the workaround Alex
I do find it pathetic on digiums part that they still havent done anything about it.
Cheers
Sent with Proton Mail<https://proton.me/> secure email.
------- Original Message -------
On Tuesday, January 3rd, 2023 at 5:26 PM, nutxase
<nutxase@proton.me<mailto:nutxase@proton.me>> wrote:
Hi All
I have setup kamailio using dispatcher to proxy registrations from the UAC to asterisk
but when asterisk sends an incoming call it does not seem to keep the path header and
therefore kamailio sends 404
is there anyway around this?
Thanks
Sent with Proton Mail<https://proton.me/> secure email.
7:43 p.m.
On Jan 4, 2023, at 8:25 AM, Henning Westerholt
<hw(a)gilawa.com> wrote:
it seems that this bug apparently does not harm to many people, or the workaround with
the outbound proxy works for most of them.
I've been complaining about it constantly, but lack the PJSIP depth to provide a
robust fix.
I think it's quite unfortunate because it's functionality that used to exist in
chan_sip, when it was finally added in Asterisk 12. Systems were built with that
assumption in mind. chan_pjsip isn't supposed to be a step backwards...
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
8:17 p.m.
Hi Alex,
so far, we did not have any customer that need this functionality.
We did some work in asterisk chan_pjsip recently related to a special inter-op bug [1].
But it's certainly a bit more work as for Kamailio, especially if you are not doing it
that often and are not familiar with the processes.
Cheers,
Henning
[1] https://issues.asterisk.org/jira/browse/ASTERISK-30193
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com>
Sent: Wednesday, January 4, 2023 5:44 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: [SR-Users] Re: Dispatcher Incoming
On Jan 4, 2023, at 8:25 AM, Henning Westerholt
<hw(a)gilawa.com> wrote:
it seems that this bug apparently does not harm to many people, or the workaround with
the outbound proxy works for most of them.
I've been complaining about it constantly, but lack the PJSIP depth to provide a
robust fix.
I think it's quite unfortunate because it's functionality that used to exist in
chan_sip, when it was finally added in Asterisk 12. Systems were built with that
assumption in mind. chan_pjsip isn't supposed to be a step backwards...
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to
sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
8:26 p.m.
On Jan 4, 2023, at 12:17 PM, Henning Westerholt
<hw(a)gilawa.com> wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up having to
use something like the "imaginative" Contact workaround instead.
I suppose it's hard to say whether the functionality was strictly necessary or born of
a more puristic sensibility about how to make the proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to chan_pjsip, and
having previously relied on Path support because it existed in chan_sip for approximately
a decade. This means we had to totally rearchitect their systems, some of which have been
very stable for about that long.
No, it's not that I'm entitled and think open-source projects owe us something for
free, of course. But from a product management point of view, I think this is quite
embarrassing. It's better to never have offered Path at all than to implement it (with
considerable fanfare at the time!), then break it via a mandatory and quite controversial
upgrade path (chan_sip -> chan_pjsip), then obstinately refuse to fix it.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
8:47 p.m.
Hello Alex,
I completely agree to your point regarding the product management topic.
Some of our customers are also doing upgrades from chan_sip to chan_pjsip right now.
Let's see if they are affected, then I could have a closer look to that code. In case
there is a fix, I will let you (and the list know), for sure.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com>
Sent: Wednesday, January 4, 2023 6:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: [SR-Users] Re: Dispatcher Incoming
On Jan 4, 2023, at 12:17 PM, Henning Westerholt
<hw(a)gilawa.com> wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up having to
use something like the "imaginative" Contact workaround instead.
I suppose it's hard to say whether the functionality was strictly necessary or born of
a more puristic sensibility about how to make the proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to chan_pjsip, and
having previously relied on Path support because it existed in chan_sip for approximately
a decade. This means we had to totally rearchitect their systems, some of which have been
very stable for about that long.
No, it's not that I'm entitled and think open-source projects owe us something for
free, of course. But from a product management point of view, I think this is quite
embarrassing. It's better to never have offered Path at all than to implement it (with
considerable fanfare at the time!), then break it via a mandatory and quite controversial
upgrade path (chan_sip -> chan_pjsip), then obstinately refuse to fix it.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to
sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
14 Mar
14 Mar
4:30 a.m.
Hi,
For what it's worth, I am successfully using Path with Asterisk+pjsip ..
endpoint registers through Kamailio to Asterisk;
asterisk remembers path;
asterisk uses path when dialing endpoint with Dial(PJSIP/endpointid)
You have to enable a setting "support_path" ="yes" in the endpoint
configuration.
Asterisk 18.10.0~dfsg+~cs6.10.40431411-2, Copyright (C) 1999 - 2021, Sangoma Technologies
Corporation and others.
I believe there is a different issue with path support on non-registered
'trunks'.
Jawaid
On 1/4/23, 11:16 AM, "Henning Westerholt" <hw(a)gilawa.com
<mailto:hw@gilawa.com>> wrote:
Hello Alex,
I completely agree to your point regarding the product management topic.
Some of our customers are also doing upgrades from chan_sip to chan_pjsip right now.
Let's see if they are affected, then I could have a closer look to that code. In case
there is a fix, I will let you (and the list know), for sure.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/ <https://skalatan.de/blog/>
Kamailio services - https://gilawa.com <https://gilawa.com>
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com
<mailto:abalashov@evaristesys.com>>
Sent: Wednesday, January 4, 2023 6:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org
<mailto:sr-users@lists.kamailio.org>>
Subject: [SR-Users] Re: Dispatcher Incoming
On Jan 4, 2023, at 12:17 PM, Henning Westerholt
<hw(a)gilawa.com <mailto:hw@gilawa.com>> wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up having to
use something like the "imaginative" Contact workaround instead.
I suppose it's hard to say whether the functionality was strictly necessary or born of
a more puristic sensibility about how to make the proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to chan_pjsip, and
having previously relied on Path support because it existed in chan_sip for approximately
a decade. This means we had to totally rearchitect their systems, some of which have been
very stable for about that long.
No, it's not that I'm entitled and think open-source projects owe us something for
free, of course. But from a product management point of view, I think this is quite
embarrassing. It's better to never have offered Path at all than to implement it (with
considerable fanfare at the time!), then break it via a mandatory and quite controversial
upgrade path (chan_sip -> chan_pjsip), then obstinately refuse to fix it.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com <https://evaristesys.com>
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to
sr-users-leave(a)lists.kamailio.org <mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
<mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
4:57 a.m.
Interesting.
Path is only applicable to registrations.
On Mar 13, 2023, at 9:30 PM, Jawaid Bazyar
<bazyar(a)gmail.com> wrote:
Hi,
For what it's worth, I am successfully using Path with Asterisk+pjsip ..
endpoint registers through Kamailio to Asterisk;
asterisk remembers path;
asterisk uses path when dialing endpoint with Dial(PJSIP/endpointid)
You have to enable a setting "support_path" ="yes" in the endpoint
configuration.
Asterisk 18.10.0~dfsg+~cs6.10.40431411-2, Copyright (C) 1999 - 2021, Sangoma Technologies
Corporation and others.
I believe there is a different issue with path support on non-registered
'trunks'.
Jawaid
On 1/4/23, 11:16 AM, "Henning Westerholt" <hw(a)gilawa.com
<mailto:hw@gilawa.com>> wrote:
Hello Alex,
I completely agree to your point regarding the product management topic.
Some of our customers are also doing upgrades from chan_sip to chan_pjsip right now.
Let's see if they are affected, then I could have a closer look to that code. In case
there is a fix, I will let you (and the list know), for sure.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/ <https://skalatan.de/blog/>
Kamailio services - https://gilawa.com <https://gilawa.com>
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com
<mailto:abalashov@evaristesys.com>>
Sent: Wednesday, January 4, 2023 6:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org
<mailto:sr-users@lists.kamailio.org>>
Subject: [SR-Users] Re: Dispatcher Incoming
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
On Jan 4, 2023, at 12:17 PM, Henning Westerholt
<hw(a)gilawa.com <mailto:hw@gilawa.com>> wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up having to
use something like the "imaginative" Contact workaround instead.
I suppose it's hard to say whether the functionality was strictly necessary or born
of a more puristic sensibility about how to make the proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to chan_pjsip, and
having previously relied on Path support because it existed in chan_sip for approximately
a decade. This means we had to totally rearchitect their systems, some of which have been
very stable for about that long.
No, it's not that I'm entitled and think open-source projects owe us something
for free, of course. But from a product management point of view, I think this is quite
embarrassing. It's better to never have offered Path at all than to implement it (with
considerable fanfare at the time!), then break it via a mandatory and quite controversial
upgrade path (chan_sip -> chan_pjsip), then obstinately refuse to fix it.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com <https://evaristesys.com>
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email
to sr-users-leave(a)lists.kamailio.org <mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
<mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
5:33 a.m.
When the issue surfaced years ago, Asterisk 18 wasn't even out yet. Must
have been fixed quietly without backport to older versions.
On Mon, Mar 13, 2023, 10:21 p.m. Alex Balashov <abalashov(a)evaristesys.com>
wrote:
Interesting.
Path is only applicable to registrations.
up
having to use something like the "imaginative" Contact workaround
instead.
On Mar 13, 2023, at 9:30 PM, Jawaid Bazyar
<bazyar(a)gmail.com> wrote:
Hi,
For what it's worth, I am successfully using Path with Asterisk+pjsip ..
endpoint registers through Kamailio to Asterisk;
asterisk remembers path;
asterisk uses path when dialing endpoint with Dial(PJSIP/endpointid)
You have to enable a setting "support_path" ="yes" in the endpoint
configuration.
Asterisk 18.10.0~dfsg+~cs6.10.40431411-2, Copyright (C) 1999 - 2021,
Sangoma
Technologies Corporation and others.
I believe there is a different issue with path support on non-registered
'trunks'.
Jawaid
On 1/4/23, 11:16 AM, "Henning Westerholt" <hw(a)gilawa.com <mailto:
hw(a)gilawa.com>> wrote:
Hello Alex,
I completely agree to your point regarding the product management topic.
Some of our customers are also doing upgrades from chan_sip to
chan_pjsip right
now. Let's see if they are affected, then I could have a
closer look to that code. In case there is a fix, I will let you (and the
list know), for sure.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/ <
https://skalatan.de/blog/>
Kamailio services - https://gilawa.com
<https://gilawa.com>
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com <mailto:
abalashov(a)evaristesys.com>>
Sent: Wednesday, January 4, 2023 6:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org
<mailto:sr-users@lists.kamailio.org>>
Subject: [SR-Users] Re: Dispatcher Incoming
> On Jan 4, 2023, at 12:17 PM, Henning Westerholt <hw(a)gilawa.com <mailto:
hw(a)gilawa.com>> wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended
I suppose it's hard to say whether the functionality was strictly
necessary or
born of a more puristic sensibility about how to make the
proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to
chan_pjsip,
and having previously relied on Path support because it existed
in chan_sip for approximately a decade. This means we had to totally
rearchitect their systems, some of which have been very stable for about
that long.
No, it's not that I'm entitled and think open-source projects owe us
something for free, of course. But from a product management point of view,
I think this is quite embarrassing. It's better to never have offered Path
at all than to implement it (with considerable fanfare at the time!), then
break it via a mandatory and quite controversial upgrade path (chan_sip ->
chan_pjsip), then obstinately refuse to fix it.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com <https://evaristesys.com>
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an
email to sr-users-leave(a)lists.kamailio.org <mailto:
sr-users-leave(a)lists.kamailio.org>
Important: keep the mailing list in the
recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
<mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the
recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
>
>
>
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the
recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
6:31 a.m.
That possibility had not occurred to me, but it's quite sneaky.
On Mar 13, 2023, at 10:33 PM, Sergiu Pojoga
<pojogas(a)gmail.com> wrote:
When the issue surfaced years ago, Asterisk 18 wasn't even out yet. Must have been
fixed quietly without backport to older versions.
On Mon, Mar 13, 2023, 10:21 p.m. Alex Balashov <abalashov(a)evaristesys.com> wrote:
Interesting.
Path is only applicable to registrations.
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
On Mar 13, 2023, at 9:30 PM, Jawaid Bazyar
<bazyar(a)gmail.com> wrote:
Hi,
For what it's worth, I am successfully using Path with Asterisk+pjsip ..
endpoint registers through Kamailio to Asterisk;
asterisk remembers path;
asterisk uses path when dialing endpoint with Dial(PJSIP/endpointid)
You have to enable a setting "support_path" ="yes" in the endpoint
configuration.
Asterisk 18.10.0~dfsg+~cs6.10.40431411-2, Copyright (C) 1999 - 2021, Sangoma Technologies
Corporation and others.
I believe there is a different issue with path support on non-registered
'trunks'.
Jawaid
On 1/4/23, 11:16 AM, "Henning Westerholt" <hw(a)gilawa.com
<mailto:hw@gilawa.com>> wrote:
Hello Alex,
I completely agree to your point regarding the product management topic.
Some of our customers are also doing upgrades from chan_sip to chan_pjsip right now.
Let's see if they are affected, then I could have a closer look to that code. In case
there is a fix, I will let you (and the list know), for sure.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/ <https://skalatan.de/blog/>
Kamailio services - https://gilawa.com <https://gilawa.com>
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com
<mailto:abalashov@evaristesys.com>>
Sent: Wednesday, January 4, 2023 6:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org
<mailto:sr-users@lists.kamailio.org>>
Subject: [SR-Users] Re: Dispatcher Incoming
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: On Jan 4, 2023, at 12:17 PM, Henning Westerholt
<hw(a)gilawa.com <mailto:hw@gilawa.com>> wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up having to
use something like the "imaginative" Contact workaround instead.
I suppose it's hard to say whether the functionality was strictly necessary or born
of a more puristic sensibility about how to make the proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to chan_pjsip, and
having previously relied on Path support because it existed in chan_sip for approximately
a decade. This means we had to totally rearchitect their systems, some of which have been
very stable for about that long.
No, it's not that I'm entitled and think open-source projects owe us something
for free, of course. But from a product management point of view, I think this is quite
embarrassing. It's better to never have offered Path at all than to implement it (with
considerable fanfare at the time!), then break it via a mandatory and quite controversial
upgrade path (chan_sip -> chan_pjsip), then obstinately refuse to fix it.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com <https://evaristesys.com>
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email
to sr-users-leave(a)lists.kamailio.org <mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
<mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
11:27 a.m.
Hello,
looking at the first issue (a second one was created later that ultimately lead to the
fix) it seems to also affected asterisk 18:
https://issues.asterisk.org/jira/browse/ASTERISK-27963
My understanding that here were two issues, in "user" mode it was working, but
not in "trunk" mode. Link to the second issue:
https://issues.asterisk.org/jira/browse/ASTERISK-30100
Cheers,
Henning
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com>
Sent: Dienstag, 14. März 2023 04:31
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: [SR-Users] Re: Dispatcher Incoming
That possibility had not occurred to me, but it's quite sneaky.
On Mar 13, 2023, at 10:33 PM, Sergiu Pojoga
<pojogas(a)gmail.com> wrote:
When the issue surfaced years ago, Asterisk 18 wasn't even out yet. Must have been
fixed quietly without backport to older versions.
On Mon, Mar 13, 2023, 10:21 p.m. Alex Balashov <abalashov(a)evaristesys.com> wrote:
Interesting.
Path is only applicable to registrations.
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to
sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
On Mar 13, 2023, at 9:30 PM, Jawaid Bazyar
<bazyar(a)gmail.com> wrote:
Hi,
For what it's worth, I am successfully using Path with Asterisk+pjsip ..
endpoint registers through Kamailio to Asterisk; asterisk remembers
path; asterisk uses path when dialing endpoint with
Dial(PJSIP/endpointid)
You have to enable a setting "support_path" ="yes" in the endpoint
configuration.
Asterisk 18.10.0~dfsg+~cs6.10.40431411-2, Copyright (C) 1999 - 2021, Sangoma Technologies
Corporation and others.
I believe there is a different issue with path support on non-registered
'trunks'.
Jawaid
On 1/4/23, 11:16 AM, "Henning Westerholt" <hw(a)gilawa.com
<mailto:hw@gilawa.com>> wrote:
Hello Alex,
I completely agree to your point regarding the product management topic.
Some of our customers are also doing upgrades from chan_sip to chan_pjsip right now.
Let's see if they are affected, then I could have a closer look to that code. In case
there is a fix, I will let you (and the list know), for sure.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
<https://skalatan.de/blog/> Kamailio services - https://gilawa.com
<https://gilawa.com>
-----Original Message-----
From: Alex Balashov <abalashov(a)evaristesys.com
<mailto:abalashov@evaristesys.com>>
Sent: Wednesday, January 4, 2023 6:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org
<mailto:sr-users@lists.kamailio.org>>
Subject: [SR-Users] Re: Dispatcher Incoming
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
On Jan 4, 2023, at 12:17 PM, Henning Westerholt
<hw(a)gilawa.com <mailto:hw@gilawa.com>> wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up having to
use something like the "imaginative" Contact workaround instead.
I suppose it's hard to say whether the functionality was strictly
necessary or born of a more puristic sensibility about how to make
the proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to chan_pjsip, and
having previously relied on Path support because it existed in chan_sip for approximately
a decade. This means we had to totally rearchitect their systems, some of which have been
very stable for about that long.
No, it's not that I'm entitled and think open-source projects owe us something
for free, of course. But from a product management point of view, I think this is quite
embarrassing. It's better to never have offered Path at all than to implement it (with
considerable fanfare at the time!), then break it via a mandatory and quite controversial
upgrade path (chan_sip -> chan_pjsip), then obstinately refuse to fix it.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com <https://evaristesys.com>
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
<mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
<mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
605
days inactive
675
days old
18 comments
5 participants
participants (5)
-
Alex Balashov -
Henning Westerholt -
Jawaid Bazyar -
nutxase -
Sergiu Pojoga