CUCM - Skype for Business SIP Issue

[smccloud1]

Hi,

I have set up a sip trunk between a CUCM and a Skype for Business platform but have an issue whereby calls work successfully from Skype to CUCM but it doesn't work for CUCM to Skype.

Everything is configured as per the cisco document for integrating Skype for Business 2015 and CUCM 10

Any ideas what could cause this?  Any SIP settings?

Thanks,

Shaun

[Adarsh Chauhan]

Hi,

That description is not very helpful.

What is the user experience?

A quick tip, after creating a SIP trunk it should always be reset.

Can you give us logs from call manager through RTMT?

Regards,

Adarsh Chauhan

[smccloud1]

Adarsh,

Here are the logs you requested.

[smccloud1]

Adarsh,

Right now I am able to call from Skype for Business to CUCM & to the outside world.  I cannot call from CUCM or the outside world to Skype for Business.  Logs are attached.

[Adarsh Chauhan]

Hi,

can you give me the calling number and called number and what happened when you dialed the number? 

Regards,

Adarsh Chauhan

[smccloud1]

Adarsh,

I am calling from 3612 and calling 3690.  I get a busy signal.

[Adarsh Chauhan]

Hi,

Isn't 3690  suppose to be a route pattern associated with the SIP trunk pointing to SFB.

how many 3690 patterns you have (check here:CM_Administration--> Call_Routing-->RoutePlanReport)?

Currently CUCM is routing call to 3690 in PCP_Base_PT. Is this your Route pattern?

Also what is this pattern smccloud@unimax.local_SFBsmccloud?

Regards,

Adarsh Chauhan

[smccloud1]

Adarsh,

My current route pattern is for 369X to go to my SFB Route List.  Attached is the RoutePlanReport for 3690.

smccloud@unimax.local is SFB SIP URI.  From what I read that is how you are supposed to forward a call from CUCM to SFB.  If this isn't right, I will gladly change it once we are able to determine the correct way.

[Adarsh Chauhan · Accepted solution]

Hi,

You have got an overlapping pattern here.

3690 PCP_Base_PT

369X PCP_Base_PT

call is going to 3690 Directory number instead of the route pattern.

if you can (easiest way) temporarily delete 3690 director number and make a test call.

Let me know what happens.

Please rate and mark if helpful

Regards,

Adarsh Chauhan

[smccloud1]

Adarsh,

With the 3690 Directory Number deleted, I still get a busy signal when dialing it from my Cisco extension.  However, it does take longer to get the busy signal than it did before.  Using RTMT I can see the call hitting the SFB server.  I think it might be an issue with the SFB server routing the call to my client now, but I'm not sure.  Updated logs are attached.  Please let me know if you agree with my assessment that the issue is probably on the SFB side now.

[Adarsh Chauhan]

Hi,

it seems that you have formed a call loop here.

I can see call coming in for 3690 and then being routed again back to the SFB.

Please note on SFB there shouldn't be a pattern matching 3690 and routing call back to CUCM.

in short the dial-plan of the two vendor should be unique or some kind of translation needs to be done.

Having said that, my question is, what is 3690 on SFB (it shouldn't be pattern routing call back to cucm)?

Please rate and mark correct if helpful

Regards,

Adarsh Chauhan

[Jaime Valencia]

What's the document that you're following?

[smccloud1]

Jamie,

I am following http://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/interoperability-portal/skyp-for-business.pdf