www1 and www3 working paralell?

Hallo,

some days ago www3 was down, which is absolutely fatal at us.

Is there any way to use either double conncetions (www1 and www3) or change it quickly in case of "emergency".

It should be a must for business applications.

Thank you for the ideas.

Regards,

P.

RE: www1 and www3 working paralell?

The www3 server is still down, but www1 was not affected at all by this connectivity issue.

To minimize downtime in cases like this, the recommended strategy is to setup another PBXes account, host it on another server (like www1 in your case), and duplicate the setup you have on your primary account.

All your SIP User Agents should register an extension to both servers, and in case of failure you just route calls over the functioning extension.

This works without any issues for outbound calls, but leaves inbound calls from most ITSPs to end up going to the failed server for period of time. That situation creates an issue, until the trunks on the working server take over the registration.

Which brings us to the topic of concurrent registrations. Some ITSPs will gladly allow you to register from multiple SIP UAs located in different places for free, some will try get additional funds for the privilege (e.g. Broadvoice), while other ITSPs won't touch the subject with a ten-foot pole.

Concurrent registrations allow our DIDs to support fail-over, which is their most important feature, since we need to be able to answer incoming calls at all times. So we need to demand that ITSPs allow concurrent registrations, and make it an issue when they refuse to. Otherwise forget automated fail-over for inbound calls.

RE: www1 and www3 working paralell?

Hallo,

Thank you.

it means I host a 2nd setup and create the same system of extensions on both of them: Same extension, same password etc.

All the extensions will be logged on both servers in the same time, are not they?

If one server fail the 2nd one will manage the calls.

How can I switch between the servers? Will it be done automatically or I must route it manually. How can it be done practically.

Is it really possible that a softphone is connected to both servers in the same time?

Thank you for your answer.

Regards,

I.

RE: www1 and www3 working paralell?

• It means that you get another PBXes account and ask for it to be hosted onto another server.

• The extension numbers can be the same for ease of use, but they don't necessarily have to be. The extension passwords should not be the same. No reason for them to match across accounts.

• All of the extensions will be registered to both accounts on different servers at the same time.

• You do not need to switch to another server. The extensions trying to register to the failed server will not work. Just use the other set of extensions which work.

• Depending on the soft-phone vendor, soft-phones can register and remain connected to more than one SIP Proxies.

If you have only used soft-phones so far, try getting your hands on an IP phone which supports multiple registrations. If you wish to be immediately informed on registration issues, get an IP phone with LEDs that change color. For example the SPA-9xx phones' LEDs light up green when the extensions are registered, but turn to orange when there is a registration issue with one or several of them. So you can see the state of the SIP registrations from across the room, without even getting close to the phone.

RE: www1 and www3 working paralell?

Ok. Thank you. It means the "switch" between the servers could not be done automatically because the logins must be changed in the phones.

It is of course a better solution than nothing but is not 100% suitable for us because I can not expect from our colleagues to log in the AVM Fritzbox and change the login to the server :-(

Gr. I.

RE: www1 and www3 working paralell?

You have completely missed the point. No one needs to login into the Fritz!Box or any other SIP UA that supports more than one concurrent registration.

Let's assume you have setup two PBXes accounts, one on www1 and the other on the www3 server. You then setup two extensions on each Fritz!Box or any other SIP UA, the first registering on your PBXes account hosted on www1 and the other registering on your PBXes account hosted on the www3 server.

You then point each of these two extensions, the first to ring on the Fon1 and the other to ring on the Fon2 port. So when the www3 server has an issue, the user can swap to using the other phone connected on Fon2 instead of Fon1.

Nothing to re-provision on the Fritz!Box or any other SIP UA. Zero downtime, just PFM.