Remote SCN extension User Button Readme!

[BURLYMAN]

Well I just found something out last night! In previous releases of IPO (before 3.0) if you place a "User" button for a remote SCN extension on a local extension (i.e. Extension 201 has a User button programmed for Extension 301) you will actually see the button illuminate on extension 201 when extension 301 is busy or a call is ringing the extension. I believe that the unintended result in version 3.0 is that you are able to hit the button on extension 201 and actually answer the call!!! I tried this in earlier releases with no luck (1.4 and 2.0) - attempting to answer the call just did not work. NOTE: This will only work if the button is programmed using the "Name" under the user tab of an extension. I tested using the actual extension number and it does not work. I guess this is because SCN does not work when using remote SCN extension numbers on telephones but for some reason SCN will pass and use the extension name. Now the great thing for me . .. . I have posted a couple of questions in regards to adding a remote SCN extension to a local hunt group which can not be done. (i.e. I wanted to add extension 301 to the local 200 hunt group so that when inbound calls from telco come in to hunt group 200, extension 301 would ring as well and this just does not work as you cannot place a remote SCN extension into a local group). However with this ability I have half of the solution: when and extension in the local hunt group is ringing I can see it on my remote extension via the led. My problem now is that the remote extension will not ring but the light will illuminate and I am able to answer the call. Currently I have an IP phone registered to the local group that rings in my remote office (I have the ringer turned way up!!!) and when this happens I can look at my extension and see the led for the user button illuminate and I can answer the call. Does anyone have any suggestions for ring generation at this point??

 

[Morrack]

If you aren't using Phone manager for your phone at the remote site you could sign in as the phone that is part of the huntgroup, the one that you are programming the user button for.

I would be cautious about this whole solution though, it smells to me like you are exploiting a bug that Avaya will "fix" in an upcoming release.



Peter Sherwood

Morrack Consulting

http://www.morrack.com