12-22-2011 10:02 AM - edited 03-19-2019 04:09 AM
We have ICM 8.5.1 and Avaya CM 5.2 with AES 4.2.3. When we send calls to the ACD using a Translation Route, the call arrives on the appropriate VDN and executes the correct Adjunct steps in the Vector but the PIM log the following errors:
11:07:22:707 PG1A-pim1 Trace: ASAI_RECV => 217: asai_errno=-20 Bri:1 !SaoID 12100 C_EN_REP (C_REQUEST) C_OFFERED SwCID 7736 Trk 6240 DecodedTrk 198 Dom[Type VDN Val 1971738] Clng 6154457355 Cld 1971738 UUI[len 0 Prot ?? Data (NULL)] User[len -2147483648 Type NUSE] DNIS (NULL)
11:07:22:707 PG1A-pim1 Trace: Bri/SAOid: 1/12100; C_OFFERED (NEW): [Dom VDN 1971738] Cid=7736 Clng=6154457355 Cld=1971738 UU=None TrkInfo=[342/198 NON [0]] Dom=[C_VDN [12] 1971738]
Clct=13 Timeout=16842752 IncUdata=None PriLvl=C_NUSE_LONG Iflow=C_NUSE_LONG QTime=[-1:-1:-1] Dnis=(NULL)
11:07:22:707 PG1A-pim1 Trace: Call::SetSourceConnectionID: CID: 7736 DeviceID: D293901 DevIDType: 1
11:07:22:707 PG1A-pim1 Trace: Call SourceConnectionID [CID 7736 Dev D293901 Type 1]
11:07:22:707 PG1A-pim1 Trace: C_OFFERED: called_num=1971738 is copied into dnis_chars[1971738] of private Data
11:07:22:707 PG1A-pim1 Trace: Callid=7736 AddPartyToList[1, D293901] Total 1
11:07:22:707 PG1A-pim1 Trace: CSTA DELIVERED,
PrivData=[UU=None Consult[CID 0 Dev DevType 1] II 0
Alert[Handle -1 Type LT_UNKNOWN] ANI 6154457355
dnis_chars [1971738] UCID 0x11E3800
TG 342 Tk 198 Mult 1]
LoginDigits [] CallPrompt []
CallID = 7736 DeviceID = D293901 DeviceType = Dynamic
Alerting = 1971738
Calling = 6154457355
Called = 1971738
Redirection =
LocalState = INITIATE
Cause = EC_NEW_CALL
The full log is attached.
01-12-2012 01:15 PM
Ah, well, even after opening a TAC case, I had to solve my own issue. I'll put the solution here in hopes it will help someone else.
Ultimately, I decided to look back over my PG configuration since I noticed in the PIM log that I wasn't even receiving a Route Request. I fould that I had mistakenly set the PIM to use ASAI SignalID Link 1 for Post-Route instead of Link 2. I correctly set it to monitor Link 2, which explains why I could see agent and VDN data, but without Post-Route on Link 2, the PG never received the Route Request.
See the attached screenshot for reference.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide