SIP Trunk Between NRS and Avaya Session Manager

[nortavaya]

Hello,

We have created a SIP Trunk between the NRS (CS1000) and Avaya Session Manager
When we call from Avaya Session Manager (station in CM) to the CS1K, the call works fine, however when we call from CS1K side, we got busy tone (release and try again)

When we check SIP traces of both Sig Server and Session Manager we can see this error:

500 Server Internal Error (Cannot determine realm)(INVITE) => on the INVITE sent from CS1K to SM

Please any idea what can be the issue ?

Thank you in advance.

 

[KCFLHRC]

See below

Session Manager sending back 500 Server Internal Error
Rate Content Rate this Page

Doc ID: SOLN297687
Version: 1.0
Status: Published
Published date: 04 Oct 2016
Author:
Wil Gillis

Details

Entity link to 3rd Party SIP entity will not come up. Can Recieve calls from SIP entity but Session Manager is unable to send any calls to it.

Problem Clarification

Entity Link to 3rd Party device not coming up, seeing 500 Server Internal Error
Cause

Adaptation was incorrectly configured with Module Parameters under the Egress URI Parameters
Solution

When configuration adaptations ensure that parameters such as iosrcd, iodstd, fromto are configured under the Module Parameters (as Name-Value Pairs) rather then as Egress URI Parameters.

 

[nortavaya]

Hi KCFLHRC

Thanks for your reply, so you mean that the issue is not in CS1K/NRS side, I forward this solution to the other side team (Avaya red)
Because they said, that the INVITE is not passing through NRS when we call from CS1K phones, then the Session Manager cannot route the call

Thank you

 

[KCFLHRC]

From the solution it appears to be an Adaptation Setting in the NRS in Session Manager

 

[AvayaHE]

What against an integration CS1K to Sessionmanager ?

 

[nortavaya]

Hi AvayaHE,
it is working now, the Session Manager team add some CS1K adaptation on SMGR, and then it works fine

Thank you.