immediate auto-attendant 1

[Telecomboy]

Is there a parameter that can be changed to send all incoming calls straight to the auto-attendant without having it ring 3 times first? Incoming call route is pointed to Attendant, but the caller still hears 3 rings before it is connected. Is there a way to send it immmediate? Thanks in advance for any input.

 

[CarGoSki]

Do you have loop start lines with caller ID?

 

[Telecomboy]

One of my customers has loop start lines with caller id, the other one has a PRI.

 

[CarGoSki]

Loop start lines with caller ID take two rings for the caller id to be sent. If your customer desires to have caller id on these loop start lines then you can not avoid the ring times.

There are many different ways to route calls immediately to an auto attendant. You could route calls to a hunt group with no members and voice mail on.

You could route calls to a short code. In either case you would pick up the routing in VMPro. Group section for hunt group routing or short code or module section for short code routing.

Do you have the engineers toolkit?

 

[Telecomboy]

I have the lines routed corrctly through a shortcode, I was just wondering if their was a way to cut-out the 3 rings before it picks up. It sounds like with loop-start lines it isn't possible. Can you cut-out the rings if they have a pri?

 

[CarGoSki]

You can cut out the ringing with loop start lines if you set each line to loop start and not loop start ID. But of course you will lose caller ID.

You can cut out the rings for PRI. Extraneous rining in not necessary when using PRI.

 

[hohumIPO]

Hey, if you create a Voicemail Module and link the incoming call route to it straight to a huntgroup you eliminate the 3 rings.. be carefull, this can confuse customers and in Australia it is actually considered illegal for there not to be 3 rings before the "other end" picks up....

 

[aeverson]

PRI's should not ring three times before answering. If you turn off Caller ID on your loop start lines then that will reduce the number of rings before the IP Office picks up. What in your auto-attendant are you routing to. Is it a menu, assisted transfer, campaign, etc? You may want to take a look at how your PRI is configured because in my year of dealing with IP Offices and digital circuits I have never had any pre-ringing before the auto-attendant message plays.

 

[CarGoSki]

Why on earth would it be illegal in Australia to have fewer than three rings before AA picks up?

 

[hohumIPO]

you tell me and we will both know

 

[CarGoSki]

Sounds like an urban legend to me.

 

[Telecomboy]

I have my incoming call route (a DID on a PRI) destination set as Attendant. The Attendant short code starts out with a Menu option. When I call the main number, it still rings 3 times before the Menu option picks up. It's not a huge deal, but I know other IP Offices I have encountered with what seems to be the same set-up go right to the Attendant Menu.

 

[CarGoSki]

Post your incoming route and shortcode. BTW, do you get three rings before pickup when you dial the shortcode directly?

 

[bason]

When using VMpro if you send calls to a group,set queue time to 1 second and use a group node with the "queued" check box set.Then set up the AA from there.

 

[big70]

If you make a shortcode and point it to a module in VM-Pro
it will directly answer the call and you lose the tree rings.

Greets Peter

 

[crashtest1000]

Just us a Module and end this thread

 

[NuggiFirst]

Why do you guys use groups to send calls to VM Pro??

The easiest way (my opinion)

In "Incomming call route", set the the destination to (example): VM:Main.
Then make a node called "Main" in VM Pro/Modules, and pick it up from here. No Shortcodes needed, no extra group needed. And it picks up instantly!
An extra feature: If the VM server is down, the calls will go to the "Main" HG, so you also have a fallback ;-)

 

[IPGuru]

The most likly reason why people are still using groups for VM access is because your suggested solution did not work correctly in early releases, old habits die hard

 

[NuggiFirst]

He he.. Yes it's an old Alchemy feature ;-)

But it's the only good way to do it on an IPO! (my opinion).

To my knowledge it has worked since 1.4?!?

 

[IPGuru]

Yes it was an old achemy feature & got fixed in 1.4
the trouble is some of us - especialy the old alchemy guys ,like your self, have been working with IPO since V1.0 & had to find alternative ways to cope with VM failure (especialy as V1.0 was prone to this)

From V2.0 I would recommend sending the incomming call route to a VM Node & setting a group as the FallBack option