Acme Packet (MOSC)

MOSC Banner

Avaya Transfers to Lync cause 488 or 491 GatewayCall is not in conneced state

in Acme Packet (MOSC) Question

While troubleshooting a multiplatform environment, we found that calls placed to an Avaya, then transferred to MS Lync 2013 (Skype for Business) through the SBC fail with GatewaCall is not in connected state.   On a warm transfer you will get a 488, on a blind transfer you will get a 491.

Looking at the sip traces we found that the Avaya does not supply an SDP in the re-invite.  Microsoft has recognized this as an issue in SR number 114022611216239


The fix to this problem was to use the following parameters in the sip-interface for Lync


add-sdp-invite

add-sdp-profile PCMU   <or whatever you named your media-profiles>

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center