Avaya - TServer connection error

[RN]

Hi Guys,

Iam facing an issue while trying to do the connection between the Avaya PBX and the Avaya TServer ...I have checked the avaya DLG port configuration and it seems to be correct .But the port state shows as not connected ...

A snipet of the error is given below.

@18:19:40.2360 [tsgctm] Link [1,s0] Changing state to 1
(tcp_connect_handler) 10.64.130.70:5678 is connected on socket [360]
@18:19:40.2360 [tsgctm] Link [1,s1] Rx UP_PACKET
@18:19:40.2360 [tsgctm] Link [1,s1] openSession
@18:19:40.2360 [tsgctm] Link [1,s1] Changing state to 2
@18:19:40.2360 [asai] Link [1,s2] (sysReqSessionOpen)
@18:19:40.2360 [asai] No CRVs allocated.
18:19:40.236 Trc 31000 Connection Request: Link[1], link number[1], protocol(1)
@18:19:40.2360 [31000] Connection Request: Link[1], link number[1], protocol(1)
TP_ConnectionRequest
Link number: 1
Protocol: 1
@18:19:40.2360 [>>] 01 00 00 02 01 01
@18:19:40.2520 [<<] 02 0B 00 01 66
TP_ConnectionAccepted
Link status: Down
Link: BRI port busied-out or not administered
18:19:40.252 Trc 31002 Connection Progress: Link[1], progress [Success], reason [Connected]
@18:19:40.2520 [31002] Connection Progress: Link[1], progress [Success], reason [Connected]
18:19:40.252 Trc 31001 Connection Accepted: Link[1], status [Down], reason [BRI port busied-out or not administered]
@18:19:40.2520 [31001] Connection Accepted: Link[1], status [Down], reason [BRI port busied-out or not administered]
@18:19:40.2520 [asai] Link [1,s2] (sysReqSessionClose)
TP_DisconnectNotification

Has anyone seen this error before ?

[Daimonas]

Sounds like the link is not administered on the switch. Based on the logs, I can see you connecting to the MapD but when the MapD attempts to communicate with the switch, the switch reports it is down.

If you call Genesys Support and ask for David's G3 Avaya Guide, they will send it to you.  I did a quick search for it and I don't have it handy.

[IanDS]

I concur....if you post the configuration of the pabx and your tserver settings I will take a look

[Chattguy]

Do a status bri-port on your MAPD card and see what is returns.  It should look like this...

                        STATUS BRI-PORT


            Port: 01D0601                          Version: 3
    Service State: in-service          Active NCA-TSC Count:
Maintenance Busy?: no
    Layer 1 State: activated

      TEI Value  Layer2 State    Endpt Extension    Endpt SPID  Service SPID?

Link1    3      l3-established        2772

Link2

Link3




If not then you may have to verify that the MAPD is programmed right.

If that does not work try to busy out the MAPD or do a MSHUT and reboot the MAPD.

It should be one of the two, most likely the MAPD programming if it has never established and if you have established a connection before the MSHUT will work.
                                                   

[rn]

Hi Guys,

It seems like it was an mapd configuration issue ..we changed the mapd card and it worked out well

thanks for your help