Hello,

Sorry for the bother again, but I have a question regarding an error I'm getting when attempting to RouteRegister, which is outstandingReqLimitExceeded. Now, I can understand getting the error if I'm attempting to register the same device on multiple servers, however I am getting it if I simply attempt to register multiple routes. For example, I can register 2504 and 2522 separately, but not ever at the same time, even across different sessions.

Is this a licensing concern? Is it possible the way it was set up by our engineers these two are somehow linked?

Thanks for your time.

I may have found the answer, though I'm still not 100% clear on it.

As per: https://downloads.avaya.com/elmodocs2/cmapi/docs/api/doc-files/12.2.14ErrorValue.html

12.2.14.5 Subscribed Resource Availability Errors

Error values in this category shall indicate that the service request could not be fulfilled because a required resource must be purchased or contracted by the client system. This category shall include one of the following specific error values:
generic - This is a general purpose value to be used when the server is unable to be any more specific about the cause of the error.
- objectMonitorLimitExceeded - The service request would exceed the server�s limit of monitors for the specified object.
- trunkLimitExceeded - The service request would exceed the server�s limit of trunks.
- outstandingRequestsLimitExceeded - The service request would exceed the servers�s limit on the number of outstanding service requests.
- objectRegistrationLimitExceeded - This service request would exceed the switching function�s limit on the number of registrations for this device.

So - licensing then?

Adjunct Routing requires a TSAPI Advanced license, rather than a TSAPI Basic license.

As far as I know, one TSAPI Advanced license will allow any number of TSAPI applications on a single AE Services to register as a routing service for any number of VDNs on one Communication Manager. There are three flavours of license (Small, Medium and Large), depending on the size of the Communication Manager.

In your case, as you can register for one VDN, I assume you have a valid TSAPI Advanced license. Therefore, you should be able to register for any number of VDNs, as long as they are all on the same Communication Manager. The only limitation is that only one application can register as a routing service per VDN.

When I tested this in my lab, I saw the behavior I expected, ie:

1. A could register as a routing service for several VDNs using one or more application.
2. If I registered for a VDN using one application and then attempted to register for the same VDN using a different application, I got an OUTSTANDING_REQUEST_LIMIT_EXCEEDED as only one application can register per VDN.
3. If I tried to register for a VDN twice using the same application, I was successful as the AE Services is able to tell that there was only one service registering.

Therefore, I do not see how this could be a licensing problem. I am also not aware of any configuration on the Communication Manager that could cause your problem.

BTW. According to the TSAPI Programmers Guide (DMCC uses TSAPI to provide routing and other third party services):
OUTSTANDING_REQUEST_LIMIT_EXCEEDED (44) – The specified routing device already has a registered routing server.

Martin

Thanks for the answer Martin.

I hope this formats properly, it is a print out of the request / response from our AES server when I'm asking to RouteRegister.

I can register 2522 and 2504 - but not at the same time in the same application. This shows that I can stop monitoring one in order to monitor the other.

I am starting the session as version 6.1

---------------------

Outgoing XML 11

<?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">2522</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 11 

<?xml version="1.0" encoding="UTF-8"?>

<RouteRegisterResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">

  <routeRegisterReqID>80084</routeRegisterReqID>

</RouteRegisterResponse>

---------------------

Outgoing XML 12

<?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">2504</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 12 

<?xml version="1.0" encoding="UTF-8"?>

<CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">

  <subscribedResourceAvailability>outstandingReqLimitExceeded</subscribedResourceAvailability>

</CSTAErrorCode>

---------------------

Outgoing XML 13

<?xml version="1.0" encoding="utf-8"?>

<RouteRegisterCancel 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">

    <routeRegisterReqID>80084</routeRegisterReqID>

</RouteRegisterCancel>

-----------------------

Incoming XML 13 

<?xml version="1.0" encoding="UTF-8"?>

<RouteRegisterCancelResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3" />

---------------------

Outgoing XML 14

<?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">2504</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 14 

<?xml version="1.0" encoding="UTF-8"?>

<RouteRegisterResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">

  <routeRegisterReqID>80086</routeRegisterReqID>

</RouteRegisterResponse>

---------------------

Outgoing XML 15

<?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">2522</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 15 

<?xml version="1.0" encoding="UTF-8"?>

<CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">

  <subscribedResourceAvailability>outstandingReqLimitExceeded</subscribedResourceAvailability>

</CSTAErrorCode>

---------------------

Outgoing XML 16

<?xml version="1.0" encoding="utf-8"?>

<RouteRegisterCancel 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">

    <routeRegisterReqID>80086</routeRegisterReqID>

</RouteRegisterCancel>

-----------------------

Incoming XML 16 

<?xml version="1.0" encoding="UTF-8"?>

<RouteRegisterCancelResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3" />

---------------------

Outgoing XML 17

<?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">2522</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 17 

<?xml version="1.0" encoding="UTF-8"?>

<RouteRegisterResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">

  <routeRegisterReqID>80088</routeRegisterReqID>

</RouteRegisterResponse>

Thanks for all your time.

Your problem goes beyond what I can handle on the forum. If you want me to investigate further, you will need to open a Technical Support ticket using the "Devconnect Support" menu above.

Please note that, for non-paid members, there is a fee for this service.

Martin

Thanks for your continued help Martin. :)
I will discuss with the higher ups and go from there.

Hey Martin,

I have been doing some research and I thought perhaps some additional information may lead to a better understanding of my issue - now that I have been playing with routing for a while.

I believe my issue stems from putting in an incorrect device ID - the VDN in which I am monitoring in 2504, and my switch is swlink1...

When I simply put in 2504 in the deviceid, and swlink1 - I believe I begin to monitor everything, not just 2504, as that is when I can no longer put in a second device and get outstandingReqLimitExceeded. However, if I put in 2504:swlink1:<ip>:0 it still registers but I no longer get any RouteRequest requests.

Do you think you could assist me in the correct syntax needed to register for routing requests on VDN 2504 on switch swlink1?

Thanks

Ok... so something I learned today. If you attempt to use a deviceId that doesn't actually exist, it would appear that sessionbecomes a routing server for all adjunct routes - with that said, for my deviceId, I used 2504:::0, and a switch of swlink1 and everything works properly. I can register that, then 2521:::0 on the same switch, turn them up an down individually, etc.

I'm not sure if it's because I know nothing about phones / Avaya, or if these syntax's are really obscure and difficult for others to figure out - with next to no examples on what should be used in these fields.

Either way, I'm 99.99% sure I've got this working and again appreciate the assistance you've given me.