I don't think you can do a blanket announcement,,,,
but it would be easy to add
announcement xxxx
to the beginning of your main incoming vectors for the call centers.. ect..
as for the DID's,,, you could do use incoming-call-handling treatment to manipulate the digits... and if you have variables then it would be pretty easy,, just create a vdn for each DID, and assign the real users ext as V1,, then route to same vector
1 wait time 2 secs hearing ringback
2 announcement XXXX
3 route to number V1 with cov y if unconditionally...
Have got the announcement at the start of the call centre and the main switchboard numbers, but wanted to have it before all DID calls. on;y prob is, dont think we have the variables allowed. We are running call manager 3, but without bells & whistles
Andy, it's a long shot but you might be able to get the carrier to play it for you at network level. I know BT can do it on call plans for non geographics, we had full menu's on ours. So they may be able to extend that functionality to all inbound calls to your number range. Like I say its a long shot, but if you're stuck it may be worth a call?
With no Vector Variables available, we have had to do it the hard way:
Create a vector to play your announcement and then route to the extension number (try to keep some form of unity with the extension number for ease of admin)
Create a VDN (again with unity, ie if your extension range starts 77, use 67 for the vdn number) linked to the vector
change inc-call-handling-trmt trunk-group x (where x is your trunk number)
Add in the line as required to divert your dialled DDI to the VDN number that you have configured.
Hey presto, the system plays the announcement, then rings the phone.
you can also (if like me) you have an "Emergency" group set up, include the routing line for that in your vector, so that you are covered in all call entry points
Can you post the vect you used? I'm not following how you did this w/o variables. Are you creating a seperate vector for each ext.? I'm trying to accomplish the same thing.
Yes, I have essentially set up a vector and vdn for each extension that plays the incoming announcement and then routes to the extension called.
So, if my incoming DDI is xxxxx 497762 my inc-call-handling table for the trunk is set to route this call to ext 6762 (keeping some semblance of similarity.
6762 is the VDN for vector 162 (again, similarity)
vector 162 is coded as:
01: announcement xxxx (whichever announcement you want)
02: route-to number 7762 with cov y if unconditionally
This is absolutley fine if you have a small number of extentions that will not exceed the capacity of inc-call-handling-trmt trunk-group
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.