Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Route CLI to required destination

Status
Not open for further replies.

DCPTS

Vendor
Sep 6, 2010
19
GB
We require to route a specific incoming caller to a specific destination.

We have done this easily on an IP Office but now require to do the same on an 'Argent Office' 2.6(65)

The programming looks the same as the IP Office but simply does not work?? Incoming call from the programmed CLI still goes to the catch-all Main Huntgroup???

INCOMING CALL ROUTE PROGRAMMING:
Incoming Call Group ID: [0]
Incoming number: [Left blank and also tried *]
Incoming subaddress: [Left blank]
Incoming CLI: [entered full CLI number including national dialling code]
Destination: [entered from drop down desired destination]
AnyVoice [selected]

Looking at the monitor trace, the incoming CLI is show but always goes to 'Main' huntgroup

Anybody had this working on an Argent Office?

Cheers
 
Programming on an Argent should be idenitcal
I have had this working in the past but it was a long time ago...
I suggest you double check the data in the cli field
(it may also be woth setting this up on a dedicated DDi whilst testing)


I do not Have A.D.D. im just easily, Hey look a Squirrel!
 
It might also be worth trying to change "Any voice" to "Any" just in case that it doesn't come in with the proper service.
But like IPGuru said test it out with a DID and that way you can play around with it without screwing up the real incoming calls.

Joe W.

FHandw., ACSS

insanity is just a state of mind
 
IPGuru

Thanks for your reply.

100% sure that the CLI field is correct, tried a mobile number and also a land-line number of head office.

The incoming CLI is shown and confirmed on the incoming call in the monitor trace although should it show as matching something in the monitor trace?

What do you mean by 'setting this up on a dedicated DDi whilst testing'?

 
put in a number in the incoming number field so it only works on one number dialed

Joe W.

FHandw., ACSS

insanity is just a state of mind
 
Westi
Thanks for your reply.

On the IP Office we entered a star in the incoming number field that caught all calls but maybe this do not work on the Argent Office.

We will try one of the DDI's as you suggest.
 
As I said, you WILL need to use a DDI to route your CLI as well, unfortunately a * will not work on an old argent / alchemey as this is a reasonably new "feature" of the IPO.

So, if you have 100 DDIs...... :-S
 
Thanks guys ... test DDI number entered and it works!

They want 3 CLI numbers steering and there are 20+ DDI's = lots of entries!!

Cheers
 
Now retry it with the *
I cant remembre if this was available in the alchemy release though


I do not Have A.D.D. im just easily, Hey look a Squirrel!
 
Try to enter the last 5 digits of that CLI, or just remove the first most left 3 or 4 digits.

You don't need to match the whole number, also check the SysMon how the number is presented to the IPO.

Enable the ISDN filter and turn off the rest.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top