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

 

[Bonker1974]

 

[fondog2]

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.

 

[Bonker1974]

yes this is the first SIP trunk

 

[fondog2]

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.

 

[Bonker1974]

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.

 

[Bonker1974]

@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.

 

[fondog2]

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.

 

[Bonker1974]

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.

 

[fondog2]

https://www.devconnectprogram.com/fileMedia/download/e2006793-dc8c-4b47-a9e9-9a6783f18197

 

[Bonker1974]

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.

 

[fondog2]

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.

 

[Bonker1974]

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.

 

[fondog2]

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

 

[Bonker1974]

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

 

[fondog2]

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.

 

[Bonker1974]

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.

 

[kyle555]

firewall?

 

[Bonker1974]

No firewall.

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

 

[kyle555]

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.

 

[fondog2]

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.