Avaya SIP Phone disconnecting calls?

[fishnoob]

Hi all and firstly Happy New Year!

I am struggling with something I'm hoping someone can help with.

We are on a CM6 system with SM version 6.3.18.0.631804 with an Avaya SBC that we connect our remote users to, then to our SM.

Connectivity is fine and the phone works as it should with one exception:

When the user is connected to a call (trunk call or internal) and another call comes in and rings on the same call appearance, the CONNECTED call will disconnect without warning. You can answer the second call without issue.

Anyone ever heard of this or can aid in something to try?

Reviewed the config and it looks good?

Thanks in advance.

 

[kyle555]

a trace from session manager would be a good start! where does the initial disconnect come from? what kind of phone?

 

[jimbojimbo]

I believe I have seen this with OCS/Lync integration using RCC and I believe there was one other scenario where this came up but I can't recall the details. Since these are SIP endpoints are they showing as AST in System Manager.

 

[fishnoob]

Thanks for the quick replies!

The set is a 9608G
The TraceSM i set up shows the BYE being sent to the originating phone once the new call comes in.

Jimbo, I just checked and NONE of our endpoints are registered as AST. I think that might be it, but I gotta verify why they're not registering as AST in the first place.... gah!

Thanks all, I will update when I have new discoveries.

 

[jimbojimbo]

Make sure the public unknown table has the extensions in there. Also there as a "bug" if your are using "rp" in the SIP Trunk field on the station form so try AAR. Reboot the phone.

 

[JayNEC]

What is this bug you speak of?

New England Communications

http://www.necomm.com

 

[jimbojimbo]

May not apply on a 6.3.18 but on 7.0.1 I had to have a custom patch 24013 created. When using rpXXX where XXX is the route pattern instead of AAR in the SIP trunk field of the station form the avaya-cm-feature interactions with SIP stations would not work correctly. Symptoms include send-call status incorrect and bridged call appearances not working. It was fixed in a 7.1 patch however 7.1 is a major upgrade of the underlying OS so customer didn't want to make that move yet.