cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1874
Views
0
Helpful
11
Replies

CUCM Skype For Business not working

Maheer Brown
Level 1
Level 1

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

11 Replies 11

From RTMT, can you please share real time trace for failed call.

Also, where are you getting this error message from CUCM or S4B?

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 

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?

Yes route pattern with the gw set to the Skype trunk

DNA Result:

Cisco Unified Communications Manager Dialed Number Analyzer Results

  • Results Summary
    • Calling Party Information
      • Calling Party = 923
      • Partition = Skype_PT:IPMA:SprkE_HQ:WH:OPA:HQ_ITL
      • Device CSS =
      • Line CSS = Skype
      • AAR Group Name =
      • AAR CSS =
    • Dialed Digits = 0723779056
    • Match Result = RouteThisPattern
    • Matched Pattern Information
      • Pattern = XXXXXXXXXX
      • Partition = Skype_PT
      • Time Schedule =
    • Called Party Number = 0723779056
    • Time Zone = Etc/GMT
    • End Device = skype_1
    • Call Classification = OffNet
    • InterDigit Timeout = NO
    • Device Override = Disabled
    • Outside Dial Tone = NO
  • Call Flow
    • Route Pattern :Pattern= XXXXXXXXXX
      • Positional Match List = 0723779056
      • DialPlan =
      • Route Filter
        • Filter Name =
        • Filter Clause =
      • Require Forced Authorization Code = No
      • Authorization Level = 0
      • Require Client Matter Code = No
      • Call Classification =
      • PreTransform Calling Party Number = 923
      • PreTransform Called Party Number = 0723779056
      • Calling Party Transformations
        • External Phone Number Mask = NO
        • Calling Party Mask =
        • Prefix =
        • CallingLineId Presentation = Default
        • CallingName Presentation = Default
        • Calling Party Number = 923
      • ConnectedParty Transformations
        • ConnectedLineId Presentation = Default
        • ConnectedName Presentation = Default
      • Called Party Transformations
        • Called Party Mask =
        • Discard Digits Instruction = None
        • Prefix =
        • Called Number = 0723779056
    • Device :Type= SIPTrunk
      • End Device Name = skype_1
      • PortNumber =
      • Device Status = UnKnown
      • AAR Group Name =
      • AAR Calling Search Space = Skype
      • AAR Prefix Digits =
      • Call Classification = Use System Default
      • Calling Party Selection = Originator
      • CallingLineId Presentation = Default
      • CallerID DN =
  • Alternate Matches
    • Note: Information Not Available

Using a softphone for testing purposes

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.

I cant see any detail

So basically when dialing from SFB then the call doesnt even hit the CUCM

Can you hit cucm from the machine running the softphone?

Did you add the softphone in cucm? What softphone are you using?

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" 

Can you pull logs from OCS logger from SFB to see what exactly its happening around.

Regards

Nadeem Ahmed

Br, Nadeem Please rate all useful post.

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

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

Br, Nadeem Please rate all useful post.