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!

Auto Attendant at start 3

Status
Not open for further replies.

Ludit

Technical User
Sep 29, 2015
69
US
Hello tek tip peeps, I'm here again seeking for wisdom!

I have a place that wants AA at start and this is how I have setup.

HuntGroup-> Main 200 (Reception 250)
HuntGroup-> Greetings 201 (Phantom 251 that forwards to AA *60)
Incoming Call Route - All analog lines goes to goes to Greetings 201 hunt group so it can be forwarded by Phantom 251.

So what I get here is that when someone calls in it goes to Greetings 201 which connects to Phantom 251 that forwards to Main 200 then finally dials to user Reception 250.

The first caller calls in and its no problem but the problem I came across is that when the Reception is currently on the phone, an second caller tries calling in would only get ringing and does not goes to the AA.

Is this the best setup for an immediate AA?
The time profile and out of service button seems ok here.

Thank You
 
Why don't you set the AA as target in ICR? There you can also configure different targets based on time profiles.
 
Hi,
Yes that was the first configuration I tried. It has 4 analog #'s and I put them all to AA(*60 or AA:Greetings). Same problem arises, the first caller would reach the AA but the second caller would just hear ringing while the first caller in on the line.
 
Wait sorry derfloh, let me try that configuration again.
 
Yep, the second caller is still ringing.
 
Then you're doing it wrong, no point making an over complicated routing plan just because you can't get it working the right way.
Are all the lines on the same number? Are they all in the same incoming line group? Are you sure they are all connected correctly? What if you route the elsewhere? How many times have you done this in the past?
Many questions to be answered and things to be checked before assuming the system is not working correctly.
Also out the box it will only allow 2 calls at once in VM and/or attendants :)

 
Hi amriddle01,
Yes you're correct due to my limited experience on setting an AA during an incoming call from the start so I can't assume it's not working. I have other sites that doesn't have AA from start, it would be just basic if no one picks up it goes to AA or overflow it goes to AA.

All 4 different incoming lines and they all go to the same incoming group and with same ID group as well. I can route directly to the Reception phone no problem without using the AA.

If derfloh suggestion for setting an AA from the start for this kind of configuration then I must have overlooked somewhere.
 
Certainly sounds like they aren't even hitting the system, you need to trace things and watch what happens, you aren't giving us much to go on so you need to troubleshoot it :)

 
Seems like VM is busy.

Can you check system status alarms? See if you get an vm overload..
 
Ok I'm currently looking through the monitor, this is what happens when it connects successfully. I can see it hits the AA.


CMSetup
Line: type=AnalogueLine 6 Call: lid=6 id=3 in=1
Called[] Type=Unknown (0) Reason=CMDRdirect SndComp Calling[1234567890] Type=Unknown Plan=Unknown Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
BChan: slot=3 chan=2
IE CMIECallingPartyName (110)(Type=CMNameDefault) name=New York NY
IE CMIEDeviceDetail (231) c0a8018400000003 LOCALE=enu HW=15 VER=9 class=CMDeviceAlogTrunk type=0 number=6 channel=0 features=0x0 rx_gain=32 tx_gain=32 ep_callid=3 ipaddr=192.168.1.132 apps=0 loc=0 em_loc=0 features2=0x0 is_spcall=1
Timed: 15/12/15 15:46
15:45:09 1825317247mS CD: CALL: 6.3.1 BState=Idle Cut=1 Music=0.0 Aend="Line 6" (3.2) Bend="" [] (0.0) CalledNum= () CallingNum=1234567890 (New York NY) Internal=0 Time=3 AState=Idle
15:45:09 1825317247mS CMCallEvt: c0a8018400000003 6.3.1 2258 Alog Trunk:6: StateChange: END=A CMCSIdle->CMCSDialInitiated
15:45:09 1825317247mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: LOOKUP CALL ROUTE: GID=0 type=0 called_party= sub= calling=7188879787 dir=in complete=1 ses=0
15:45:09 1825317247mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: SET BESTMATCH: length 0 vs -1 match=2891507 dest=Greeting
15:45:09 1825317247mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: AMBIGUITY: match=2891917 dest=Greeting
15:45:09 1825317248mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: AMBIGUITY: match=2891985 dest=Greeting
15:45:09 1825317248mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: AMBIGUITY: match=2891954 dest=Greeting
15:45:09 1825317248mS CMCallEvt: Priority hike: call 2258 priority 0->1
15:45:09 1825317248mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: LOOKUP ICR: DDI=7187896325 CGPN=1234567890 Matched Time profile: Day (Destination AA:Greetings ) => CDPN=AA:Greetings
15:45:09 1825317248mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: ADD TARGET (N): number=AA:Greetings type=0 depth=1 nobar=1 setorig=1 ses=0
15:45:09 1825317249mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: ADD VM TARGET
15:45:09 1825317249mS CMTARGET: **** c0a8018400000003 6.3.1 2258 Alog Trunk:6: MakeVoicemailTarget pbx=<null> local=1 type=3
15:45:09 1825317249mS CMCallEvt: 0000000000000000 0.9273.0 -1 BaseEP: NEW CMEndpoint f1845d60 TOTAL NOW=3 CALL_LIST=1
15:45:09 1825317250mS CMTARGET: c0a8018400002439 0.9273.0 2258 RAS.0: ADD PRIMARY
15:45:09 1825317250mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: ADD VM TARGET: SUCCEEDED
15:45:09 1825317250mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: INITIAL TARGETING SUCCEEDED
15:45:09 1825317250mS CMTARGET: c0a8018400000003 6.3.1 2258 Alog Trunk:6: GetNoAnswerTimer:15
15:45:09 1825317250mS CMCallEvt: c0a8018400000003 6.3.1 2258 Alog Trunk:6: StateChange: END=A CMCSDialInitiated->CMCSDialled
15:45:09 1825317251mS CMLineTx: v=6
 
