12 Mar
2021
12 Mar
'21
12:30 p.m.
Hi everyone
I have a question regarding the dialog module.
It uses the RecordRoute header, which seems all fine.
The situation:
I have a setup, where the Kamailio proxy, which is running with the dialog module, is
talking to an Asterisk.
Now the logic in the Asterisk, is to place a new call, and return in to the Kamailio
proxy, which sends it to the PSTN.
By the logic of the asterisk, it doesn’t persist with the RecordRoute headers. It starts
from scratch with a new callId.
Here lies the problem. Because the RecordRoute header isn’t given, then a new “dialog” is
made, instead of using the one that is established.
Here comes my question.
Is it against the standards to make the Asterisk persist with these headers, or am I
looking at the wrong solution?
If not, I do see the power of the dialog module, when a call bounces between UAS’, but
not when an asterisk is in the setup.
Another solution could be to use a custom x- header for the dialog id, but it doesn’t look
like that is a possibility.
Have any of you run into this situation, and might have a solution?
Thanks in advance
// Nicki Bo Otte
12 Mar
12 Mar
8:37 p.m.
Hello,
Asterisk is a b2bua and it is normal to create a completely new and
different call. It is not only the missing of the record-route, but
different call-id, from-tag, etc ... Also, Asterisk can create many
outbound calls out of one incoming, for example in case of group hunting.
If you want to track a single dialog in such case, you have to track
only incoming one to asterisk, or the outgoing one.
Cheers,
Daniel
On 12.03.21 10:30, Nicki Otte wrote:
Hi everyone
I have a question regarding the dialog module.
It uses the RecordRoute header, which seems all fine.
The situation:
I have a setup, where the Kamailio proxy, which is running with the
dialog module, is talking to an Asterisk.
Now the logic in the Asterisk, is to place a new call, and return in
to the Kamailio proxy, which sends it to the PSTN.
By the logic of the asterisk, it doesn’t persist with the RecordRoute
headers. It starts from scratch with a new callId.
Here lies the problem. Because the RecordRoute header isn’t given,
then a new “dialog” is made, instead of using the one that is established.
Here comes my question.
Is it against the standards to make the Asterisk persist with these
headers, or am I looking at the wrong solution?
If not, I do see the power of the dialog module, when a call bounces
between UAS’, but not when an asterisk is in the setup.
Another solution could be to use a custom x- header for the dialog id,
but it doesn’t look like that is a possibility.
Have any of you run into this situation, and might have a solution?
Thanks in advance
// Nicki Bo Otte
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
15 Mar
15 Mar
11:45 a.m.
Thanks for the reply!
Sad but what I expected.
I’ll find another way around my situation then.
// Nicki Bo Otte
From: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Friday, 12 March 2021 at 18.37
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>rg>, Nicki Otte
<Duckay(a)live.com>
Subject: Re: [SR-Users] Dialog using Recod Route, with an asterisk
Hello,
Asterisk is a b2bua and it is normal to create a completely new and different call. It is
not only the missing of the record-route, but different call-id, from-tag, etc ... Also,
Asterisk can create many outbound calls out of one incoming, for example in case of group
hunting.
If you want to track a single dialog in such case, you have to track only incoming one to
asterisk, or the outgoing one.
Cheers,
Daniel
On 12.03.21 10:30, Nicki Otte wrote:
Hi everyone
I have a question regarding the dialog module.
It uses the RecordRoute header, which seems all fine.
The situation:
I have a setup, where the Kamailio proxy, which is running with the dialog module, is
talking to an Asterisk.
Now the logic in the Asterisk, is to place a new call, and return in to the Kamailio
proxy, which sends it to the PSTN.
By the logic of the asterisk, it doesn’t persist with the RecordRoute headers. It starts
from scratch with a new callId.
Here lies the problem. Because the RecordRoute header isn’t given, then a new “dialog” is
made, instead of using the one that is established.
Here comes my question.
Is it against the standards to make the Asterisk persist with these headers, or am I
looking at the wrong solution?
If not, I do see the power of the dialog module, when a call bounces between UAS’, but
not when an asterisk is in the setup.
Another solution could be to use a custom x- header for the dialog id, but it doesn’t look
like that is a possibility.
Have any of you run into this situation, and might have a solution?
Thanks in advance
// Nicki Bo Otte
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>
www.twitter.com/miconda<http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>
Funding: https://www.paypal.me/dcmierla
1351
days inactive
1354
days old
2 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Nicki Otte