S8300 Failover

[FicBen]

We have an S8700 at our main office and a LSP/8300 at a remote site. When we drop the network connection between the two, the phones at the remote site go into discovery looking for the clans at our main office and not registering to its S8300.

Any suggestions on what I can check?

Thanks!

 

[nohuhu]

FicBen,

check the dhcp option for second gatekeeper address. seems to me that phones just don't know about your lsp.

 

[ischadia]

Checks if the network-region that use the IP telephones has configured the ip of LSP S8300.

 

[FicBen]

Second gatekeeper address? What IP's should be in the 176? I currently have the G700 included.

I did add the 8300 to the network region on page 2.

 

[nohuhu]

FicBen,

in the option 176 there should be at least two ip addresses: first for primary gatekeeper (c-lan circuit pack at the main location) and second for backup gatekeeper. so the string may look like "MCIPADD=xxx.xxx.xxx.xxx,yyy.yyy.yyy.yyy". note that second ip address should be of the s8300 procr interface, not g700 gateway's.
if a telephone couldn't see the first gatekeeper, it would try to reach second and register with it.

 

[FicBen]

We have a clan at the main office listed as the first IP address, and the 8300 listed as the second IP address.

The LSP is listed in the IP-network-region also.

When we drop the network connection, the PRI card goes down and the phones stay in "discovering" mode. The phones still do not see the 8300 when the IP addresses are hardcoded either.

Any suggestions?

 

[JayNEC]

Have you confirmed that the 8300 does in fact go into LSP mode?

Also, how long have you waited? The phones will go through any addition CLAN's that are available, then finally the LSP. If there are a lot of CLAN's that may take a while.

If that is the case, you can play with the timers...

 

[FicBen]

I thought I would post an update for future searches on this issue. Thanks for replying with your suggestions.

Yesterday afternoon, I added a location with the time zone offset and a new network region with the LSP on page 2. We also changed the time to one minute for the failover. However, the two sites did not synch up with the changes. Once we resolved the synch issue, everything worked great!

We also verified that changes are being sent to the LSP as part of the nightly backups (disp sys maint).