|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
I'm having some trouble on an IP500 running 4.1 with embedded voice mail. I do not see how to make an incoming call ring to a hunt group and then go to the auto attendant if there's no answer. It's very easy on VM Pro in the editor but I'm not seeing any obvious way to have an incoming call ring a hunt group and then go to AA.
Any ideas?
|
|
|
|
Joined: Apr 2006
Posts: 254
Member
|
Member
Joined: Apr 2006
Posts: 254 |
To set up embedded VM to delay answer during the day and immediate answer at night: Here is exactly what you need to do for a day and night AA using the embedded vm.. Incoming Route: Main Hunt Grp: Main Add whatever members you want. Group, CW enabled, no VM, Fallback: Time profile=Day hours, Night service=Night Attendant, Queue off Overflow: Select the Attendant hunt grp. Hunt Grp: Attendant Users: add the phatom user you create called AttendantAgent.(3100 example) Linear, CW enabled, no VM, Queue off Hunt Grp: Night Attendant Users: add phatom user you create called NightAttendantAgent.(3500 example) Linear, CW enabled, no VM, Queue off Users: AttendantAgent, 3100, no vm fwd tab:fwd uncond., fwd number= *95, allias=DayAttendant or whatever you want to call it, it follows the shortcode. check the fwd hunt grp calls in this tab as well. Users: NightAttendantAgent, all the same options except make the fwd number=*96, allias=NightAttendant (right click edit) Short codes: *95 AA:DayAA AutoAttendant 0 *96 AA:NightAA AutoAttendant 0
|
|
|
|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
Aha! That looks like a great way to do it! How much would it complicate things if they want to stick with a manual night mode button instead of joining the 90's and doing it based on time? Thanks for the pointers!
|
|
|
|
Joined: Apr 2006
Posts: 254
Member
|
Member
Joined: Apr 2006
Posts: 254 |
It wouldn't at all. Just omit the "Time Profile" info above and give a user a button to set the group into night mode.
|
|
|
|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
I think I set it up as you described but I'm getting this in monitor: 239367690mS CD: CALL: 1.2.1 State=1 Cut=1 Music=2.0 Aend="Line 1" (0.1) Bend="Main(200)" [] (0.0) CalledNum=204 (Night) CallingNum= () Internal=0 Time=12039 AState=1 239367690mS CMTARGET: 1.2.1 367 Alog Trunk:1: PrimeForHGTarget: Night setorig=0 recall=0 resetExtnVars 1 239367690mS CMTARGET: 1.2.1 367 Alog Trunk:1: AddHGTarget Night (depth=0) allowq=0 type=CMNTypeUnknown 239367690mS CMTARGET: 1.2.1 367 Alog Trunk:1: AddHGTargetRingGroup Night ring_attempt_count 0 239367691mS CMTARGET: 1.2.1 367 Alog Trunk:1: Night: Not using 209: FwdU 239367691mS CMTARGET: 1.2.1 367 Alog Trunk:1: OV visable. VM NOT visable:Group VM off 239367691mS CMTARGET: 1.2.1 367 Alog Trunk:1: FindNextInServiceHgInHgIncludedList: Resolved No Alternative! 239367691mS CMTARGET: 1.2.1 367 Alog Trunk:1: PrimeForHGTarget: Night setorig=0 recall=0 resetExtnVars 1 239367691mS CMTARGET: 1.2.1 367 Alog Trunk:1: AddHGTarget Night (depth=1) allowq=0 type=CMNTypeUnknown 239367691mS CMTARGET: 1.2.1 367 Alog Trunk:1: AddHGTargetRingGroup Night ring_attempt_count 0 239367692mS CMTARGET: 1.2.1 367 Alog Trunk:1: Night: Not using 209: FwdU 239367692mS CMTARGET: 1.2.1 367 Alog Trunk:1: OV visable. VM NOT visable:Group VM off 239367692mS CMTARGET: 1.2.1 367 Alog Trunk:1: FindNextInServiceHgInHgIncludedList: Resolved No Alternative! 239367692mS CMTARGET: 1.2.1 367 Alog Trunk:1: ADD HG Night Complete search - no targets found
209 is what I set up to forward to *95 which calls AA:MainAA. Both day and night go to the same AA, just different routes there.
Daytime is supposed to ring a hunt group containing 210 and then overflow with no answer to 211 and 217. If they don't answer it should go to the auto attendant.
Night should go directly to the AA.
Incoming call route points to hunt group 200 that contains the hunt group 201 (Receptionist) as overflow whose only member is 210 (The person). I tried that checking to see if the forwarding would only work if it was overflow. The night destination for 200 is hunt 204.
Overflow is hunt 202 containing extensions 211 and 217.
Night is hunt 204 containing only extension 209, the one that forwards unconditional to *95.
I think I followed what you had described but they aren't quite flowing. I wish Embedded worked a bit closer to how VM Pro works...
Thanks for the help dave
|
|
|
|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
There does seem to be an error in the version we are running as explained here https://www.tek-tips.com/viewthread.cfm?qid=1483576&page=6 I've got it working now so that if I set to night mode it goes to the AA and the overflow from main reception to backup reception works, but we don't overflow from backup reception to auto attendant now.
|
|
|
|
Joined: Dec 2004
Posts: 236
Member
|
Member
Joined: Dec 2004
Posts: 236 |
guys, Since you are both installers, and this is not a basic user issue, but involves some more extensive knowledge I would suggest you take it to the installers forum. I have a little bit of knowledge on the IPO, but do not offer help beyond user type items in an open forum.
I can not recommend any technology platform, only technicians!
|
|
|
|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
There was no reply on the topic for two weeks until you replied to it. It was well on the way to disappearing.
|
|
|
|
|
sts pft
by davetel - 01/14/25 01:31 PM
|
sts pft
by davetel - 01/11/25 06:42 PM
|
|
Forums84
Topics94,462
Posts639,668
Members49,825
|
Most Online5,661 May 23rd, 2018
|
|
1 members (metelcom),
59
guests, and
54
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|