Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » Device, Media and Call Control (Archive - Oct 2013 and earlier) » RouteRegister is monitoring other routes than requested   XML
 
Author Message
KishorePinnamaneni



Joined: 10/01/2014 17:55:39
Messages: 1
Offline

Using dashboard, I started session. Went to Routing services tab and registered route 2101 using deviceid and switch name. Registration is successful. However it is delivering events from other routes. Events from other routes showed
under the Route Register Req ID generated by route (2101)


Also I am receiving "performanceLimitExceeded"


Please see the xml communication and events received.



Outgoing XML 2
<?xml version="1.0" encoding="utf-8"?>
<RouteRegister xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<routeingDevice typeOfNumber="other" mediaClass="notKnown">2101</routeingDevice>
<extensions>
<privateData>
<private>
<RouteRegisterPrivateData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.avaya.com/csta">
<switchNameList>swlink1</switchNameList>
</RouteRegisterPrivateData>
</private>
</privateData>
</extensions>
</RouteRegister>
-----------------------
Incoming XML 2
<?xml version="1.0" encoding="UTF-8"?>
<RouteRegisterResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<routeRegisterReqID>80004</routeRegisterReqID>
</RouteRegisterResponse>
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<RouteRequest xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<crossRefIdentifier>51179239</crossRefIdentifier>
<routeRegisterReqID>80004</routeRegisterReqID>
<currentRoute>
<deviceIdentifier typeOfNumber="explicitPrivate:localNumber" mediaClass="notKnown" bitRate="constant">3502:SWLINK1::0</deviceIdentifier>
</currentRoute>
<callingDevice>
<deviceIdentifier typeOfNumber="explicitPrivate:localNumber" mediaClass="notKnown" bitRate="constant">2517216352:SWLINK1::0</deviceIdentifier>
</callingDevice>
<routedCall>
<callID>397</callID>
<deviceID typeOfNumber="other" mediaClass="notKnown" bitRate="constant">3502:SWLINK1::0</deviceID>
</routedCall>
<routeSelAlgorithm>normal</routeSelAlgorithm>
<extensions>
<privateData>
<private>
<RouteRequestPrivateData xmlns:ns1="http://www.avaya.com/csta" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="RouteRequestPrivateData">
<trunkGroup>3</trunkGroup>
<trunkMember>4</trunkMember>
<callLinkageData>
<globalCallData>
<globalCallLinkageID>
<globallyUniqueCallLinkageID>00001003971382731129</globallyUniqueCallLinkageID>
</globalCallLinkageID>
</globalCallData>
</callLinkageData>
</RouteRequestPrivateData>
</private>
</privateData>
</extensions>
</RouteRequest>
-----------------------
Incoming XML 9999
<?xml version="1.0" encoding="UTF-8"?>
<RouteEnd xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<crossRefIdentifier>51179239</crossRefIdentifier>
<routeRegisterReqID>80004</routeRegisterReqID>
<errorValue>
<performanceManagement>performanceLimitExceeded</performanceManagement>
</errorValue>
</RouteEnd>





Route Register Response: 2
Route Register Req ID: 80004
Route Request Event:
Algorithm: normal
Calling Device: 2517216352:SWLINK1::0
Globall Unique Call Linkage Id: 00001003971382731129
Current Route: 3502:SWLINK1::0
Event Cause:
-------- Look Ahead Information Start
InterFlow Priority: Undefined
Interflow Type: Undefined
Source Vdn:
Hours:
Minutes:
Seconds:
-------- Look Ahead Information End
Routed Call:
Device Id: 3502:SWLINK1::0
Call Id: 397
Route Register Req ID: 80004
Routing Cross Ref ID: 51179239
Trunk Group: 3
Trunk Member: 4
User Data:
-------- User Entered Code Start
Collect VDN:
Data:
User Entered Code Type: Undefined
User Entered Code Indicator: Undefined
-------- User Entered Code End
-------- Device History Start
-------- Device History EndRoute End Event:
Route Register Req ID: 80004
Error: performanceLimitExceeded
MartinFlynn



Joined: 30/11/2009 05:00:18
Messages: 1323
Offline

Hi Kishore,

DMCC uses TSAPI for Routing. Therefore, you may be able to learn more from the TSAPI traces on the AE Services. In particular, I don&#039;t think I have come across the performanceLimitExceeded error before. This error will have been generated from a TSAPI error. The TSAPI error may be easier to decypher.

There are instructions for enabling TSAPI traces in the devconnect FAQ "What is the procedure for enabling and accessing the AE Services logs for TSAPI (trace, tracing, g3trace, csta_trace)?". The csta trace file will show the communication between the DMCC & TSAPI systems. The g3 traces will show the messages to/from the Communication Manager. These may give you a clearer picture of what is happening.

You should be able to get a clue as to the meaning of the error from the document "TSAPI for Avaya Communication Manager Programmer&#039;s Reference".

Martin
KishorePinnamaneni



Joined: 10/01/2014 17:55:39
Messages: 1
Offline

I will look in to the error scenario. Why other routes fired under registered route?
JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 384
Location: Thornton, CO
Offline

In TSAPI if you route register without a device ID, what happens is you are registering for adjunct-route requests from all VDNs. I suspect for some reason that is what is happening to you. As Martin indicates you will need to get the TSAPI trace associated with the route register and see if the deviceID you are providing to DMCC is being seen properly by TSAPI and being shown in the TSAPI trace.
JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 384
Location: Thornton, CO
Offline

In TSAPI if you route register without a device ID, what happens is you are registering for adjunct-route requests from all VDNs. I suspect for some reason that is what is happening to you. As Martin indicates you will need to get the TSAPI trace associated with the route register and see if the deviceID you are providing to DMCC is being seen properly by TSAPI and being shown in the TSAPI trace.
 
 
Go to: