The 46xx series phones have a dual gatekeeper, which means they can re-register themselves with a secondary server if the primary server failes. This works with the Communation Manager and Definity based systems, but so far I didn't get a definite answer whether this is possible or not with an IP Office system. Did anyone try this or have an answer to this question?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
46xx re-registration
- Thread starter siftach
- Start date
- Thread starter
- #3
- Thread starter
- #5
The 46xx will try to register with another CM media gateway if they are working in a CM setup. However it is unclear if they will do the same with IPOs. They should, as long as both primary and secondary IPOs have the same extension setup, but I guess I'll have to get my hand on a 46xx phone and test it myself.
As for having this feature in the 56xx - I don't believe Avaya will do it, but you can use a 46xx phone instead - they cost the same and give you the same features on IPO.
As for having this feature in the 56xx - I don't believe Avaya will do it, but you can use a 46xx phone instead - they cost the same and give you the same features on IPO.
- Thread starter
- #7
I think it has a dual gate keeper. How will this enable the phone to re-register on a secondary IPO I don't know, but I read someplace it is possible in a SCN environment when using an external DHCP. I want to test it in a non SCN environment. My biggest problem is that Avaya's office here know nothing about IPO and the main distributor of IPO have only one support person and he can't give me answers.
It could be possible if you have a switch/router on the network that senses that the destination is unavailable and sends the traffic to a secondary location.
Had this on sketch, but in the end the customer wasn't willing to pay for the solution so it never left the drawingboard.
Seems Avaya usually thinks that if the customer wants this kinda fallback they should buy a CM solution so any solution using IPOs will be homebuilt and unsupported
Had this on sketch, but in the end the customer wasn't willing to pay for the solution so it never left the drawingboard.
Seems Avaya usually thinks that if the customer wants this kinda fallback they should buy a CM solution so any solution using IPOs will be homebuilt and unsupported
- Thread starter
- #9
With the CM it depends on how you have it setup, you can have the second gateway setup in the Option 176 of the DHCP scope, or depending upon what version of CM, when the extension logs on, it will grab it's "survivable Node". this will come into play if it loses it's connection to the CM, it will attempt to register to another LSP.
The IPOffice does not allow this configuration, but you can try it via the DHCP, this will allow the phone to hunt till it gets to a valid pbx, but like you said, you'd need a whole seperate IPO with the same extension range in place.
>mike
The IPOffice does not allow this configuration, but you can try it via the DHCP, this will allow the phone to hunt till it gets to a valid pbx, but like you said, you'd need a whole seperate IPO with the same extension range in place.
>mike
- Thread starter
- #11
The problem is not having a seperate IPO, the problem is having a DHCP server for each IPO. What I am trying to do is give an IPO solution in a tender for which all the other competitors offer a CM solution. My advantage - the price. All the phones are registered in the main IPO (because each one of them can act as a CCC agent), but when the connection failes the client requires the local branch to have the local PBX working. If I get the phones to register with the local PPX when the main IPO fails, I have the solution needed.
Although the CM solution offers more functionality on fallback than this, it would be a lot of help if this could be done on an IPO system instead since it in standard settings doesn't offer any fallback at all.
You could do this by a configuration in the network to offer fallback.
But now you got me curious enough to try if I could get it to work on a 46xx.
You could do this by a configuration in the network to offer fallback.
But now you got me curious enough to try if I could get it to work on a 46xx.
Probez
Programmer
- Oct 22, 2004
- 3
I have tried it on a 3.0 solution with two ip offices. both with dhcp options and with settings file. it works fine but you have to do a reset of the phones for getting them back on the main system (simply by rebootin the sec system) or use the sysmonitor program and do a reboot of the phones from there, i wrote a little applikation there did the same as system monitor, for simple restore operation. I have tried in a lab, and didn't have the need to use more than two ip offices, as far as I see it you have a option to limit the need for multiple DHCP servers.
You could add the mac adr to a specific profile (primary/secondary) gatekeeper, it will take some time but it as valid solution, if you are not in to dhcp scripts for linux servers or windows GUI DHCP settings you may should think about using hanewin dhcp/tftp server it is simple and cheep.
You could add the mac adr to a specific profile (primary/secondary) gatekeeper, it will take some time but it as valid solution, if you are not in to dhcp scripts for linux servers or windows GUI DHCP settings you may should think about using hanewin dhcp/tftp server it is simple and cheep.
- Thread starter
- #14
- Status
