SIP Enity Link

[Bonker1974]

Hi All,
I have an Issue I can't get my Entity link between the session manager and the CM to come up. The SIg group is up and the trunks are in service but the TCP link will not come up.

CM 7.0
SMGR 7.1

 

[kyle555]

CM will mark a sig group up if it gets any SIP response from the far end node name. 404 not found, unauthorized, whatever - that's "up" as far as CM is concerned.

SM's entity link monitoring is telling you when it sends an OPTIONS ping to CM, it gets no response, that that's why it's 408 and timeout and down.

Typically CM won't respond to SIP messages for things it doesn't have a sig group for. Hypothetically, if you typed in CMs IP wrong in the entity in SMGR, then SM could get that timeout and if you programmed your sig group right in CM, CM would get some response to it's options pings from SM (even though SM has no config/wrong config to route calls) and CM would show it happy and have a sig/trunk in service.

 

[Bonker1974]

When it cm try to register I get the below trace




192.168.16.244:24948 ──TCP─► 192.168.16.246:5060 │
12:4├──────────────────────────────────────────────────────────────────────┤olin
12:4│NOTIFY sip:cm-resubscribe@colina.com SIP/2.0 │on d
│From: <sip:colina.com>;tag=f0c02cbe6b6741e9a42c0c29e84464 │
│To: <sip:cm-resubscribe@colina.com> │
│Call-ID: f0c02cbe6b6741e9a42c0c29e84464 │
│CSeq: 1 NOTIFY │
│Max-Forwards: 70 │
│Via: SIP/2.0/TCP 192.168.16.244;branch=z9hG4bKf0c02d186b6741e9a42d0c29│
│e84464 │
│User-Agent: Avaya CM/R017x.01.0.532.0 │
│Contact: <sip:192.168.16.244;transport=tcp> │
│Route: <sip:acm-routed@192.168.16.246;transport=tcp;lr> │
│P-Asserted-Identity: <sip:192.168.16.244> │
│Subscription-State: terminated │
│Content-Length: 0






192.168.16.246:5060 ──TCP─► 192.168.16.244:24948 │on d
├──────────────────────────────────────────────────────────────────────┤
│SIP/2.0 481 Call or Transaction does not exist │
│Call-ID: f0c02cbe6b6741e9a42c0c29e84464 │
│CSeq: 1 NOTIFY │
│From: <sip:colina.com>;tag=f0c02cbe6b6741e9a42c0c29e84464 │
│To: <sip:cm-resubscribe@colina.com>;tag=6559174210778659_local.1530299│
│315903_12185373_12185572 │
│Via: SIP/2.0/TCP 192.168.16.244;branch=z9hG4bKf0c02d186b6741e9a42d0c29│
│e84464 │
│Av-Global-Session-ID: 865e95e0-6b67-11e9-9b54-000c29e38981 │
│Server: AVAYA-SM-7.1.0.0.710028 │
│Content-Length: 0

 

[fondog2]

Verify your node names/IP are correct and verify you have the correct far end node name in the signaling group.

 

[Bonker1974]

The Node name IP are correct

 

[fondog2]

What about the far end node name of the signaling group?

 

[Bonker1974]

The Far end 192.168.16.246 which is the SM ip address
The Near End is 192.168.16.244 Procr IP

 

[fondog2]

One of these is the issue, Node names are incorrect or mis-matched, far end network region or the far end domain name. This is a TCP SIP trunk correct?

 

[Bonker1974]

yes it is TCP

 

[Bonker1974]

If you look at the information you will see the IP address are correct.

 

[fondog2]

Ok, is network region 100 connected to the network region procr is in?

 

[Bonker1974]

See Network region100

 

[fondog2]

Status the signaling group for the trunk and post it please.

 

[Bonker1974]

 

[fondog2]

Also turn off Initial IP to IP Direct Media to no on the signaling group. This will cause issues down the road.

 

[Bonker1974]

I have done that.

 

[Bonker1974]

When I busy the signaling group and return it to service I can see this "481"

 

[fondog2]

DO you have a proxy route pattern selection for this location?

 

[Bonker1974]

 

[fondog2]

Display locations and look at the entry to the right.