You should make a note that, at the beginning, when you go to create the service, you're creating the EM service itself. You call it the extension mobility cross-cluster service, which is a bit confusing for people who already have EM enabled, but want to enable it cross-cluster. Good vid, though!
@roychoar Hey Rogelio, If you go to the CUCM Admin Page on both home and remote clusters and go to 'Advanced Features' > 'EMCC' > 'EMCC Feature Configuration' > check that you have selected a value for the first field 'Default TFTP Server for EMCC Login Device'. This is shown from around 13:10 onwards and remember to complete it on both home and remote clusters. Hope this helps, John
Hi John: I got an error in the last step of your procedure (the one you execute at 16:00) . When I press the "Update Remote Cluster Now" button in the remote cluster, CUCM replies the following error message: "...Update not performed. EMCC Feature Configuration parameter Default TFTP Server for EMCC Login Device must be configured...." ¿Any hints? It seems that some of the steps you executed on home cluster should also be executed in the remote cluster. Thanks in advance, Rogelio
Hi John: Now I have a different error. The phone rejects the login attempt with error code 37 ("same device name exists on both clusters"). After this, I typed a wrong PIN (on purpose), and the error code was 2 (incorrect PIN), so the visiting cluster seems to be working OK with the home cluster. Coming back to error code 37: ¿why is the system finding a collision of device names? I am sure that devices are unique across clusters. Just in case: I have CUCM8.5.1 Any hints? TIA, Rogelio
Hii John...Good Day .. Thanks for uploading the same.I configured this as per this video and the cisco callmanager administration guide. In this setup when I loggin to one cluster it shows error 23 and second if I try to the second one it shows error 35. Each cluster gets the update of remote one..but cant loggin.. please help me...thanks in advance
Hello John:
Thanks a lot for your help. I will check it out tomorrow and let you know.
Best regards, Rogelio
This is a great video. You're going a bit fast, but who cares, that's what pause and rewind are for =) thanks for going through all of that!!
You should make a note that, at the beginning, when you go to create the service, you're creating the EM service itself. You call it the extension mobility cross-cluster service, which is a bit confusing for people who already have EM enabled, but want to enable it cross-cluster.
Good vid, though!
@roychoar
Hey Rogelio,
If you go to the CUCM Admin Page on both home and remote clusters and go to 'Advanced Features' > 'EMCC' > 'EMCC Feature Configuration' > check that you have selected a value for the first field 'Default TFTP Server for EMCC Login Device'.
This is shown from around 13:10 onwards and remember to complete it on both home and remote clusters.
Hope this helps,
John
Hi John:
I got an error in the last step of your procedure (the one you execute at 16:00) . When I press the "Update Remote Cluster Now" button in the remote cluster, CUCM replies the following error message:
"...Update not performed. EMCC Feature Configuration parameter Default TFTP Server for EMCC Login Device must be configured...."
¿Any hints? It seems that some of the steps you executed on home cluster should also be executed in the remote cluster.
Thanks in advance, Rogelio
Hi John:
Now I have a different error. The phone rejects the login attempt with error code 37 ("same device name exists on both clusters").
After this, I typed a wrong PIN (on purpose), and the error code was 2 (incorrect PIN), so the visiting cluster seems to be working OK with the home cluster.
Coming back to error code 37: ¿why is the system finding a collision of device names? I am sure that devices are unique across clusters.
Just in case: I have CUCM8.5.1
Any hints? TIA, Rogelio
Hii John...Good Day ..
Thanks for uploading the same.I configured this as per this video and the cisco callmanager administration guide.
In this setup when I loggin to one cluster it shows error 23 and second if I try to the second one it shows error 35.
Each cluster gets the update of remote one..but cant loggin..
please help me...thanks in advance