Scenario#47 – Jabber users see ‘offline’ status after logging in

I came across an issue for a client where few of their users would login to Jabber (ver 10.5) and see their presence status as ‘offline’. They won’t be able to change it as well. Other Jabber users will also see them as ‘offline’ even though they are logged in and should be online. That was one issue. Few other users would give ‘false’ presence status like if they are ‘away’ they will be shown online and vice versa. They were on 10.5(2) IM&P which is a fairly new release so I was so sure it cannot be due to … Continue reading Scenario#47 – Jabber users see ‘offline’ status after logging in

Scenario#46 – 9951 SIP phones drop call after 18 seconds

Recently I came across an issue with a new customer deployment where the 9951 SIP phones would drop call after 18s. All other SCCP phones were working fine but only these SIP phones would drop the call.   Call flow: 9951 -> SIP -> CUCM -> SIP -> CUBE Bind commands were in place and the only way I could resolve the issue was forcing RTCP parameter “disabled” under Common phone profile and Enterprise Phone parameters. System -> Enterprise Phone Configuration AND Device -> Device Settings -> Common Phone Profile RTCP DISABLED Continue reading Scenario#46 – 9951 SIP phones drop call after 18 seconds

Scenario#45: 7841 SIP phone in Registration loop

I was working on this customer issue last week where they added a new 7841 phone but it was not registering properly or should I say it was registering briefly before unregistering. Call Manager was 9.1.2.11900-12 which does not support 78XX phones so customer actually applied the device pack cmterm-devicepack9.1.2.12039-1.cop  so that they can add 78XX phones. Looking at the logs I found that it is registering with Pub and not Sub even though Sub was the Primary CCM in Call Manager group. At Pub I can see something like this: Pub: REGISTER sip:192.168.11.2 SIP/2.0 Via: SIP/2.0/TCP 172.18.52.91:51736;branch=z9hG4bK739dd207 From: <sip:49715220XXXXX@192.168.11.2>;tag=544a003629fd000a741be677-22e1dea8 … Continue reading Scenario#45: 7841 SIP phone in Registration loop

Scenario#44 – CME Call Forward to Internal Extension not Working

I came across an interesting issue for a Swiss customer where they were having problem with Call-forward to an internal extension on their CME systems. Call-forward to an internal extension seems quite straight-forward so I checked how telephony-service is configured and found both call-forward patterns as well as transfer-pattern were configured as .T .. so no real issue there. Customer added that it use to work fine before but not working anymore. After asking few questions I found that they recently migrated from ISDN to a SIP provider so all incoming calls are coming on SIP while I was thinking … Continue reading Scenario#44 – CME Call Forward to Internal Extension not Working

Scenario#43 – CUCM 9.1(2) RL/RG Reject Issue

Few weeks back I came across a issue for a customer who are on CUCM 9.12() cluster. The issue was outbound calls not reaching either of the MGCP gateways from a Translation pattern even though both gateways were registered fine with Call manager. I checked the E1s and MGCP status and all was OK. The Route List was reset as well but had no joy. I also did a Reset on MGCP quite few times but had no luck. During test calls I found this in CCM logs: 93958336.006 |18:10:05.348 |AppInfo  |RouteListCdrc::null0_CcSetupReq – Selecting a device. 93958336.007 |18:10:05.348 |AppInfo  |RouteListCdrc::selectDevices … Continue reading Scenario#43 – CUCM 9.1(2) RL/RG Reject Issue

Scenario#42 – CUC not working after adding Secondary Server

I came across an interesting scenario few days back where customer added a CUC Secondary server back to the Cluster but it was not working as it should. Customer had two CUC servers in the cluster in a load-balanced configuration with half of the ports on unity-02(sub) and other half on unity-01(Pub). For some hardware failure the secondary failed and they had to re-build it from Scratch. The problem they were facing was that unity was not taking any calls as the first 80 ports were on unity-02 and for some reason it was not happy. I checked the replication … Continue reading Scenario#42 – CUC not working after adding Secondary Server