A call to RouteRegister for Device 6923 (a VDN) returns the following error - why?

Outgoing XML 6
<?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">6923:CM:10.90.15.102:0</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>labme1-cm</switchNameList>
</RouteRegisterPrivateData>
</private>
</privateData>
</extensions>
</RouteRegister>
-----------------------
Incoming XML 6
<?xml version="1.0" encoding="UTF-8"?>
<CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<operation>generic</operation>
</CSTAErrorCode>

TIA
Martin

Please check the AE Services /opt/mvap/logs/dmcc-trace.log.0 file at the corresponding moment in time. The information it provides is sometimes more helpful. If the exception there is not helpful, enable TSAPI tracing using the information in this FAQ.

https://devconnect.avaya.com/secure/faq/d_faq.jsp?f=1&q=423#q423

routing services require a TSAPI Advanced license to be available. Check WebLM and verify one is available for the link type. Depending on the AE Services release TSAPI Advanced licensing varies. Up through release 4.x there was a TSAPI_ADVANCED_USER license, along with a SMALL, MEDIUM, LARGE AEC license required. (SMALL equates to S8300, MEDIUM (S8400 & S8500) Large S8600 and above). In AE Services release 5, the TSAPI ADVANCED USER license is subsumed into the AEC license.

There are other conditions on a successful route register. For example the deviceID represents a VDN, and that some other application is not already registered for route requests on that VDN. Please review the error responses in the TSAPI for Communication Manager Programmer's Reference document associated with the method request you are making.

The problem was the missing TSPI_ADVANCED_USER license. Thanks for the hint