Sharing Avaya extension in different environments

[edobellamy]

Hi, I'm sharing Avaya extensions in a Dev and UAT environments, but seems I need to remove completely an extension from CME before I can use it in another one.
Has anybody experienced this? Do you know the reason?

[cavagnaro]

You can't monitor 1 single extension by 2 TServers...

[edobellamy]

But how is this controlled? Avaya? On TServer dosen't know about the other, and what about back up TServer isn't it both registering the same DN?

Seems strange to me 

[Kubig]

How? Under switch configuration in CME are configured DNs which are registering to the T-Server, which is linked to this switch. For case, where you need to use one set of extensions for two env, you have to disable them on one env and then you can use them on second env. If you need switch env, you have to do same process, but in opposite order. From my experience is too good to uncheck the "register" option on env where you have disabled extensions.

[cavagnaro]

Avaya also knows that an extension is being monitored. 2 Tservers can cause "confusion" to Avaya over a same extension. You can have many clients connected to Tserver but only 1 TServer to 1 extension. As Kubig says, disable the other. On my experience, contrary to Kubigs, that check didn't help much unless you start the Tserver after or a restart, because some PBX do not support UNMONITOR request.
If you insist on this idea, you are free to do so but don't expect much help

[Kubig]

Thx for addition infos, you are right. I have not much experience with Avaya PBXs with Genesys, almost with SIP or Alcatel, sometimes unfortunately Nortel :-)) In general is better to do restart of T-Server after similiar changes.

[cavagnaro]

haha hate Nortel...wwwwwwwooooooooooooorrrrrrrrrrrrrsssssssssttttttttt PBX ever...