CM 5.2.3 does not send response to 183 Session Progress message for a call call to Lync 2013

[keschber]

I have CM 5.2.3 and am trying to make a call to Lync 2013 via Avaya Session Manager 6.0 and Oracle (formerly Acme Packet) SBC.

During call setup the far end phone, Lync phone, rings but when answered the call is not established. The calling extension, Avaya extension continues to hear ring back for 30 seconds until the session times out.

We know that Lync is sending a 183 Session Progress message. This is making its way to the SBC then to Session Manager then to CM. CM never responds to this message.

Does anyone know if there is something that I need set in the Avaya to get this to work or if there are any tech notes that might explain why CM does not respond?

 

[montyzummer]

There is a setting on page 4 of your trunk group that pertains to that setting try changing that and see how you get on

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[keschber]

Thanks for the response.

These are the settings on page 4 of the trunk group but I don't see anything that looks like 183 Session progress.

Correction my CM version is 5.2.1.

We are able to make this work from CM to Genesys via the same Session Manager -> SBC path.

change trunk-group 12 Page 4 of 21
PROTOCOL VARIATIONS

Mark Users as Phone? n
Prepend '+' to Calling Number? n
Send Transferring Party Information? n
Network Call Redirection? n
Send Diversion Header? n
Support Request History? y
Telephone Event Payload Type: 101

 

[kyle555]

From CM 5.2.1 SP15 release notes...

Late PRACK for 183 provisional response caused a SIP call to drop when UPDATE reaches the far-end first.

What load of CM are you on? swversion from Linux... should have a 5 digit patch # that identifies the service pack?