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. Where would you like me to send it too?

--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-142709756

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?

--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-146525266

Jorj, The issue seems to be only with the Polycom UA making a call outbound. I can not find an issue with and inbound call. The Call-ID of the seize/appearance seems to be missing some characters on the prefix of the at-sign in relations to the real Call-ID of the INVITE/BYE.

Just my observation.

Kev

--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-147733763

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 Scott Adams KSA Technologies, LLC 4625 Sundew Street Commerce Township, MI. 48382

http://www.ksatechnologies.com kevin.adams@ksatechnologies.com P: +1 248 521 8203 ----- Original Message -----

From: "Jorj Bauer" notifications@github.com To: "kamailio/kamailio" kamailio@noreply.github.com Cc: "Kevin Scott Adams" thegrandwazoo@ksatechnologies.com Sent: Wednesday, October 14, 2015 8:28:57 AM Subject: Re: [kamailio] Module:sca Line seize does not release after some 'BYE's (#341)

Apologies for being unresponsive; I've recently left Penn.

I'll need more detail, unfortunately. Can you send any log messages relating to that Call ID?

e90b49fb-d94a179a-a738a3@192.168.1.85

-- Jorj

On 10/13/15 10:34 AM, Kevin Scott Adams wrote:

Jorj, The issue seems to be only with the Polycom UA making a call outbound. I can not find an issue with and inbound call. The Call-ID of the seize/appearance seems to be missing some characters on the prefix of the at-sign in relations to the real Call-ID of the INVITE/BYE.

Just my observation.

Kev

— Reply to this email directly or view it on GitHub https://github.com/kamailio/kamailio/issues/341#issuecomment-147733763.

— Reply to this email directly or view it on GitHub .

--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-149204328

Closed #341.

--- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#event-683451886

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

4625 Sundew Street Commerce Township, MI. 48382 Phone: +1 248 521 8203 Email: kevin.adams@ksatechnologies.com Web: www.ksatechnologies.com

----- Original Message -----

From: "Daniel-Constantin Mierla" notifications@github.com To: "kamailio/kamailio" kamailio@noreply.github.com Cc: "Kevin Scott Adams" thegrandwazoo@ksatechnologies.com, "Author" author@noreply.github.com Sent: Monday, June 6, 2016 4:59:22 PM Subject: Re: [kamailio/kamailio] Module:sca Line seize does not release after some 'BYE's (#341)

Reopen if this issue is still actual and new details can be provided. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

--- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-224311995

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 Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: exec: *** cfgtrace:request_route=[SCA] c=[//etc/kamailio/kamailio.cfg] l=974 a=25 n=is_method Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: exec: *** cfgtrace:request_route=[SCA] c=[//etc/kamailio/kamailio.cfg] l=990 a=16 n=if Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: exec: *** cfgtrace:request_route=[SCA] c=[//etc/kamailio/kamailio.cfg] l=984 a=25 n=is_method Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: exec: *** cfgtrace:request_route=[SCA] c=[//etc/kamailio/kamailio.cfg] l=990 a=24 n=sca_call_info_update Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: DEBUG: sca [sca_util.c:53]: sca_get_msg_contact_uri(): Empty Contact header Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: DEBUG: sca [sca_util.c:53]: sca_get_msg_contact_uri(): Empty Contact header Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: ERROR: sca [sca_call_info.c:1580]: sca_call_info_bye_handler(): sca_call_info_bye_handler: sip:ParksAndRec@kamailio.newgarllc.com dialog leg 170216930662016111325@192.168.1.40;584cf90b-57a7-4543-bfda-fd7cd71ca84c is not active Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: ERROR: sca [sca_call_info.c:2032]: sca_call_info_update(): Failed to update Call-Info state for Jun 6 11:14:28 sip-registrar /usr/sbin/kamailio[15361]: exec: *** cfgtrace:request_route=[SCA] c=[//etc/kamailio/kamailio.cfg] l=993 a=2 n=return

The [SCA] route is the one in the modules readme or website doc.

--- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-224317941

@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.

--- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-224347748

Good day. I think I have a lead on this to help come up with a resolution. I might be able to do it myself but I need to really dig into the code and kamailio to understand it better. First, I was using the sip_trace module along with Homer to gather the info, but it did seem incomplete. The work of the SCA module is not picked up by the sip_trace module. I believe because it if doing instead script work and sending its own packets, which would not be picked up by the script anymore. I finally used sngrep (referred by Javan Strika who is also having the issue) and was able to see the entire conversations for the SCA's. But the sngrep in a "HEP" and "non verbose" mode seems to have a memory leak and will crash kamailio due to no more memory. So, I am now turning to captagent to get a more stable system to get better traces for this issue.

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

--- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/341#issuecomment-231119363