Hi, We use CUCM6.1.2,
1 publiser, 1 subscriber, 150+ phones (7941 and 7961) + extension mobility on all phones.
publisher 10.0.0.11
subscriber 10.0.0.21
I have checked what happens if one callmanager failes, and how it's setup now, it is ready for improvement.
How would you make this setup (more)failsave?
1. TFTP for booting a phone
in our w2k3 server, scope option 150 was set to the ip of the publisher. If that one failes after a powerfailure, non off the phone are able to boot...
I put a second ip in, the ip of the subscriber.
After testing: phones can boot from both IPs
So that fine now?
2. Extension mobility
Device -> Device settings -> Phone Services -> Extention Mobility.
This url connects to So if the subscriber fails, no phone is able to login or logout.
I red an artical of using DNS:
Creating the same hostname for both IP's, roundrobin 0 secs and putting the hostname in the url instead of the IP.
But, roundrobin is good for this: if an ip is not pingable: the phone doesn't know this and still tries that ip address. So failing to get a url back, it cannot login.
(stupid if I may so, is this:
DNS syncs itself to other DNS servers within the same domain
DHCP is not able to do that. It's like to try if an ip is avalailable, if not 'okay, you may use that address'.
But DNS is at the other hand not able to do such a check.
grrr, always something stupid;-(
)
3. URL's
System -> Enterprise Parameters -> Phone URL Parameters
All entries are directed to the ipaddress of the publisher.
So if the publisher fails? (a bit the same as 2)
so, what are you using in your envirnment to keep it working?
1 publiser, 1 subscriber, 150+ phones (7941 and 7961) + extension mobility on all phones.
publisher 10.0.0.11
subscriber 10.0.0.21
I have checked what happens if one callmanager failes, and how it's setup now, it is ready for improvement.
How would you make this setup (more)failsave?
1. TFTP for booting a phone
in our w2k3 server, scope option 150 was set to the ip of the publisher. If that one failes after a powerfailure, non off the phone are able to boot...
I put a second ip in, the ip of the subscriber.
After testing: phones can boot from both IPs
So that fine now?
2. Extension mobility
Device -> Device settings -> Phone Services -> Extention Mobility.
This url connects to So if the subscriber fails, no phone is able to login or logout.
I red an artical of using DNS:
Creating the same hostname for both IP's, roundrobin 0 secs and putting the hostname in the url instead of the IP.
But, roundrobin is good for this: if an ip is not pingable: the phone doesn't know this and still tries that ip address. So failing to get a url back, it cannot login.
(stupid if I may so, is this:
DNS syncs itself to other DNS servers within the same domain
DHCP is not able to do that. It's like to try if an ip is avalailable, if not 'okay, you may use that address'.
But DNS is at the other hand not able to do such a check.
grrr, always something stupid;-(
)
3. URL's
System -> Enterprise Parameters -> Phone URL Parameters
All entries are directed to the ipaddress of the publisher.
So if the publisher fails? (a bit the same as 2)
so, what are you using in your envirnment to keep it working?