Module:sca Line seize does not release after some 'BYE's #341
Comments
TheGrandWazoo
changed the title
|
If you can get a clean packet capture, feel free to send it to me off-list. If you can't, then perhaps you can dig all of the Kamailio logs out for -- Jorj On 9/23/15 3:44 PM, Kevin Scott Adams wrote:
|
|
It will be hard to get a packet capture but I can give you what I have in the logs. I will also get homer going which should give us a better capture due to it sporadicness. |
|
You can send it directly to me off-list. -- Jorj On 9/23/15 3:51 PM, Kevin Scott Adams wrote:
|
|
Jorj, What is the email address to send you the capture and SCA output. I think I see the issue but don't know why it happens? |
|
Ill try this...hope it works. sip:Mindfield@kamailio.newgarllc.com 1 active 1444143590 sip:Mindfield@192.168.1.85 sip:1030@192.168.1.40:5060 e90b49fb-d94a179a-a738a3@192.168.1.85 7EF5202B-6BC5E1EA 1c836141488 Thanks, Kevin Scott Adams ----- Original Message ----- From: "kamailio-sync" notifications@github.com You can send it directly to me off-list. -- Jorj On 9/23/15 3:51 PM, Kevin Scott Adams wrote:
— |
|
Jorj, Just my observation. Kev |
|
Apologies for being unresponsive; I've recently left Penn. I'll need more detail, unfortunately. Can you send any log messages e90b49fb-d94a179a-a738a3@192.168.1.85 -- Jorj On 10/13/15 10:34 AM, Kevin Scott Adams wrote:
|
|
Jorj, I do not have that log file any more. I will need to look for a new seize and give you that info. Sorry about that, kevin.adams@ksatechnologies.com ----- Original Message ----- From: "Jorj Bauer" notifications@github.com Apologies for being unresponsive; I've recently left Penn. I'll need more detail, unfortunately. Can you send any log messages e90b49fb-d94a179a-a738a3@192.168.1.85 -- Jorj On 10/13/15 10:34 AM, Kevin Scott Adams wrote:
— |
|
Jorj, I'm going to see on my test system if I can find out why we might be missing these < INVITE >s. |
|
Reopen if this issue is still actual and new details can be provided. |
|
Yes, it is still happening under 4.2 at the current git patch. Phones are Polycom VVX310/410 at 5.3.2 and I have Homer running to capture. Problem is only outbound from Polycom to an outside line via an Audiocode Mediant 1000 with the phone(s) having 2 different SCA's and 2 to 3 line appearances per SCA. Thanks, Kevin Scott Adams ----- Original Message ----- From: "Daniel-Constantin Mierla" notifications@github.com Reopen if this issue is still actual and new details can be provided. |
|
Is there a committer/developer for this module? |
|
Typical log entry under the [SCA] route for this situation... Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: exec: *** cfgtrace:request_route=[SCA] c=[//etc/kamailio/kamailio.cfg] l=984 a=16 n=if The [SCA] route is the one in the modules readme or website doc. |
|
Another seized via kamcmd sca.all_appearances Saturday, June 04, 2016 1:04:30 PM Log on the siezed.... |
|
@JorjBauer used to maintain the module at some point, but I think he changed positions and not sure if he is still involved in some work with the module. |
|
Good day. Now for the SCA problem. It seems that the unreleased "seized event" resides with the "held" event and the reinvite/invite that occurs to kamailio. It seems to get lost, hungup. pushed around or jacked up in the 'route[WITHINDLG]' section of the script and the reinvites/invites will keep happening until a timeout occurs or the sometimes I have seen the 404 Not here error occur. I know this is not much to go on until I upload a good trace but maybe a brainiac might go...Oh, I know that problem and quicker fix. Using Kamailio 4.2.7 with latest patches. CentOS 6.7-latest. One test bed is a mix of 2 Polycom VVX [34]10 with 5.4.4 and 1 Polycom 650 with 3.3.5; Another is a mix of 14 Polycoms VVX [34]10 with 5.3.2, another is a mix of 4 Polycom VVX [34]10 with 5.3.2 |
|
Good day to people following this. But, this issue still persists and I can confirm and duplicate the issue now that has been haunting me (and others) for quite some time. This issue is when a call is placed on HOLD and another phone picks up the 'held' call...all seems fine until the hangup. This is when the line is still considered 'active' by the SCA module. The current UA (Polycom) seems to have released it but all other phones have the 'appearance' still active. Within 15 to 20 seconds the UA that was part of the released call receives the 'active' appearance. It can be duplicated every time. |
|
If people are following this issue thread, I have decided to forked the kamailio repo to my Github account and I am actively working on fixing the issue(s) i have encountered, cleaning up code and hoping to enhance the code to make the module better. The fork is at https://github.com/TheGrandWazoo/kamailio and I will be committing some changes soon. Thanks |
|
I have been committing changes to the 4.3 branch and HEAD under my fork at this time. |
|
According to PR #768, this was fixed. |
I have a situation that I can't get my head around. Every so often I have a SCA seized and I need to manually release it. Here is the log of the sca and bye from the event logs.
messages-20150920:Sep 18 14:35:28 sip-registrar /usr/sbin/kamailio[7608]: ERROR: sca [sca_call_info.c:1580]: sca_call_info_bye_handler(): sca_call_info_bye_handler: sip:Mindfield@kamailio.newgarllc.com dialog leg 96b9ad37-9a7fa462-15c35d3@192.168.1.117;1c389191866 is not active
messages-20150920:Sep 18 14:35:28 sip-registrar /usr/sbin/kamailio[7610]: NOTICE: acc [acc.c:317]: acc_log_request(): ACC: transaction answered: timestamp=1442601328;method=BYE;from_tag=76C3EC1F-114D759A;to_tag=1c389191866;call_id=96b9ad37-9a7fa462-15c35d3@192.168.1.117;code=200;reason=OK;src_user=Mindfield;src_domain=kamailio.newgarllc.com;src_ip=192.168.1.40;dst_ouser=Mindfield;dst_user=Mindfield;dst_domain=192.168.1.117
And the kamcmd showing the seize line
sip:Mindfield@kamailio.newgarllc.com 1 active 1442601278 sip:Mindfield@192.168.1.117 sip:1030@192.168.1.40:5060 96b9ad37-9a7fa462-15c35d3@192.168.1.117 76C3EC1F-114D759A 1c389191866
I am running Kamailio 4.2.6. The phones are Polycom VVX 310/410 running 5.3.1. And the PSTN gateway is an Audiocodes Mediant 1000 running 6.60A.292.001.
The call volume is light so I don't think there is a lot of traffic but there is about 16 phones one SCA. It is not happening all time. Could be a couple days that nothing happens and then there could be a couple days that it happens multiple times a day. I can't find a common element that would be causing this unless the 'bye' is closing the call before the SCA has a chance to do something with it.
Thanks
Kev
The text was updated successfully, but these errors were encountered: