×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

SIP Enity Link

SIP Enity Link

SIP Enity Link

(OP)


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

RE: SIP Enity Link

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.

RE: SIP Enity Link

(OP)
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

RE: SIP Enity Link

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

RE: SIP Enity Link

(OP)
The Node name IP are correct

RE: SIP Enity Link

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

RE: SIP Enity Link

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

RE: SIP Enity Link

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?

RE: SIP Enity Link

(OP)
yes it is TCP

RE: SIP Enity Link

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









RE: SIP Enity Link

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

RE: SIP Enity Link

(OP)
See Network region100




RE: SIP Enity Link

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

RE: SIP Enity Link

(OP)

RE: SIP Enity Link

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

RE: SIP Enity Link

(OP)
I have done that.

RE: SIP Enity Link

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

RE: SIP Enity Link

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

RE: SIP Enity Link

(OP)


RE: SIP Enity Link

Display locations and look at the entry to the right.

RE: SIP Enity Link

(OP)

RE: SIP Enity Link

Is this your first SIP trunk you have built on your system? Let me know if it is I have a step by step that will help you considering I can't see or touch all the pieces in your switch.

RE: SIP Enity Link

(OP)
yes this is the first SIP trunk

RE: SIP Enity Link

Ahhh. OK that makes a lot more sense. Private message me your info and I'll send you a doc when I get home tonight. One of the things it covers is the proxy route selection. You are really close. Build a route pattern for this SIP trunk and add that route pattern to the location. Now I'm not sure how you plan on using the SIP trunk but if you are connecting to another switch you will need AAR to route the call over the SIP trunk to test. Or for an SBC. Make sure you set up you private/public unknown tables too.

RE: SIP Enity Link

(OP)
Thanks , I will PM you. Well I'm trying to establish the sip trunks between the CM and the Session manager.It is usually straight forward I just don't understand what is going on here.

Thanks for all your help thus far. I really appreciate it.

RE: SIP Enity Link

(OP)
@fondog2- I don't believe I can PM you. I looked all over the site I don't see how I can PM you.

Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.

RE: SIP Enity Link

Try this link. Keep in mind this is TLS but keep your ports at 5060 for TCP and you should be good. A lot of good information in this doc.

RE: SIP Enity Link

(OP)
No Link in your post. can you send it again please.

Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.

RE: SIP Enity Link

(OP)
Hi Fondog2,
I have done everything to the T with that doc but still no doing. I did nos more research I most believe this issue is a certificate issue. I need to figure out how to import smgr certificate into the cm truststore.

DO you have any idea how that is done?

Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.

RE: SIP Enity Link

Wouldn't be a cert issue unless you are configuring TLS. You did verify you have SIP licenses? I didn't see any screen shots.

RE: SIP Enity Link

(OP)
Sorry for the late response was traveling.




Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.

RE: SIP Enity Link

Did you ever set a proxy selection route pattern? Also what does your route pattern look like?

RE: SIP Enity Link

(OP)

Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.

RE: SIP Enity Link

Change the numbering format to lv0 pvt then verify your trunk groups are set to private unknown then verify you have entries for your extensions for this trunk in the private unknown table.

RE: SIP Enity Link

(OP)
I have made the changes but still the same

Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.

RE: SIP Enity Link

firewall?

RE: SIP Enity Link

(OP)
No firewall.

Leadership determines the direction of the company. Organization determines the potential of the company. Personnel determines the success of the company.

RE: SIP Enity Link

I maintain what I said earlier - that SM isn't getting answers to its options pings towards CM.

What you can do is turn off entity link monitoring in the SIP entity. That'll at least make SM toss calls at it.

The way entity link monitoring works is that, when enabled, options pings are sent every few minutes from SM to the far end. If the far end replies, SM considers the link up. If the far end doesn't reply, SM considers the link down and will be able to more quickly jump to the next choice.

Without entity link monitoring, suppose you had 2 routing policies to 2 SBCs and the first choice was down, SM would send the invite to the first one, even though it's down, and still forcibly wait for a timeout for every call before trying the second choice.

What I'm saying is that if you disable entity link monitoring, you should be able to see SM pitch a call at CM and work with that. The 408 Timeout thing is making me feel like it's more layer 3 than layer 7.

RE: SIP Enity Link

kyle555 might be right on the layer 3. Did you verify that ports 5060 as well as all the other ports on the matrix are open for you? I'd really like to see a sniff of this. We all would have a lot more to troubleshoot with.

RE: SIP Enity Link

Look at the flows on that traces you posted on the 13th. There are no OPTIONS messages flowing from the SM toward the direction of the CM. Only the 200 OK response flows towards the CM. That isn't correct behavior. It's backwards of what it should be. Double check your IP addressing in the entity set ups. And I mean down all the way to terminal connect to the Linux and run ifconfig to validate the underlying structure too. You have something majorly wrong with an address or two somewhere.

Plus from that same day you have a screen cap from SMGR that appears to show the SM built as an entity. You don't do that. You build the SM. Then you build entities for the SM to link to. You might be confusing things all to heck and causing recursive routing with that one.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close