Transfer to operator causing channel lock on Dialogic

[hms400]

I have encountered an issue when a caller, in all call scenerios, is transferred to the operator(could be 0 or another defined DN), the dialogic card looks to release this channel once transfer is complete but once the channel is hit again, there is RNA.

These dialogic channels are created as emulated 2616's and are in a group hunt. A pldn is assigned to this group. The strange thing is, to free up the channel that is locked, you dial it directly and it will answer. I am thinking it might be related to the PLDN of the hunt group, or some sort of call disconnect problems..

Any help would be great...

 

[johnpoole]

best cure is to buy a call pilot.. short of that, sounds more like the pldn is broke.. on the 16's (interface) add fna to the next channel.. shot in the dark.. then trac calls until you can catch the broken link, is it one channel? might be a patch but i do not know of any rls that needed a ght patch..

i would do a ld 80 entc x x x x 0100 on my set and test call untill i could duplicate the problem, down that channel and retest...

john poole
bellsouth business
columbia,sc

 

[hms400]

Yeah I wish we could use a CallPilot...they need the hospitality features though...The PLDN overrides any programming on the 2616's themselves so I am pretty sure it has something to do with the PLDN also. The transfer to operator eventually locks up all channels, just random were it starts.
That ld 80 is some sort of monitor? I should try that in my lab to see but I have been unable to reproduce this error.

Thanks

 

[MrPederman]

I was researching a similar problem and found Nortel pep MPLR21899. It is "View Only", so you would probably have to have a Nortel case and have them see if it is applicable to your problem, but here are the details.

The jist of it is that an Attendant transfered call does not have the correct "Call ID" information in the AML disconnect message.

****************************************
PEP Details

PEP ID MPLR21899 ISSUE 2
Old PEP Name N/A
Type PATCH
Machine CPP Generic And Release X21 04.50W
Status VO
Category GEN Included In Deplist(s) (PRODUCTION)
Included In Deplist(s) (TRIAL)
Site Dependent Yes
Fixed In Release X21 04.81I


Title

SCCS: Wrong Call ID in ONHOOK and DISCONNECT message when attendant release the call.

Problem Description

Setup:
---------
1) Set A is ACD agent set which is acquired by Symposium(SCCS 5.0) belongs to ACD Queue say xxxx.
2) Attendant set is configured in the same node.

Actions Performed
---------------------------
1) Set A logged into ACD Queue xxxx.
2) Set A calls Attendant.
3) Attendant answers the call on loop key 0.
4) Attendant press the release key.


Reponse
-----------
1) RTD display shows Set A is idle.
2) Call rings on the Attendant set of loop key 0. RTD of Set A is updated to Busy.
3) Call is established between Set A & attendant and USM active goes for Set A with Call ID say C1. And RTD of Set A is Busy.
4) Call is released and USM ONHOOK/DISCONNECT goes for Set A with invalid Call ID. And RTD of set A is
updated to IDLE.

The actual response should be USM ONHOOK/DISCONNECT for Set A should have the CAll ID C1.

ELAN16 O MTYP=1A USM TN=002 0 00 00 TIME=20:10:04
ELAN16 IN 59CE6950 OUT 00000000 QSIZE 00000000
ELAN16 03 36 00 00 00 08 16 1A 00 00 00 00 37 02 00 08 36 02 2A A5
ELAN16 3B 01 08 A3 01 01 38 01 04 3A 02 00 48 39 02 AF 10 3C 01 0B (Active)
ELAN16 96 04 00 00 01 0B 5F 07 1D 08 14 05 14 0A 04 Call ID C1 = 01 0B

ELAN16 O MTYP=1A USM TN=002 0 00 00 TIME=20:10:20
ELAN16 IN 59CEE5E7 OUT 00000000 QSIZE 00000000
ELAN16 03 28 00 00 00 08 16 1A 00 00 00 00 37 02 00 08 36 02 2A A5
ELAN16 3B 01 08 38 01 01 96 04 95 56 73 73 5F 07 1D 08 14 05 14 0A (Onhook)
ELAN16 14 Call ID = Corrupted

ELAN16 O MTYP=1A USM TN=002 0 00 00 TIME=20:10:20
ELAN16 IN 59CEE5EB OUT 00000000 QSIZE 00000001
ELAN16 03 28 00 00 00 08 16 1A 00 00 00 00 37 02 00 08 36 02 2A A5 (Di sconnect)
ELAN16 3B 01 08 38 01 05 96 04 FE EF 42 F0 5F 07 1D 08 14 05 14 0A Call ID = Corrupted.
ELAN16 14

 

[hms400]

Thanks a lot, I'll check out that patch, see if it is on the switch.