18 Feb
2010
18 Feb
'10
11:47 a.m.
Hi,
I'm using kamailio 1.5 from the branch. In a conditional forwarding scenario
with this call flow:
Phone A Kamailio Phone B Phone C
| | | |
| | | |
| | | |
|INVITE | | |
|------------->| | |
|100 Trying | | |
|<-------------| | |
| |INVITE | |
| |------------->| |
| |100 trying | |
| |<-------------| |
| |180 Ringing | |
| |<-------------| |
|180 Ringing | | |
|<-------------| | |
| |486 Busy Here | |
| |<-------------| |
| |ACK | |
| |------------->| |
| |INVITE | |
| |---------------------------->|
| |100 trying | |
| |<----------------------------|
| |180 Ringing | |
| |<----------------------------|
|180 Ringing | | |
|<-------------| | |
| |200 OK | |
| |<----------------------------|
|200 OK | | |
|<-------------| | |
|ACK | | |
|------------->| | |
| |ACK | |
| |---------------------------->|
| | | |
| | | |
What I'm observing is that when Kamailio receives the 486 from B, the dialog
between A and B is not destroyed, so when the call is finally established
between A and C there are two active dialogs as I could check with `kamctl
fifo get_statistics active_dialogs`. Shouldn't there be only one active
dialog? Is this a problem in my script or a problem with the dialog module?
Thanks in advance,
Santi
18 Feb
18 Feb
12:16 p.m.
El Jueves, 18 de Febrero de 2010, Santiago Gimeno escribió:
Hi,
I'm using kamailio 1.5 from the branch. In a conditional forwarding
scenario with this call flow:
Phone A Kamailio Phone B Phone C
|INVITE | | |
|------------->| | |
|100 Trying | | |
|<-------------| | |
|
| |INVITE | |
| |------------->| |
| |100 trying | |
| |<-------------| |
| |180 Ringing | |
| |<-------------| |
|
|180 Ringing | | |
|<-------------| | |
|
| |486 Busy Here | |
| |<-------------| |
| |ACK | |
| |------------->| |
| |INVITE | |
| |---------------------------->|
| |100 trying | |
| |<----------------------------|
| |180 Ringing | |
| |<----------------------------|
|
|180 Ringing | | |
|<-------------| | |
|
| |200 OK | |
| |<----------------------------|
|
|200 OK | | |
|<-------------| | |
|ACK | | |
|------------->| | |
|
| |ACK | |
| |---------------------------->|
What I'm observing is that when Kamailio receives the 486 from B, the
dialog between A and B is not destroyed, so when the call is finally
established between A and C there are two active dialogs as I could check
with `kamctl fifo get_statistics active_dialogs`. Shouldn't there be only
one active dialog? Is this a problem in my script or a problem with the
dialog module?
For now dialog module is not "forking-aware" which means that fails detecting
cases like yours. However I don't know which should be the expected behaviour
for your case (serial forking) with the current dialog module code.
PS: Could you tell me how did you "paint" the above SIP flow? it's very nice
:)
--
Iñaki Baz Castillo <ibc(a)aliax.net>
12:35 p.m.
Hi Iñaki,
2010/2/18 Iñaki Baz Castillo <ibc(a)aliax.net>
For now dialog module is not "forking-aware" which means that fails
detecting
cases like yours. However I don't know which should be the expected
behaviour
for your case (serial forking) with the current dialog module code.
Thanks for the answer.
It's a pity it's not supported as it makes the pua_dialoginfo module to work
in a weird way. It's not nice to see a BLF for a extension that's not
actually ringing. Maybe something can be done in the script in order to drop
the PUBLISH requests I'm not interested in. Do you think this is feasible?
PS: Could you tell me how did you "paint" the above SIP flow? it's very
nice
:)
Yeah, it's great. It doesn't look it's maintained anymore but it does its
job just fine:
http://sourceforge.net/projects/callplot/
Best regards,
Santi
--
Iñaki Baz Castillo <ibc(a)aliax.net>
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
19 Feb
19 Feb
4:22 a.m.
nice tip santi!
i thought you typed the callflow character per character.
Kelvin Chua
On Thu, Feb 18, 2010 at 6:35 PM, Santiago Gimeno
<santiago.gimeno(a)gmail.com>wrote;wrote:
Hi Iñaki,
2010/2/18 Iñaki Baz Castillo <ibc(a)aliax.net>
For now dialog module is not "forking-aware" which means that fails
detecting
cases like yours. However I don't know which should be the expected
behaviour
for your case (serial forking) with the current dialog module code.
Thanks for the answer.
It's a pity it's not supported as it makes the pua_dialoginfo module to
work in a weird way. It's not nice to see a BLF for a extension that's not
actually ringing. Maybe something can be done in the script in order to drop
the PUBLISH requests I'm not interested in. Do you think this is feasible?
PS: Could you tell me how did you "paint" the above SIP flow? it's very
nice
:)
Yeah, it's great. It doesn't look it's maintained anymore but it does its
job just fine:
http://sourceforge.net/projects/callplot/
Best regards,
Santi
--
Iñaki Baz Castillo <ibc(a)aliax.net>
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
5390
days inactive
5391
days old
3 comments
3 participants
participants (3)
-
Iñaki Baz Castillo -
Kelvin Chua -
Santiago Gimeno