cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
adam_lay
New Contributor

6355 feasability and pri

What is required to backup sip phones with a pri as the secondary route? We have an installation of around 120 sip phones which will require multiple Netvanta 6355 connected to form an array. What is the feasable backup capability as well as feasability of 'daisy chaining' multiple sip inputs to a single primary, and secondary route? Also, would it be possible to establish a third D/R route in the event of primary and secondary failure with POTS lines?

Any advice or knowledge is greatly appreciated. This is our largest project to date regarding sip phones.

Extra info: we are linking our sip phones to an off-premise Metaswitch which we use for provisioning etc.

Thanks, Adam

0 Kudos
1 Reply
jayh
Honored Contributor
Honored Contributor

Re: 6355 feasability and pri


adam.lay wrote:



What is required to backup sip phones with a pri as the secondary route? We have an installation of around 120 sip phones which will require multiple Netvanta 6355 connected to form an array. What is the feasable backup capability as well as feasability of 'daisy chaining' multiple sip inputs to a single primary, and secondary route? Also, would it be possible to establish a third D/R route in the event of primary and secondary failure with POTS lines?



Extra info: we are linking our sip phones to an off-premise Metaswitch which we use for provisioning etc.



Are you going to be using the features of the 6355 or the Metaswitch for the phones in terms of call routing, voice mail, etc.?  Where do the phones register?

You probably don't need a cluster of 6355s.  One 6355 will have the SIP smarts for all of the phones at the site.  Then use PoE switches to gain enough ports for the rest of the phones.  1238P for 100-Mbit LAN or 1534P for gigabit LAN. 

For a secondary route you need the PRI VIM for the 6355 or FXO VIM if using POTS lines, or both.  Then program a secondary (higher cost) route on a voice trunk group for the secondary.

Note that the secondary route will only work for outbound calls from the site without extra work on the carrier side which can be substantial. 

Inbound calls will be routed to the primary SIP endpoint for the Metaswitch (or 6355).  Getting inbound calls routed to your PRI in the event of a failure involves work with the carrier, depends on the nature of the failure and the cluefulness of the carrier, and can be rather tricky or impossible depending on your situation.