IP Phones Failover

[nicka29]

Hi

I have IPO on 8.0.18 and a failover IPO on 8.0.18.

Last night I tried to test the failover but got some weird results. I configured the SCN fallback correctly and did a reboot of the main unit. 1st problem being the failover happened very quickly (20secs) meaning that very time I did a reboot the phones would always try to failover. The 2nd issue was that the phones would never log onto the failover box they would just sit saying airing for ext. Auto create extns are off on both IPO. You can't then just reboot failover bx as the phone is in no mans land and actually doesn't exist on either IPO. You have to power cycle the switch or reboot the phone to get it to register with the main IPO again.

Westcon have replicated the issue in there lab as well and it's been passed up to avaya. We think it could be a problem with windows DHCP as it doesn't happen when you statically assign a phone.

Anyone come across this issue before

Thanks. Nick

 

[Bas1234]

Do the base extension and the users have the same number? If not then it won't work and you need Avaya IP Endpoint licences for everery extension in the fallback unit.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[amriddle01]

Systems acting as failover do not need endpoint licences for the failover phones, they are not required in that scenario, this is mentioned in the docs

 

[kwing112000]

Make sure your backup system doesnt have the base IP extensions of your main site. i had this exact same issue and removing all the IP extensions fixed it right away.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[nicka29]

Hi

There is no ext at all in the failover unit.

Seems to work fine if phone is getting dhcp from IP Office or is statically assigned an address

Nick

 

[tlpeter]

Systems acting as failover do not need endpoint licences for the failover phones, they are not required in that scenario, this is mentioned in the docs

Indeed, this was only needed in 5.0 (first version with fallback)
All later version use the licenses of there main system.


BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

You sure Peter? As 5.0 didn't have endpoint licences

 

[tlpeter]

But it did have the SCN resiliency:

IP Office Release 5 will permit an H323 trunk that is configured as a “Resilient SCN” trunk in the drop down list of choices to be marked as the Secondary (Backup) PBX for resiliency. The backup system is only required to have an SCN trunk to the main system. Provided it holds the correct license keys for Release 5 and Voicemail Pro, there is no further configuration required for basic operation.

BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

I know, but it didn't impose the handset licencing requirements we are discussing, you started drinking your loopy juice early?

 

[amriddle01]

 

[tlpeter]

Not yet and i need to buy a new one tomorrow
I am not sure which version but now you do not need IP endpoint licenses on a backup system.


BAZINGA!

I'm not insane, my mother had me tested!

 

[jfilary]

I have experienced (and am still experiencing) this issue as well. I currently have an active case open with our distributor looking in to it. I'll keep you posted once I get some feedback. I actually have 6 sites in the SCN. Sites 2, 3, 4, 5 & 6 are all set to fallback to 1. 1 is set to fallback to 2. We are experiencing licensing issues, and also phones re-registering immediately instead of waiting the 3 minutes.

I found something in the IPO knowledgebase that confused me, and I was thinking it may have something to do with this problem. Maybe someone out there has some thoughts on it.

"From the Knowledgebase"
• Note that both ends of the SCN trunk connection must be set to fallback.
• On the system requesting backup, the required SCN Backup Options are selected, indicating that it is requesting backup. A single system can only request backup from one other system.
• A system providing backup can provide backup for up to 7 other systems.

I don't see how this scenario could exist. It states that a system can backup 7 other systems. It also says that each side of the SCN trunk must be set to SCN-fallback, but then says you can only specify (1) H323 trunk per site for SCN-fallback. That being the case I can't set both sides of the other 6 sites to SCN-fallback like it says you need to do...

I don't get it... Am I missing something here???

 

[Albus2]

I actually never used Fallback, as the option to register the phone on a second site is nice, but you still have no PSTN connection. I know, there are other options to overcome this, but still.

Anyway, if you use the IPO as DHCP server, it will give two addresses for the callserver option. The first is the local system, the second is the backup site. If you do it with a 3rd party DHCP server, you need to specify two callserver sddresses.
But that's not all it needs.
Of course your networks must be setup to allow a phone on site A to reach the IPO on site B. If you try it manualy, can you register a phone on the other system?