Problem Swapping Extensions - Forwarded Calls Ringing @ the Wrong X

[mikey71174]

I'm using WinSPM R 9.0 with our Avaya Merlin Magix PBX system. When I swap two extensions, calls forwarded to one are going to the other (i.e. - Extension 2271 was moved to office X from office Y, and extension 2204 was moved from office Y to office X. Calls forwarded to extension 2271 are ringing at extension 2204 in office X). If anyone can explain why this is happening, and how I can fix the problem, I would greatly appreciate it.

Thanks!!

 

[SYQUEST]

Please post prints of both stations, so we can have a look see, and the problem may be self apparent.

....JIM....

 

[mikey71174]

I would be glad to, but as I am new to WinSPM and Merlin Magix (experienced with Meridian systems), I don't know how to do that.

 

[dagwoodsystems]

Extension programming follows the port or Logical ID, not the extension number. It sounds like you "programatically" swapped extensions as opposed to physically swapping cross-connects.

To truly swap extensions, you should first print an Extension Info report for each. After renumbering both extensions, reference each report to properly rebuild each extension as it was. I'll say it again for clarity: intercom buttons, private lines, autodial buttons, forwarding, etc is all built on the port record, not the extension number. In fact, the extension number itself is just another attribute of said port. That's why "swapping" extension numbers via programming takes a bit of effort.

To print an Extension Info report: SysProg > Start > More > Print > More > Ext Info

Tim Alberstein

http://www.dagwoodsystems.com

 

[mikey71174]

Thanks. After printing, I found that the extension is set to forward to the other for some reason. However, I don't know how to turn that off.

 

[dagwoodsystems]

UNforward by forwarding the extension to itself.

Tim Alberstein

http://www.dagwoodsystems.com

 

[mikey71174]

That would be done at the phone itself as far as I know, but I don't know where the extension is physically located. It is not located at any of the two locations I swapped. Is there a way to change the setting in WinSPM?

 

[Telecomboy]

What is the extension that is forwarding to x2271 (now x2204)?

Here is what happened: When you swap extension numbers that is all you are doing, none of the programming moves with the phone. So, that extension that did forward to x2271 is now forwarding to x2204 because the programming stays with the port.

What you need to do is figure out what extension is forwarding to x2204 (originally x2271) and forward it to x2271 again. If it is a phantom extension, you need to figure out what the authorization code assigned to that phantom extension is so you can re-forward it.

 

[mikey71174]

The extension forwarding is 2217, and it's forwarding to 6404. I know the extension number, but not it's physical location. I've tried to call it to recreated the issue, but it now goes straight to voicemail as if there's no phone plugged in.

 

[merlinman]

Mikey - There is more than 1 way to find out the physical port involved.

It is easy to determine the extension port in Maintenance (Standard SPM - Menu - Maintenance)

Maintenance - Station - Extn Number - Enter - STATUS

Or - you can print the Extension Directory and know where they all are:

Standard SPM - Menu - Sys Prog - Start/Exit - More - Print - More - Ext Dir.

This will print a report to you SPM Computer.

http://home.comcast.net/~merlinman