08-05-2016 03:26 AM - edited 03-17-2019 07:44 AM
Hi Guys
I'm struggling to get Skype for Business 2015 working with CUCM 10.5
I followed this exact config guide but I keep getting "your organization does not support calling this number" error on the skype client when trying to dial out.
https://technet.microsoft.com/en-us/library/dn951430.aspx
Please help?
Thanks
M
08-05-2016 03:59 AM
From RTMT, can you please share real time trace for failed call.
Also, where are you getting this error message from CUCM or S4B?
08-05-2016 05:09 AM
Salaam Mohammed
See trace attached
The number (0723779056) is being dialed and not showing in the trace
CUCM IP: 10.1.10.40
SFB IP: 10.1.200.64
Error message is coming from the SFB when trying to dial.
Also I cant see the Cisco phone attempting to dial the number as well
Thanks
Maheer
08-05-2016 05:46 AM
ok this look interesting. Do you have route pattern configured and pointing to s4b sip trunk.
use DNA to trace the called number from cucm and see where its getting lost.
Also, what is you calling phone?
08-05-2016 05:59 AM
Yes route pattern with the gw set to the Skype trunk
DNA Result:
Using a softphone for testing purposes
08-05-2016 06:22 AM
Good. So configuration looks good. Now I don't need sdl trace. From RTMT navigate to real time trace and share the ladder diagram for the call.
Make sure that you have select 60 mins as duration then search for the call. I need to see the SIP message involved in the call.
08-05-2016 06:41 AM
I cant see any detail
So basically when dialing from SFB then the call doesnt even hit the CUCM
08-05-2016 06:43 AM
Can you hit cucm from the machine running the softphone?
Did you add the softphone in cucm? What softphone are you using?
08-05-2016 06:47 AM
If I dial from the Cisco softphone then everything works 100%
When I dial from SFB then nothing happens
Basically trying to configure the "click to call"
08-05-2016 03:17 PM
Can you pull logs from OCS logger from SFB to see what exactly its happening around.
Regards
Nadeem Ahmed
08-06-2016 10:40 AM
Then its S4B problem. I suggest you post this in MS forums to and see if they can help. Unless the message hits CUCM nothing can be checked from CUCM side
08-09-2016 12:17 PM
Did pulled the logs from OCS logger its quite easy to see and understand message from OCS tool and help you figure out where the problem persist and accordingly take appropriate action
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide