Page 1 of 2

call from 4645 auto att not o/flow to 2nd route in entity

Posted: 26 Jul 2009 17:38
by knightr1der
Hi guys,

I have an entity with a Hunt Grp in Day 1 and another 4645 auto att number in Day2.

When I call the Entity call prefix internally it rings Hunt Group and then after overflow timer it goes to 4645 auto att nicely.

But when I call Auto attendant then choose option to call the entity call pfx it rings Hunt Group but then does not overflow to day2 :?

Release is H1.301.28.b

Anyone had similar or know of a fix?

Thanks in advance

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 27 Jul 2009 03:48
by murraya
oh no! why on earth would you do that night? It sounds like something I would do.
Now to be serious. I have had that very senario with level 3 for about 4 monts now and R&D are looking into it as we speak. They have offered lots of work arounds to me and I keep shhoting them down as as far as I see it sould work but won't.
If you provide a email address ( or if PM is working) I can send you some of their suggestions for you to try if you want.
As it stands the only option they have come up for me is to fall back to the trunk entity table but I already use that at my site because of the lack of (different) overflow timers for extn's. My customer has multiple companies and I was wanting the same as you for a night bell for one of them.
call comes into 4645 AA
option 0 ( operator) rings group with only bell in it.
overflow to a night mailbox after 40 seconds.
timer 4 is 15 sec as used by extn's overflow to voicemail.

Let me know if you have an address to forward R&D workarounds :(

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 27 Jul 2009 03:50
by murraya
BTW R&D say fix in week 0930 :D
oh! is that week ninehundread and thirty? as I thought there were only 52 weeks in a year.
If it's week 30 2009 that is this week :D :D :D :D

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 27 Jul 2009 04:37
by knightr1der
thanks for the reply murraya :D

Ok, PM's are still not working! Can you shot me a mail?
knightr1der@tiscali.co.uk :D

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 27 Jul 2009 05:22
by murraya
email sent :D

I'll updat in this post with any news so others can find as well.

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 27 Jul 2009 05:45
by murraya
Good news :D :D
week 0930 is this week.
I just got a email from support and R&D say it is not possible unless I use the workaround to follow trunk entity (which I can't do at the site) :(
They have come up with a solution for me :D
The solution is open a marketing request :(
Maybe they could add it to the others that they don't do :lol:

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 30 Jul 2009 13:06
by knightr1der
hey murraya - I got your emails.

It seems you were right. It's a buggy they aint gonna fix!

Here is what I've just got back from my escalation;
I would like to keep you nformed that I was able to reproduce the issue in R9.0 h1.301.32 in UK empty database. So I am escalating this issue to further level
I'll keep y'all posted!

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 31 Jul 2009 00:25
by murraya
Hi, I,ve started the ball rolling for a marketing request. I hope to hear from Alcatel Presales shortly on the issue.

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 31 Jul 2009 07:54
by knightr1der
I think meanwhile we might try IAA to get around the problem.

Re: call from 4645 auto att not o/flow to 2nd route in entity

Posted: 31 Jul 2009 17:43
by murraya
Hi, that should work except in my case where I needed to give more than 4 options to the caller.
Good luck :D