Compatible in US and UK?

[mytelecoms]

This may seem a silly question, but here goes.

I am wondering if a Small Office Edition which is bought in the US (without trunk cards) will work in the UK, and likewise would a UK model work in the US.

I know that the likes of a 403, 406 and 412 come in A-Law and MU-Law versions, but IP Office has the option to set A-Law or MU-Law on the system tab, and so does the Small Office Edition.

Finally, would the loop start analogue ports work in the UK? They appear to be the same spec, but I need to check.

Thanks

 

[intrigrant]

It will work just fine as long as you use the eng locale in the UK.

 

[mytelecoms]

I thought as much. Thanks.

Wonder why Avaya mark them up as US? Is it simply the default state?

I expect the analogue trunks will be fine too?

Thanks again

 

[sizbut]

There are a few other things than A/U-Law affected by the default settings, a key one for the US market is E911 stuff.

If you try setting it up on a system that is US default from the manufacturer it won't work. You can change the locale, see E911 setting but you can't setup the zone aspect.

So a US system can be rejigged for non-US but unless your sure the customer doesn't want E911, a non-US system can't go to the US

 

[mytelecoms]

Am I right in saying E911 is for tracking exactly where 911 calls come from in the US?

I thought this was only useful for mobile or cellular phones, unless of course the office is not sending out CLI.

Would the customer benefit from this in an office if they are sending outgoing CLI??

All this said, bringing a US system to the UK would be fine then? It's only the other way I need to worry about because of E911?

Thanks guys

 

[sizbut]

E911 is not tracking per say, it about identifying in which building or area of a building a phone is located so that the emergency service can be directed there rather than having to go to reception first. Think of situations such as a large multi-building campus or a multi-site company.

It helps in cases where the registed address of a line owner may differ from the physical location of the line or may not provide sufficient detailed information.

 

[IPGuru]

setting the locale in the system tab correctly controlls wether or not e911 support is enabled.

Part of the boot sequence of a default IPO is to detect the regional settings of the manager PC & configure itself acordingly. this has caused many moments of amusment when the customers PC has not been correctly regionalised resulting in a US IPO instead of a UK one.

 

[Raffles666]

This can also happen when you upgrade a unit from an alchemy to ipo. The default locale of the alchemy is 'en' - which meant UK. It means 'US' in the IPO. Something to watch out for (the appearance of the E911 tab in the config gives this away). Just change it to ENG and all will be fine .



Old school Alchemy engineer - trying to keep up with the times

 

[Spanning]

It works fine as long as the locale is set to eng , we have 12 sites and no problems.

 

[Raffles666]

Isn't that what I just said? You must be going for the 'user with the most posts' award



Old school Alchemy engineer - trying to keep up with the times

 

[Spanning]

i was only confirming ditto

 

[sizbut]

Sorry to quibble with you IPGuru, for you are the Guru, but I've learnt the hard way about E911 - ages spent trying to set it up and wondering if the manual was wrong.

Take an A-law default systems from the factory, set it to ENU and yes you see the E911 option in the config - but try adding any zones to the E911 setting! Try it with a U-law default system and its all hunky dory.

 

[IPGuru]

Having had no need to use ENU ( being UK bassed) I would always bow to the experience of my US colllegues on issues relating to the North Ammerican telephone system.

thanks for the additional info.

 

[IPGuru]

Interestingly an UK Soe will take a US cfg created using the wizard correctly & then allow edditing of zones.

getting the Soe to default as a US system does not allow the creation or edditing of zones.