We have a product that emulates a softphone on DMCC.

At some sites (one in particular), we are seeing an issue very often where our phone disconnects, but in our disconnection process, the DMCC server sends our client an error message, which then makes our software misbehave and take a few minutes to reconnect.

The actual error from DMCC is "Station must be unregistered before it can be released - current state=UNREGISTERING"

The AES log file disconnection processing looks like this;
FINE: invokeID= 34 Routing request=session[session A9FA09AF86CD5FE53C0B9276494E3042-51] ch.ecma.csta.binding.MonitorStop@1ab594f
2013-03-21 11.46.56,433 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed PhysicalDeviceListener: crossRef=100:[Holder]: [150016:JHLABSVR1:10.38.105.50:0] ,com.avaya.cmapi.monitor.PhysicalDeviceListenerImpl@a87977,session A9FA09AF86CD5FE53C0B9276494E3042-51
2013-03-21 11.46.56,433 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed RegistrationListener: crossRef=100:[Holder]: [150016:JHLABSVR1:10.38.105.50:0] ,com.avaya.cmapi.monitor.RegistrationListenerImpl@1637d13,session A9FA09AF86CD5FE53C0B9276494E3042-51
2013-03-21 11.46.56,433 com.avaya.cmapi.monitor.MonitoringServicesImpl releaseCrossRefId
FINE: released crossRefID=100: 1 are now in use, 79999 still available.
2013-03-21 11.46.56,433 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: removed monitor=100
2013-03-21 11.46.56,434 com.avaya.cmapi.monitor.MonitoringServicesImpl stopMonitor
FINE: stopped monitor=100: 1 remain in use, 79999 still available.
2013-03-21 11.46.56,435 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 34 Received com.avaya.platform.broker.impl.AsyncResponse@75cea3 in response to session[session A9FA09AF86CD5FE53C0B9276494E3042-51] ch.ecma.csta.binding.MonitorStop@1ab594f
2013-03-21 11.46.56,441 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 35 Routing request=session[session A9FA09AF86CD5FE53C0B9276494E3042-51] com.avaya.csta.binding.UnregisterTerminalRequest@11cb8e0
2013-03-21 11.46.56,443 com.avaya.mvcs.terminal.h323.TerminalH323 unregisterDevice
FINE: [10.38.105.50:150016:0] state=UNREGISTERING
2013-03-21 11.46.56,443 com.avaya.mvcs.station.h323.ras.DefaultTerminalDevice cancelQ931DisconnectTimer
FINE: [10.38.105.50:150016:0] cancelling Q931Disconnect timer
2013-03-21 11.46.56,443 com.avaya.mvcs.station.h323.ras.DefaultTerminalDevice unregisterDevice
FINE: [10.38.105.50:150016:0] Client API call - unregisterDevice
2013-03-21 11.46.56,447 com.avaya.mvcs.station.h323.ras.OutgoingRASHandlerImpl fireURQ
FINE: [10.38.105.50:150016:0] send unregistration request (URQ)
2013-03-21 11.46.56,477 com.avaya.cmapi.intsvc.CstaTerminalImpl freeAesLicense
FINE: [10.38.105.50:150016:0] : Attempting to release AES license
2013-03-21 11.46.56,477 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 35 Received com.avaya.platform.broker.impl.AsyncResponse@75cea3 in response to session[session A9FA09AF86CD5FE53C0B9276494E3042-51] com.avaya.csta.binding.UnregisterTerminalRequest@11cb8e0
2013-03-21 11.46.56,481 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: invokeID= 36 Routing request=session[session A9FA09AF86CD5FE53C0B9276494E3042-51] com.avaya.csta.binding.ReleaseDeviceId@91a9c7
2013-03-21 11.46.56,481 com.avaya.cmapi.extsvc.DeviceServicesImpl releaseDeviceID
FINE: [150016:JHLABSVR1:10.38.105.50:0] :session[session A9FA09AF86CD5FE53C0B9276494E3042-51] Client API call
2013-03-21 11.46.56,481 com.avaya.workflow.impl.RouterImpl routeRequest
WARNING: A service method threw an Exception when invoked!
ServiceMethod: com.avaya.platform.broker.impl.ServiceMethodImpl@a68180[com.avaya.cmapi.extsvc.DeviceServicesImpl@1e940b, public com.avaya.csta.binding.ReleaseDeviceIdResponse com.avaya.cmapi.extsvc.DeviceServicesImpl.releaseDeviceID(com.avaya.csta.binding.ReleaseDeviceId) throws ch.ecma.csta.errors.InvalidDeviceIDException,ch.ecma.csta.errors.InvalidDeviceStateException,ch.ecma.csta.errors.InvalidParameterValueException]
Exception: ch.ecma.csta.errors.InvalidDeviceStateException: [150016:JHLABSVR1:10.38.105.50:0] Station must be unregistered before it can be released - current state=UNREGISTERING
Request: session[session A9FA09AF86CD5FE53C0B9276494E3042-51] com.avaya.csta.binding.ReleaseDeviceId@91a9c7
java.lang.reflect.InvocationTargetException

