Transferring Old Extensions to New DID's

[smaslin]

Here's the situation...

We have a lot of DID's available, (3000,4000 series #'s), but our sales force uses non-DID 6000 series Agent ID's. The idea was put out there to replace everyone's 6000 series Agent ID and give them all 3000 or 4000 series Agent ID's so they can be direct dialed.

However, they want the old numbers to still work and forward to the person.

I know I can create VDN's for each 6000 series id, but there aren't enough vectors available to forward each one individually.

Is there a way to set up forwarding for all of the extensions? Or is it just easier to tell people to change their voicemail message on the 6000 series number that their number changed?

 

[4merAvaya]

Assuming that you have enough RTU, you could change the old Agent ID into an x-ported station and either crate a coverage path for each station to the new number or use call forwarding to the new number.

Kevin

 

[smaslin]

How would I set up the call forwarding for each station? I've looked in the switch and I can do a "list call-forwarding", but I cant figure out how to modify that.

 

[SF0751]

Call forwarding: Dial the FAC for Call Forwarding Activation (all), dial the extension you will be activating the call forwarding for, and then dial the number your are sending the calls to.

"list call-forward" just shows you what stations have call forwarding activated, and where they are call-forwarded to.

Susan
"People seem not to see that their opinion of the world is also a confession of their character."
Ralph Waldo Emerson (1803 - 1882)

 

[4merAvaya]

From a station with Console Permissions you can activate/de-activate features like call forwarding and send all calls.

Kevin

 

[smaslin]

The problem is, I'm trying to forward extensions to login-id's and its not following their coverage paths. I just tried it, it gives a busy signal when transferring to the new login id, even though it has a coverage path.

 

[RGarcia87]

Convert the stations with "x" ports and in the "hunt to station" field enter the extension it needs to forward to.

 

[smaslin]

Still getting a busy signal. It tries to do it, but gets a busy signal from the destination, even though the destination is an Agent with a Coverage Path.

 

[GuzaPasha]

Could you send exactly what you need, here is what I think we should know.

eg: Agent 6001 will match 3001 DID? is this the logic, if yes send what type of trunk do you use ISDN or T1 or E1.

GuzaPasha

 

[smaslin]

GuzaPasha:

Basically yes, that is the logic. The Agents are just going to be reassigned a new Agent ID based on DID's. We use all T1's.

 

[telcoguy]

Why not just strip the 3 an the 4 and replace it with a 6 on the trunk form routing ?
That way your customers don't need to dial new numbers as well.., as long as you can live with the fact that the 1st digits differs ..

 

[smaslin]

The numbers dont match exactly. I don't have an entire 1000 block of numbers available. I have about 300 available, with a couple numbers already taken in that range. I wish it was as easy as just striping digits.

 

[GuzaPasha]

Try inserting the digit AAR FAC on the trunk form page 1.

eg: AAR FAC 9

on that way your call will be processed by the AAR digit conversion
table, or AAR analizes.

So, if you get digits 3xxx on the AAR digit conversion table you will easily make conversion to 6xxx. The agent can be accessed directly, and will hold his old number.

If this is solution i can help much more.

GuzaPasha

 

[smaslin]

The problem is that not everyone's current login id matches up good with their new login ID..

For example, I have two login ids of 6405 and 6605. One would have to be 4205 and one would have to be 4305.

I need to come up with some good forwarding setup for this. I still cant get anything to work, still just gives busy signal.

By the way, I do have Intuity Audix, which I did notice there is a spot for a Covering Extension, but that doesnt seem to be working.

 

[SF0751]

"Covering Extension" is the destination of the "zero-out" option for the caller. Try "Secondary Extension" instead.


Susan
"People seem not to see that their opinion of the world is also a confession of their character."
Ralph Waldo Emerson (1803 - 1882)

 

[smaslin]

That didn't work either. If I try anything from Audix, I get "Please wait.... Line Busy, returning to previous activity".

I have an extension of 6666 set up, with 6665 as the old Agent LoginID, and 4144 as the new Agent LoginID. I have 6665 with currently set up with no coverage path but 4144 as the Hunt To Extension. Then I have 4144 as a regular AgentID with a coverage path pointing to Audix.
Ext 6666 is not set up with any coverage path, but noone dials their extensions anyway, just their agent loginids.