For the 401 error with the REST call, you need to upload the server certificate you are making the REST call to into UCCX Tomcat-Trust and restart the Tomcat service.  ... View more

I was having the same error on all my clusters I was trying to log into. My problem was fixed by checking something that now seems obvious that I looked over several times. In Advanced Features -> Cluster View I did not have  the enable checkbox for EMCC and PSTN Access checked.  Even though it showed remotely activated and passed the EMCC validation test what ultimately allowed me to log in was checking the “enable” checkbox and then clicking the “Update EMCC Remote Cluster Now” on all the clusters. Then I was able to log in.  ... View more

I was having the same error on all my clusters I was trying to log into. My problem was fixed by checking something that now seems obvious that I looked over several times. In Advanced Features -> Cluster View I did not have  the enable checkbox for EMCC and PSTN Access checked.  Even though it showed remotely activated and passed the EMCC validation test what ultimately allowed me to log in was checking the “enable” checkbox and then clicking the “Update EMCC Remote Cluster Now” on all the clusters. Then I was able to log in.  ... View more

I was having the same error on all my clusters I was trying to log into. My problem was fixed by checking something that now seems obvious that I looked over several times. In Advanced Features -> Cluster View I did not have the enable checkbox for EMCC and PSTN Access checked.  Even though it showed remotely activated and passed the EMCC validation test what ultimately allowed me to log in was checking the “enable” checkbox and then clicking the “Update EMCC Remote Cluster Now” on all the clusters. Then I was able to log in.  ... View more

Great article. +5    This helped me isolate a SIP issues coming from a CUCM VM. I will add SSH can be enabled from Vsphere under the Configuration -> Software pane -> Security Profile -> Properties -SSH -> start SSH ... View more

I found making 4-digit short dial for +e164 DNs in esrst mode difficult to figure out.   One cannot add a translation-profile to the esrst voice register pool like with "mode srst" in fact one cannot choose "mode srst" at all, only esrst or cme. I used the following method to expand my 5[78].. range out to the full +e164 the phones have. These numbers can be seen as the created dial-peers using the "show sip-ua status registrar" as shown below:   RT01#show sip-ua status registrar Line          destination      expires(sec)  contact transport     call-id               peer ============================================================ +12224445759  10.64.150.36     283           10.64.150.36 UDP           0041d2f8-0f92018d-20a58720-0994d939@10.64.150.36                   40024   voice translation-rule 1 Rule 1 /^\(5[78]..\)$/ /+1222444\1/ ! ! voice translation-profile srst-expand-e164 translate called 1 ! dial-peer voice 10 voip session protocol sipv2 destination-pattern 5[78]..$ translation-profile outgoing srst-expand-e164 session target ipv4:10.64.31.251     <<<<This is the router, the same IP SIP is bound to dtmf-relay rtp-nte sip-kpml codec g711u no vad   Calls from SIP phones to 5700-5800 will expand out to +12224445000 and catch the dial-peers of the devices registered in esrst mode.   I hope this helps others. ... View more

I found making 4-digit short dial for +e164 DNs in esrst mode difficult to figure out.   One cannot add a translation-profile to the esrst voice register pool like with "mode srst" in fact one cannot choose "mode srst" at all, only esrst or cme. I used the following method to expand my 5[78].. range out to the full +e164 the phones have. These numbers can be seen as the created dial-peers using the "show sip-ua status registrar" as shown below:   RT01#show sip-ua status registrar Line          destination      expires(sec)  contact transport     call-id               peer ============================================================ +12224445759  10.64.150.36     283           10.64.150.36 UDP           0041d2f8-0f92018d-20a58720-0994d939@10.64.150.36                   40024   voice translation-rule 1 Rule 1 /^\(5[78]..\)$/ /+1222444\1/ ! ! voice translation-profile srst-expand-e164 translate called 1 ! dial-peer voice 10 voip session protocol sipv2 destination-pattern 5[78]..$ translation-profile outgoing srst-expand-e164 session target ipv4:10.64.31.251     <<<<This is the router, the same IP SIP is bound to dtmf-relay rtp-nte sip-kpml codec g711u no vad   Calls from SIP phones to 5700-5800 will expand out to +12224445000 and catch the dial-peers of the devices registered in esrst mode.   I hope this helps others. ... View more

I found making 4-digit short dial for +e164 DNs in esrst mode difficult to figure out.   One cannot add a translation-profile to the esrst voice register pool like with "mode srst" in fact one cannot choose "mode srst" at all, only esrst or cme. I used the following method to expand my 5[78].. range out to the full +e164 the phones have. These numbers can be seen as the created dial-peers using the "show sip-ua status registrar" as shown below:   RT01#show sip-ua status registrar Line          destination      expires(sec)  contact transport     call-id               peer ============================================================ +12224445759  10.64.150.36     283           10.64.150.36 UDP           0041d2f8-0f92018d-20a58720-0994d939@10.64.150.36                   40024   voice translation-rule 1 Rule 1 /^\(5[78]..\)$/ /+1222444\1/ ! ! voice translation-profile srst-expand-e164 translate called 1 ! dial-peer voice 10 voip session protocol sipv2 destination-pattern 5[78]..$ translation-profile outgoing srst-expand-e164 session target ipv4:10.64.31.251     <<<<This is the router, the same IP SIP is bound to dtmf-relay rtp-nte sip-kpml codec g711u no vad   Calls from SIP phones to 5700-5800 will expand out to +12224445000 and catch the dial-peers of the devices registered in esrst mode.   I hope this helps others. ... View more

Great article. Saved my weekend! ... View more

This was exactly what I needed for moving messages in unrestricted unity connection migration. Thank you ... View more

This was exactly what I needed for moving messages in unrestricted unity connection migration. Thank you ... View more