Symposium failure to register DN

Voice & Telephony
1

We are running Genesys v5.1 with Symposium v3.

When we make a change to the ACD positionid on a handset, TServer/Symposium does not allow this new posid to be monitored. This only happens when the number assigned is one that has been used elsewhere previously. We get the following error in the tserver log file:

link: Directory Number Registration Response

    ReferenceID: 17152

    Result:Fail

    Cause:2034

@15:31:42.4333

** Registration failed… DN 1904, type 0x82, cause 0x2034: Bad resource ID

.R (reg
esp) rcr 1 conf 10:0 auto 5:1

@ 15:31:42.4813

<< ff 0a 00 11 01 c3 01 01 06 00 71 03 01 78 04 20 34

link: Directory Number Registration Response

    ReferenceID: 17153

    Result:Fail

    Cause:2034

@15:31:42.4820

** Registration failed… DN 1904, type 0x82, cause 0x2034: Bad resource ID

send__to_client 0x10010018(Stat_Server_510) message EventError

    (Bad resource ID)

    AttributeTimeinuSecs    482233

    AttributeTimeinSecs     998631102

    AttributeReferenceID    1171

    AttributeThisDN '1904'

    AttributeErrorCode      219

Has anyone seen this before?

Thanks

2

Hi, Ray,

the error comes from the link, you are right:

link: Directory Number Registration Response

ReferenceID: 17152

Result:Fail

Cause:2034

the problem seems to be that you do not have ACD position registered with Symposium/PBX.

  1. Does your ACD position 1904 exist in PBX?

  2. Is it registered with Symposium?

Open symposium client and check if you can see DN there. What is the current status next to it?

If both one and two check out, try to unacquire and unregister DN from symposium client and then register again.

Tell me if it did not work.

With best regards,

Vic

3

I suggest you check the T server documentation for the Symposium and check out the Error Messages.

From their Error 2034 seem to indicate that you have “Invalid Resource ID” which possibly means that DN does not exist or is not of the right type for Genesys to monitor. Refer to Release Notes as well.

4

Having done some more tests, we are now getting the following error in the TServer log:

05/07/02@16:50:42 client 31(VM Agent)message RequestAgentLogin

AttributeThisDN	'2402'

AttributeAgentID	'1200'

AttributePassword	''

AttributeAgentWorkMode	0

AttributeReferenceID	2

.rq (rq_next) dta[2402]

@ 16:50:42.6197

ff 0a 00 18 01 07 89 10 01 00 36 08 00 00 32 34 30 32 44 06 31 32 30 30

host: Login

ReferenceID: 1929

This Device DN:Unknown,2402

Agent ID:1200

.rq (rq_next) dta[2402]

@ 16:50:42.6268

<< ff 0a 00 19 01 87 89 10 02 00 36 08 00 00 32 34 30 32 71 03 01 78 04 20 31

link: Login Response

ReferenceID: 1929

This Device DN:Unknown,2402

Result:Fail

Cause:2031

!o (login
esp) nrl 0

parse_mlink_address: msg 1002 address 2402 apply 7

send__to_client 0x215a003a(VM Agent) message EventError

(The resource is not acquired by the application)

AttributeTimeinuSecs	628014

AttributeTimeinSecs	1020754242

AttributeReferenceID	2

AttributeThisDN	'2402'

AttributeErrorCode	216

sent to 31 (VM Agent)

The steps we took were as follows:

create new DN and ACD Position in Meridian, and acquire in Symposium

add DN & Position to Genesys (all works ok)

deacquire from Symposium

make a change to the Position (eg. different Q)

Reacquire in Symposium

attempt to login to client, & receive error message

We have also tried the above and added the step of disabling/deleting/unregistering from Genesys prior to making the change, but this doesn’t impact on the end result.

The Genesys documentation is very weak in terms of error messages, and I can’t find any documentation on error messages in Symposium can anyone point me in the right direction?

Hope someone can help with this!!

5

Hello,

On a Nortel Communication Server 1000 with SCCS / MLS, when such issues occur, we recreate the DNs in the pbx, set them to be controlled by Genesys CTI and then we create them.
It solves the problem every time.

2 Likes