SIP Trunk issue between CS1K (NRS) and 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.

 

[bignose21]

Why still using an NRS if you have a session manager? Anyway what sort of NRS is a Linux Proxy or a VXWorks Redirect server? The call is sent to the session manager have you got CS1000 adaptation on the link, also depending on call type is there adaptation for SIP URI usually say a CDP call from CS1K might have an inbound adaptation to recognize the context cdp.udp and say add some digits on the front end this can then be recognized on the outbound adaptation to add the URI back in if the destination is CS1K.

 

[nortavaya]

Hi bignose21

Thanks for your reply, the NRS is located on the site 1 (with CS1K) and the session Manager is located on the site 2 (Avaya Aura)
I don't believe you can build the SIP Trunk between site 1 and site 2 without using NRS

I find some Avaya document, all are talking about configuration of NRS when creating SIP Trunk between CM and CS1K

Thank you

 

[bignose21]

What version of cs1k you on we been using just session manager since 2012

 

[bignose21]

So we have only used session manager since we upgraded all cs1k to 7.5 (now on 7.6 SP 10). At time using SM 6.0 now 6.3 and moving to 8.0.

There is a compatibility matrix for red to blue on Avaya.

If you are at right level then just add cs1k node address as a sip entity, apply the cs1k adaptation to it (used if you want to maintain calltypes for sip uri etc.). Put session manager in for your sip proxy in the node settings and turn off allows registration also turn off failsafe NRS in the node. If you need NCS for GR sets then in inventory add a CS1000 TPS and put the Node IP of the CS1k under node. Then in Session Manager config there is a bit for NRS apps you can put leading digits and 3 points of registration.

 

[nortavaya]

Hi bignose21

The CS1K version : 7.6 but without SP10 yet
As I understand, you mean that we can only add the node IP adresse of CS1K (site 1) as SIP Entity on the Session Manager (site 2)? without building any DCH (DCIP) or configuring NRS Endpoints,domains...etc and all of this things ?

For the NCS/GR we don't have it for this customer
Do you have any document that describe the steps to follow for linking CS1K (7.6) to SM ?

Thank you.

 

[bignose21]

SP10 is to support smgr 8.0 if you look at the matrix it gives you the Smgr releases for each SP

 

[bignose21]

You still build SIP trunk just the same on CS1K as you would for NRS. Guessing that you use the System Manager as your security server for the CS1K and you don't have a separate UCM. In the CS1K node go into the SIP Gateway settings the SIP Domain needs to match the one configured in the SM Routing and set the Proxy Server Route 1 primary to session manager, and if you have a second session manager set the secondary (un check the support registration). Take note of what transport you use TCP/UDP and the port 5060 etc. You can also go in the TPS settings and put the session manager(s) in the NCS settings (but sounds like you are not using this).

In the SMGR add a CS1000 Adaptation module (CS1000Adapter) in here you can put in support for SIP URI if required. Add a SIP entity using the FQDN or IP of the CS1K Node, the CS1000 Adaptation, for the entity links setup the trust to match whats in the CS1K node, say CS1K to Session Manager TCP/5060 for example. The add a routing policy for the endpoint and then assign digit patterns to the routing pattern.

The way the adapter supports SIP URI as thats about the hardest bit is for example:

in the adapter matching pattern "x" phone context "cdp.udp" delete 0 insert 555
then when you add the digit patterns it would be 555xxxx routed to another endpoint
If it was going to another CS1K endpoit you could match 555 phone context "cdp.udp" delete 3

This would allow you to add the SIP URI for CDP calls back to calls between CS1K's for example, the same adapter could be used for all CS1K's.

good thing about using SM is obviously use traceSM to look at all the sip messaging in one place.

 

[bignose21]

The attached is the compatibility matrix that shows the CS1K SP required for different levels of SMGR/SM. I have seen another document but can't find it that states SP10 supports SMGR/SM 8.0.

 

[nortavaya]

Hi bignose21,

Thanks for your reply and the procedure, it is very clear now if we want to configure the Node IP as SIP Entity on SM

But, now it works fine through the NRS, the issue is resolved by doing some changes and adaptations on the SIP Entity yesterday

Thanks for you time and have a good day

Regards.