I'm trying to implement SNR on a new 8.0.2 CMBE and it's not quite working. Here's what I did already:
Defined Enterprise and Service parameters
Verified the mobility service is running
Enabled Mobility on an end user which is associated with a desk phone. Selected this same phone as the primary device.
Verified device is associated with user
Verified line on device is associated with user
Created new softkey
Created new remote destination profile, has international CSS and I see my associated remote destinations. Associated with correct user id. Added same primary line as for the desk phone to this profile (shared line)
Created remote destination of my cell phone, used 91... which is the same way i would dial it straight from my phone.
Checked Mobile Phone and Enable Mobile Connect. Also set it to always ring all the time.
Checked the line association box
Created an access list (didn't think I needed one though) with just !. I also tried one for 510! (my calling party area code).
Here's what happens:
1. Call my desk phone from this outside number. It rings as usual but my cell phone does not.
2. I answer the call and hit the 'mobility' softkey which posts a message to send call to mobile phone. I hit the select softkey but, again, nothing happens on my cell phone.
The CM trace logs show messages. The think I really notice was mention of me missing a '+' before my internal directory number. Also Remote Destination, could not find SNRD Pid.
18:14:01.420 |ConnectionManager - wait_AuDisconnectRequest ERROR:NO ENTRY FOUND IN TABLE,CI(25314760,0),dcType=1,IFCreated(0,0),PID(0-0,0-0),IFHandling(0,0),MCNode(0,0)|1,100,49,1.1553958^172.17.18.60^SEP001360E41878
18:14:01.421 |MatrixControl:updatePartyMediaCoordinatorNodeId: party1 videoCapable=0, party 2 videocapable=0|1,100,49,1.1553958^172.17.18.60^SEP001360E41878
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...