Call Forwarding Not Working. (CUCM 11.x)

[BTCDigitalSignatureProject5690]

I have put call forwarding on my Extension (Forward to  Mobile Number in case of no Response.) either someone call from internally or Externally. 

Now If someone call me from inside the Office (Ext e.g. 212 to my Ext 220), call forwarding is WORKING FINE 

But if someone is call from outside (e.g. 0540024616 to my number 0112684220), call Forwarding is NOT WORKING. 

Below is analyzer from Outside call. 

• Results Summary
• Calling Party Information
• Calling Party = 90112684212
• Partition = Emergency:Internal:Local:National:Mobile:Services:Toll_Free
• Device CSS =
• Line CSS = National_CSS
• AAR Group Name =
• AAR CSS =
• Dialed Digits = 90112684220
• Match Result = RouteThisPattern
• Matched Pattern Information
• Called Party Number = 90112684220
• Time Zone = Etc/GMT
• End Device = BTC_rl
• Call Classification = OffNet
• InterDigit Timeout = NO
• Device Override = Disabled
• Outside Dial Tone = NO
• Call Flow
• Route Pattern :Pattern= 9.01XXXXXXXX
• Positional Match List = 9:0112684220
• DialPlan =
• Route Filter
• Require Forced Authorization Code = No
• Authorization Level = 0
• Require Client Matter Code = No
• Call Classification =
• PreTransform Calling Party Number = 90112684212
• PreTransform Called Party Number = 90112684220
• Calling Party Transformations
• External Phone Number Mask = NO
• Calling Party Mask =
• Prefix =
• CallingLineId Presentation = Default
• CallingName Presentation = Default
• Calling Party Number = 90112684212
• ConnectedParty Transformations
• ConnectedLineId Presentation = Default
• ConnectedName Presentation = Default
• Called Party Transformations
• Called Party Mask =
• Discard Digits Instruction = None
• Prefix =
• Called Number = 90112684220
• Route List :Route List Name= BTC_rl
• RouteGroup :RouteGroup Name= Standard Local Route Group
• PreTransform Calling Party Number = 90112684212
• PreTransform Called Party Number = 90112684220
• Calling Party Transformations
• Called Party Transformations
• Alternate Matches

[George Sotiropoulos]

Hello,

Can you check at the line the CSS at the "Forward No Answer Internal" and the "Forward No Answer External"?

George

[Nithin Eluvathingal]

Isp will block calls if sent with the mobile number as calling number. So on gateway change forwarding settings from originator to first redirect or last redirect number. 

[Nithin Eluvathingal]

Can you paste the debug messages for forwarded calls. so we will have more clarity what calling and called number is send to ISP.

[TONY SMITH]

Check gateway  Device Pool and make sure it has a Local Route Group assigned.  Although the parameter Roger mentions may over-ride this.

[Roger Kallberg]

A few things to check.

1. Is the external call hitting a gateway for the egress path? Reason that I ask is that I see that your using SLRG.
2. If it hits a gateway what do you get for the call going to PSTN? Is it being disconnected by your SP?
3. What is the value of the service parameter "Local route group for redirected calls"?
   
   

[thandoan@cisco.com]

you need to debug on gateway if which calling number is sent out to PSTN. If that is not your Office number (but original caller number), the PSTN provider will block that transfer call

[tieamae97374]

However it does not apprehend when I want to invite a question or make a statement. It's like I'm nonetheless on mute irrespective of whether or not I unmute my cellphone or observe as you can check. Nor does it help with I unmute my webex icon.

[VON CLAWSON]

All great answers above. I would only add that some carriers have the capability of looking at the Diversion Header to be able to forward a call that does not have the from number in the DID range. On the SIP trunk to the CUBE you will want to check "Redirecting Diversion Header Delivery - Outbound" to include the Diversion Header in the SIP invite. The Carrier will see the number they need to see int he Diversion Header and continue the call. Some carriers may need to turn this on for you.