Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

Call Search Space Issues with Extension Mobility

I have a customer running CCM 3.2(2c) spG who has a Calling Search Space applied to his phones such that when no-one is logged into the phones, the can only make internal nad 911 calls.

The CSS applied to the Line(s) on a users Device Profile allows full access to LD and International calling.

When a user is logged into a phone and uses the phone to forward their line to their cell phone (a local call) every thing works fine.

On the other hand, if the same users browses to the CCMUSER page, logs in and selects their device profile and then does a call forward all to their cell phone, a different result is achieved. Now when their line is called, the caller receives a message back saying that the line is not in service. As you can see from the attached trace, the forward is being blocked since the calling search space being applied is the one which only has internal and 911 calling rights.

In the attached trace, the phone has css_TOR1_Local which has access to the partitions par_911 and par_TOR1_Local (which allows internal calls only).

The lines have css_TOR1_International_Restricted which allows local and most LD and International calls.

The number 416-508-9551 calls 905-212-2050 which is call forward to 416-420-9328. Of significance is "DialingPartition=par_Tor1_Local*". In the successful trace (when the user used the phone to call forward) this same line says: "DialingPartition=par_Tor1_International_Restricted*".

One would think that since the user went to their device profile and set call forward, css_Tor1_International_Restricted would apply.

My question really boils down to this: When you place a css on a phone and it's lines, calls made from that phone use the amalgamation of the two css' to determine the users access rights. How does this work with device profiles and call forwarding and why does the treatment differ depending on if the user used the phone or the ccmuser page to do the call forwarding?

Call Trace

-------------

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManager|PretransformCallingPartyNumber=4165089551*|CallingPartyNumber=4165089551*|DialingPartition=par_Tor1_Local*|DialingPattern=9.@*|DialingRoutePatternRegularExpression=(9)([2-9]X[02-9])([2-9]XX)(XXXX)*|DialingWhere=*|PatternType=National*|PotentialMatches=NoPotentialMatchesExist*|DialingSdlProcessId=(2,87,1)*|PretransformDigitString=94164209328*|PretransformTagsList=ACCESS-CODE:LOCAL-AREA-CODE:OFFICE-CODE:SUBSCRIBER*|PretransformPositionalMatchList=9:416:420:9328*|CollectedDigits=4164209328*|UnconsumedDigits=*|TagsList=LOCAL-AREA-CODE:OFFICE-CODE:SUBSCRIBER*|PositionalMatchList=416:420:9328*|VoiceMailbox=*|VoiceMailCallingSearchSpace=*|VoiceMailPilotNumber=*|DisplayName=*|RouteBlockFlag=BlockThisPattern*|InterceptPartition=*|InterceptPattern=*|InterceptWhere=*|InterceptSdlProcessId=(0,0,0)*|InterceptSsType=0*|InterceptSsKey=0

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerDigit analysis: Changed VoiceMailBox =

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerEnvProcessCdr::wait_DbCdrReq

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerEnvProcessCdr::wait_DbCdrReq DETAILED Entries 10100, Inserts 10100, ZeroCalls 0, StartRecords 0, Default 0

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerEnvProcessCdr::outputCdrData

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerEnvProcessCdr::outuptCdrHeader

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerEnvProcessCdr::formatCdrHeader_FieldNames

tor1cm1-Cluster 05/14/2003 12:56:23.637 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerEnvProcessCdr::formatCdrHeader_FieldTypes

tor1cm1-Cluster 05/14/2003 12:56:23.647 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerEnvProcessCdr::formatCdrData

tor1cm1-Cluster 05/14/2003 12:56:23.647 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerDelete entries from TransTable, now this table has 3 entries

tor1cm1-Cluster 05/14/2003 12:56:23.647 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerForwardManager - wait_SsRedirectCallErr - DestParty= 0x20064A1, CallKey= 0x1173

tor1cm1-Cluster 05/14/2003 12:56:23.647 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerForwardManager - findCallBySsParty - Found entry for party= 0x20064A1, CallKey= 0x1173

tor1cm1-Cluster 05/14/2003 12:56:23.647 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerForwarding - awaitingCallResponse_SsRedirectCallErr Code= 3, Processing - CallKey= 0x1173

tor1cm1-Cluster 05/14/2003 12:56:23.647 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerForwarding - sendClearCallReq - CallKey= 0x1173, PartyId= 0x20064A1

tor1cm1-Cluster 05/14/2003 12:56:23.647 10.160.61.14 10.160.61.11 Trace 2,100,51,1.35676 Cisco CallManagerForwarding - awaitingCallResponse_SsRedirectCallErr NoAns - Dest out of order or unknown Play re-order. - Party= 0x20064A1, CallKey= 0x1173

1 REPLY
New Member

Re: Call Search Space Issues with Extension Mobility

The calling search space for the device profile is only present when a user is logged into the physical device. When you setup your login and logout service on the phone the device is hotelling a profile. So in essence the device could actually reside in a different physical location. i.e. Physical phone in D.C. is for all purposes in Chicago. When the device has noone logged into it then it uses it's default device profile which is in a restricted CSS. When the call manager sets up the call it doesn't care what calling search space it is in at the moment. It just knows to forward calls offered to XXXX DN to 19725551212.

If the phone is not hotelling a profile for gateway access then you will see the call fail.

I do not recommend setting up a default device profile that has access to the gateway because you will have undermined the need for EM and toll restriction.

Hope this all made sense,

James

268
Views
0
Helpful
1
Replies
CreatePlease to create content