Has anyone run into an issue where single number reach isn't functioning when you call the desk phone? I have no access-lists applied in the Remote Destination Profile and I have all the correct associations for the cisco guide. It just isn't working, I'am using a SIP trunk to a CUBE for outside calling. All normal calling work properly. What determines the CSS that is used when CUCM calls the remote destination profile, what if the desk phone and the remote destination are in the same device profile, if that a possible issue? Thanks
Some things I checked
I have MLPP disabled
Auto call pickup is disabled
The number in the remote destination is in the proper format of an outside call
SNR can be tricky. Here a couple things I have found.
Associate the user with deskphone and line on the deskphone
Create the remote destination Profile, add the line from the deskphone, associate the line to user.
Add the cell phone in to the end point you want it to ring to.
Remember, you will have to adjust the triggers for rings, stopping ring so it does hit the voicemail on the cell side.
On the Device profile, you will need to set the Calling Space for this, or it will not work. This basically tells which gateway to leave out of.
Also, you can not use this for IP phones. For example, call an IP phone and SNR another IP phone. It only works with an external number such as home phone, cell phone, etc.
I have also found, some providers will not allow the caller ID be something other than their own DID block assigned to the trunk it leaves on. For example, if the DID is 408-555-1212 x1212 is on the phone. When you pick up the phone and call me, i see 408-555-1212. But when you say, call foward all calls to your cell phone, your caller ID be sent is your cell phone number, not the 408.555-1212. This throws off the providers PSTN backend switch and they have it locked down to only allow the 408-555-1212. I know for a fact TelePacific is a Broadcom softswitch in the backend and it screws up call fowarding and SNR. They are suppose to release a new patch on their to fix this.. but who knows when.
Watch your gateway for CUCM attempting to dial out. If you DO NOT see it dialing out, at least you kow its a configuration problem in CUCM.