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

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

It is working. Thanks.

However when I initiate "Reconnect" with dead session it is throwing error on Session Start event "Could not re-establish existing session".

Documentation says it generates new session when the sessionid is not active.

I have a web application that uses DMCC. A device is registered under one instance of application. If another instance try to use the same device, the previous instance should show logged off. To achieve that, From second instance, I am reconnecting to the session I created in the first instance. After reconnect to the session, I am terminating that session and starting new session with second instance. However I am not sure how to show log off on the first instance when we terminate the reconnected session from the second instance. Can we see any event firing on first instance when the reconnected session terminated on second instance?

In my scenario I need to start monitor on 4343 which should be acd. But I can not make this to acd because of the following

Huntgroup can not be administered as ACD if message center is Remote Voice Mail.

What are my alternatives?

Can you please clarify on which number you started monitor for the second delivery event to happen? Is it on the group 103 or extension 40803 or member station 40204?

I have a scenario like this

1) Hunt group 99
2) Huntgroup extension 4343 (not acd)
3) Member station T00124 (not skill)


Modular messaging is a SIP adjunct W/ virtual SIP stations

We tried to make hunt group extension as acd but we got this error

Huntgroup can not be administered as ACD if message center is Remote Voice Mail.

What are my options here?

I am seeing DeliveredEvent with incoming call. If I don't answer it and goes to voice mail, Is there any event that shows my call is connected to voice mail?. It is not firing Established event.

If I have 200 agents working on 200 different sessions and all belongs to same hunt group, my code will create 200 monitors on hunt group one per session. Is there any limit on how many monitors we can start on hunt group?

Is there any setting at AES that is affecting other agents when I stop huntgroup monitor from one session that makes other agents logged off

Sorry, I am confused. This is how I understand this.

In the application from the same instance of service provider start 2 sessions. One for Agent and another for Hunt group. Then the application should get logged events. Right?

Can I can end both sessions at the end when I dispose the service provider object without affecting any other agent logins associated with the same hunt group that are originated from other instances of application.

I tried the same scenario you explained and the events fired on Hunt Group dashboard. Is there a way to get these events on Agent's Phone dash board? I need this information of Agent's side for couple of reasons.

1) I am head set user and if the head set is off, CM will make the phone logged off. The only the applicatiuon knows about this is by getting logged events on agents application.

2) I need to capture some information of logged events.

I tried the same scenario you explained and the events fired on Hunt Group dashboard. Is there a way to get these events on Agent's Phone dash board? I need this information of Agent's side for couple of reasons.

1) I am head set user and if the head set is off, CM will make the phone logged off. The only the applicatiuon knows about this is by getting logged events on agents application.

2) I need to capture some information of logged events.

I checked with dashboard and it is working. I checked DMCC logs on AES and the xml posted is same from my code and dashboard and still login event is not happening for scenario 2

This is triggering Agent Login/Logout events. I am not sure this is the right way of doing. If different phones are registered to the same Hunt Group under different instances of the code below and logging of from one of the instances is making all phones loggedoff.

1) serviceProvider.StartApplicationSession
2) OnStartApplicationSessionResponse
   a) GetDeviceID for Phone
3) OnGetDeviceIdResponse   
   a) StartMonitor for Phone
4) OnStartMonitorResponse
   a) serviceProvider.getThirdPartyCallController.GetThirdPartyDeviceId for Phone      
   b) Register Terminal Phone
   c) serviceProvider.getThirdPartyCallController.GetThirdPartyDeviceID For Hunt Group
5) OnGetThirdPartyDeviceIdResponse
   a) serviceProvider.getThirdPartyCallController.StartMonitor for Phone
   b) serviceProvider.getThirdPartyCallController.StartMonitor for Hunt Group
6) OnRegisterTerminalResponse
   a) Login

7) This is firing
   a) serviceProvider.getThirdPartyCallController.OnAgentLoggedOnEvent
   b) serviceProvider.getThirdPartyCallController.OnAgentLoggedOffEvent




So I tried this. I created 2 instances of ServiceProvider. This is not firing AgentLogin/Logout events.

Instance 1:
1) serviceProvider.StartApplicationSession
2) GetDeviceID for For Hunt Group
3) serviceProvider.getThirdPartyCallController.StartMonitor for Hunt Group


Instance 2:

1) serviceProvider.StartApplicationSession
2) OnStartApplicationSessionResponse
   a) GetDeviceID for Phone
3) OnGetDeviceIdResponse   
   a) StartMonitor for Phone
4) OnStartMonitorResponse
   a) serviceProvider.getThirdPartyCallController.GetThirdPartyDeviceId for Phone      
   b) Register Terminal Phone
5) OnGetThirdPartyDeviceIdResponse
   a) serviceProvider.getThirdPartyCallController.StartMonitor for Phone
6) OnRegisterTerminalResponse
   a) Login

7) No AgentLoggedIn/LoggedOff events

Agent login and logout events are firing when I implemented start call monitor on hunt group device id, but when I stop monitor on hunt group device id it is making all devices under the hunt group to logoff even with different AES sessions.

Setting true to Controllable by other sessions worked for getdeviceid. However it failed registering the terminal

RegisterTerminalResponse: '<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><stateIncompatibility>invalidDeviceState</stateIncompatibility></CSTAErrorCode>