Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
When Mobility users call another internal extension from their mobile phones, the caller ID is supposed to show the calling party's internal extension and not the mobile number. CUCM is no longer associating remote destinations with internal extensio...
How can I allow IM and Presence from over the internet without the VPN? I'd like to be able for users to run Jabber IM mobile app without a tunnel due to it hogging battery resources. I have setup a NAT to my CUPS and opened the correct ports (SIP an...
I've had the calendar integration working between CUPS 8.6 and Exchange 2010 for quite sometime, single Exchange EWS gateway on single Presence server. All of a sudden it has stopped working. The Exchange server is reachable and verfied in the Presen...
I am attemping to upgrade Jabber clients from 9.0.1 to 9.0.3 using the web server based auto update that you can specify in the xml config files. When I run check for updates from a 9.0.1 install the software does look for updates but returns that I ...
NAT your internal CUPS server IP on the ASA to a public IP. Create ACL allowing any host to connect to outside IP on ports tcp/udp 5060, tcp 5222, tcp 8443.
Carlo,We're only prepending with Application Dial Rules for things like Jabber, CUPC, etc. No translation patterns or GW level prepend. That is why I questioned how SNR is making the outbound calls without the 9 configured before the 10 digit RD numb...
Carlo,Something must have changed from 8.0 to 8.6. I removed the 9 in the Remote Destination numbers and the CID is now working as it should by showing internal extension rather than mobile number. Back when this system was deployed on 7.X, the 9 had...
Thanks Carlo.CUCM receives the number as 10 digits. The remote destinations are configured as 10 digits with the 9 prepended for PSTN access. No digit manupulation for incoming external calls.It's been working for years and all of sudden quit. It may...
I have changed the Direct Transfer registry setting to All and still getting the CID of the CTI port rather than the Calling Party on transfers. Is there anything else that needs to be modified to get to this work?Thanks,Aaron