Should I be waiting for the UNREGISTER command to complete before I call the release command? Which event on the DMCC .NET object can be used to do that?

Thanks John. I have modified our solution to use multiple DMCC devices, but from a licensing perspective we should definitely look into the pager option.

Sorry for posting this here, I can't find a pure CM forum

We use DMCC to create a softphone, which listens for crisis alerts.

We have encountered a customer which uses the TN (Tenant Number) field on the station to split their sites, This means that when someone dials 911 on a specific phone, only the crisis alert station with the same TN as that phone gets the alert.

My question: Is it possible to configure a crisis alert station that gets the alert regardless of Tenant Number?

Thanks Rohan

We established (with some help from Avaya), that our app was generating many more session ids than we thought. This accounted for the additional lines.

Once we resolved that, the logs stopped growing so fast

Thanks Anthony and John

I will go back and ask them to look at the list history form, and I will also compare their view to our lab system logs.

I can confirm that our app does maintain session ids, we raise about 6 new session ids per hour. The client is seeing these log lines multiple times per second, resulting in the wtmp file groing by GBs every day.

I will ask them to raise an Avaya support request.

We have a client that says they are seeing multiple logins on the CM logs for the user account that we use through AES SMS to query phones.

Does the following log snippet in fact mean login / logout?

_begin quote_

wtmp files are filled with these:
sentry ssh 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)
sentry pts/0 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)
sentry ssh 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)
sentry pts/0 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)
sentry ssh 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)
sentry pts/0 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)
sentry ssh 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)
sentry pts/0 10.201.6.136 Mon Apr 30 23:59 - 23:59 (00:00)

_end quote_

If it does mean login / logout, would AES log in and out of CM multiple times per second if we were only making one call a second or fewer?

If not, what does it mean?

Thanks!

Excellent, thanks for that.

Thanks John, that is what I had thought too.

Is there an upper limit of 250 locations?

Hi John

it stands for Emergency Location Extension, and is the value that is filled in at the bottom of page 2 (I think) in the SAT change station command.

The location is (I think), the combination of Building, Floor and Room on the station info.

What is the maximum number of ELE's that can be used in a CM Deployment?

Someone from a reseller mentioned that ELEs are tied to Locations in CM, and CM can only support 250 locations.

Is this correct? From what I understand, an AWOH extension is created for every ELE in a well-configured environment, and in that scenario the limitation will be the amount of extensions that can be configured.

Excellent, thanks John

We developed a product against IPCode, which was the earliest version of CM and AES known to be a "good version"

For our solution's minimum requirements, I now need to know what versions of AES and CM we worked against.

I thought it was AES 4.2 and CM 4.2, but have been told that there is no such thing as CM 4.2, it stopped at 4.0.x

So, for clarity, exactly what versions of AES and CM were shipped in the last IPCode?

Thanks!

Is it possible to query / update the station button assignments (as accessed by the "change station nnnnn" SAT command) using the AES SMS Service?

I looked through the list of objects but nothing jumped out at me as being an obvious fit for querying that data.

Thanks!

Thanks John

As usual that second link took me to exactly what I needed :-)

We have an application that interacts with Avaya Aura using DMCC and AES SMS

Are either of these supported on Avaya IP Offfice? If not, are there alternatives that provide the same features (listing CM data via AES, creating a softphone using DMCC)?

Thanks!