getting a internal error 2033 - problem on a PBX side

[qahsan]

Everyone,
We use Genesys for testing and we are trying to register the DNs that we have always used now gives us the error as follows:

Directory Number Registration Response
ReferenceID:0010
Result:Fail
Cause:2033

Genesys site gives us the detail of the error as follows:
Summary: Problem Registering Switch Objects
Problem Description: It looks as though a link is established with MLS 04.02.06 PEP NI040206U008S on server , but I am unable to register some PosIDs, Extns, or CDNs

Solution: From the TServer log, it shows me all the DN's you have configured in CME:
DN array
[112] dn = '4409' type = ext xtype = DN reg-mode = 0x1 = +force
[114] dn = '1409' type = pos xtype = Position reg-mode = 0x1 = +force
[117] dn = '4408' type = ext xtype = DN reg-mode = 0x1 = +force
[118] dn = '1408' type = pos xtype = Position reg-mode = 0x1 = +force
[115] dn = '4430' type = CDN xtype = RouteDN reg-mode = 0x1 = +force
[116] dn = '2430' type = ACD xtype = Queue reg-mode = 0x1 = +force
DN/EXR array

s> 1 Directory Number Registration
ReferenceID:0010
Associated DN List:0x81,4409

s< 1 Directory Number Registration Response
ReferenceID:0010
Result:Fail
Cause:2033

This message is a Switch Internal Error message, and should be taken up with your switch vendor as it implies a switch misconfiguration. Here are a few reasons which could cause this error:

1. The DN's you entered in CME do not exist on the switch.
2. SCCS has control of the DN's at the time TServer is trying to register them.

A database query on Cause 2033 definitely indicates that is a PBX configuration issue. Please check the above 2 items, and then contact your switch vendor.

----
With the solution they have provide:
i have already checked the DNs and they exist on the PBX.
I can turn the SCCS off and we are still getting the same error.
the only other thing i can think about is that the link isnt working from the Symposium to the Switch. Is there a command that i can use to check the Switch IP?

 

[atascoman]

You can go into LD 117 and do a PRT ELNK and that will show you the active and inactive IP addresses of the PBX. You can check the link status of the Symposium by going into LD 48 and entering STAT ELAN. This should show the ELAN IP of the Symposium server and should say that it is active when the server is online.

You can also stat the TNs of the phones you are trying to acquire with Genesys in LD 20 and it will show if they are acquired by Symposium. You wil see the ELAN number that is associated with the Symposium that showed in LD 48.

 

[janaya]

Bounce the TServer. Or engage Nortel. Nortel allows you to create CDNs and ACDNs so that third party applications can control these numbers for their product.

If the Genesys system cannot acquire, or I think they call it register, the number, the problem is usually in the TServer application.

If Genesys has still not purchased the Developer's Package from Nortel, they are only guessing on what the problem is.

Reboot the Tserver then the Stat Server and all those other Servers and you will probably be fine.

We put the Genesys on the Nortel as well, but it was a freaking disaster. Ended up way past the budget to get everything up and running.

My questions is, why did you go Genesys, when Symposium would have given you everything you needed, and the products are from the same vendor. I could never get than answer from my company.

Hope this helps, and good luck

John

 

[qahsan]

PRT elnk showed:
=> prt elnk
ACTIVE ETHERNET: "SWITCH" "172.16.64.98"
INACTIVE ETHERNET: "SECONDARY_ENET" "*****XYZ"
which is wrong so i did a "rst elnk active" and it shows as follows:
=> prt host
Cabinet # 0
ID Hostname IP Address
3 REMOTE_PPP_IF 100.1.1.1
7 LOCAL_PPP_IF ***
8 SECONDARY_ENET ***ABC
9 PRIMARY_ENET *****XYZ

with the PRT ELNK command:
=> prt elnk
ACTIVE ETHERNET: "PRIMARY_ENET" "*****XYZ"
INACTIVE ETHERNET: "SECONDARY_ENET" "****ABC"
OK

Now atleast i see the link is active on the switch side.

On the symposium server: i see the swithc IP: ****XYZ and switch type: MEridian/CSE 1000
ELAN: 137.135.128.XXX
RSM: 230.0.0.1

I dont know what this ELAN is for? It doesnt match any of the settings on the switch side.

The problem is still there even after the resetting the link.

Here is what LD 48 shows:
>ld 48
LNK000
.stat elan

SERVER TASK: ENABLED
ELAN #: 16 DES: sympos
APPL_IP_ID: 0 .0 .0 .0 LYR7: DOWN DSBL

.
It shows enabled? i guess its still down? how can i enable it?
thanks for all your help.

Janaya - i will get back to you and thanks for your reply.

 

[jebloome]

At this point, you may have to just reboot Symposium and the link may come back up. If that does not work, then you may have to shut down SYMPOSIUM, go to LD 137 and DIS ELNK, then ENL ELNK, then bring Symposium back up. That way the ELAN link between server and switch sync back up.

 

[qahsan]

jebloome.... restarting the symposium didnt fix the problem.

i had to
- shutdown the symposium
- disable the link
- enable the link
- restart the symposium
and it solved the issue. while the symposium was starting up it got enabled automatically:

TIM000 14:52 27/8/2007 CPU 0
dis elnk

OK
.enl elnk

OK
.
ELAN014 ELAN 16 host IP=137.135.128.XXX is enabled

I thank you so much for your advice. Thanks again!!

 

[qahsan]

Janaya – thanks for your earlier response.

Putting Genesys with Nortel is a disaster, no questions about it. But the functionality that Genesys gives is what we needed. for example, skill based routing, better interface etc etc. Its just like working with Assembly/C++ or Visual Basic. Where Assembly/C++ is a Nortel and Visual basic is your Genesys. Its not easy to get people for Switch nowadays than for Genesys. We are gold certified partners with Genesys and for us this Nortel – Genesys is just a lab environment where we do all our testing. We have products that you can use with Genesys, e.g screen popups that will get all the info on the customer before the representative would even answer the call. thus saving about 20~30 sec agents call time. These are the things you cannot do in Switch environment. I think it all ends up with saving your call stats and give a better customer service regardless of what you use but you are right it is a disaster to put the nortel with Genesys.

I am not sure how good you are in Genesys, but I got into this CTI field a year ago and for me learning Genesys was much easier than learning Switch side. If you know the switch side and brush up your skills in Genesys, no one compete that now adays. I hope this answer somewhat of your question if not all.
Thanks again for your response.