The more interesting would what happens when an incoming call doesn't ring a phone or hits the AA.
 
Looks like your destination in ICR is "Greeting" and you're auto attendant is "AA:Greetings" ...that's not the same, try correcting it :)

 
This is me calling with my cell while the first caller in on the line, I'll try to make sense of the below portion if I can


CMSetup
Line: type=AnalogueLine 7 Call: lid=7 id=4 in=1
Called[] Type=Unknown (0) Reason=CMDRdirect SndComp Calling[91712121212] Type=Unknown Plan=Unknown Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
BChan: slot=3 chan=3
IE CMIECallingPartyName (110)(Type=CMNameDefault) name=Alex
IE CMIEDeviceDetail (231) c0a8018400000004 LOCALE=enu HW=15 VER=9 class=CMDeviceAlogTrunk type=0 number=7 channel=0 features=0x0 rx_gain=32 tx_gain=32 ep_callid=4 ipaddr=192.168.1.132 apps=0 loc=0 em_loc=0 features2=0x0 is_spcall=1
Timed: 15/12/15 15:46
15:45:29 1825336895mS CD: CALL: 7.4.1 BState=Idle Cut=1 Music=0.0 Aend="Line 7" (3.3) Bend="" [] (0.0) CalledNum= () CallingNum=91712121212 (Alex ) Internal=0 Time=3 AState=Idle
15:45:29 1825336895mS CMCallEvt: c0a8018400000004 7.4.1 2259 Alog Trunk:7: StateChange: END=A CMCSIdle->CMCSDialInitiated
15:45:29 1825336895mS CMTARGET: c0a8018400000004 7.4.1 2259 Alog Trunk:7: LOOKUP CALL ROUTE: GID=1 type=0 called_party= sub= calling=91712121212 dir=in complete=1 ses=0
15:45:29 1825336896mS CMLOGGING: CALL:2015/12/1515:45,00:00:00,000,91712121212,I,,,Alex,,,0,,"",0,n/a
15:45:29 1825336897mS CD: CALL: 7.4.1 BState=Idle Cut=0 Music=0.0 Aend="Line 7" (3.3) Bend="" [] (0.0) CalledNum= () CallingNum=91712121212 (Alex ) Internal=0 Time=5 AState=Dialling
15:45:29 1825336897mS CD: CALL: 7.4.1 Deleted
15:45:29 1825336897mS CMTARGET: c0a8018400000004 7.4.1 -1 Alog Trunk:7: ~CMTargetHandler f1850f88 ep f1859218
15:45:29 1825336897mS CMCallEvt: c0a8018400000004 7.4.1 -1 Alog Trunk:7: StateChange: END=X CMCSDialInitiated->CMCSCompleted
15:45:29 1825336897mS CMCallEvt: 0000000000000000 0.9275.0 -1 BaseEP: DELETE CMEndpoint f1857398 TOTAL NOW=3 CALL_LIST=1
15:45:29 1825336897mS CMCallEvt: END CALL:2259 (f1858c8c)
 
Also.....

You said:
All 4 different incoming lines and they all go to the same incoming group

No they don't, Line 6 in the first call trace is group 0, but Line 7 in the second is group 1, it's hard to help with incorrect information :)


 
amriddle01, you should seen my face! I have looking at the Line ID from incoming call route section, once you pointed that out I knew where to look for. I got myself a copy of the IP monitor manual yesterday and will read more about it since it's extremely helpful for situations like this. I gladly and appreciate for the members that replied. Until next time (hopefully I can figure out myself), take care.
Thanks
 
If you got some good help to solve your issue AND you elearned something to better troubleshoot I the future why not give some stars?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top