Thanks Martin!

Yes it is a 4610 phone.

I am trying to monitor a SIP phone registered to Session Manager using TSAPI. It appears that I am successfully monitoring the phone, but I do not see any events when the call starts such as established or connected. At the end of the call I get a connection cleared with no call data associated with it.


2016-07-28 11:43:40.566 Info 0 Channel 0[4000] Type: CTI_EVENT_AVAYA_TSAPI 8216(56) CSTA_CONNECTION_CLEARED IP:
2016-07-28 11:43:40.566 Info 0 Channel 0[4000] Msg==>timeReceived=11:43:40.507|eventType=56|eventClass=4|monitorCrossRefId=1|callID=41|releasingDevice=4000|droppedConnection=4000<==

Environment:

CM 6.3
AES 6.3.3
SM 6.3.4

This may seem like a strange question, but I need to have the full name for the IP_API_I licenses. I do not know the second A in the IP_API_I stands for. Does anyone know?


I have not bee able to find it online of in any of the documentation.

Do the DMCC stations require their own station RTU license when the Multiple regisitration method is used?

We have purchased the latest MLS spec and believe that our recording integration is subscribing to the skillset properly, but we are still not seeing it in the calloffered event. Is there specific configuration in the CCM 7 that is required in order for us to receive the skillset?

We currently use MLS to capture CTI events and are looking to capture the skillset of calls. Everything I found says this is available in the CALLOFFERED messaging, but we are currently not getting this information. I found a similar post, https://www.devconnectprogram.com/forums/posts/list/17409.page#p70692, that states that "The MLS spec is licensed. In the latest spec there is a new IE required in the application registration message to enable skillset content in the messaging", but i cannot find any information on the this IE in the forum or MLS spec documents.


My question is what licensing/IE is required and what configuration is needed in order to get the skillset information in the MLS messaging.

Thank you very much!

Can the multiple registration method be used to record devices with auto-exclusion enabled? If so, has been supported since multiple registration was first supported?

A customer recently requested information on how much bandwidth was required for the TSAPI client. Are there figures that I can use to calculate this based on the call volume?

I am trying to record a IV Callmaster using multiple registration and I am getting:
"Error   0   DEVICE [26589] did not register: Registration Reject reason: undefinedReason
Shared control denied because of incompatible set type - only DCP and IP phone w/speaker are allowed."

I found in the AES Programmer's guide I found that the Physical Device Services does not support devices without a speaker phone.
"Devices that are not equipped with a speaker-phone (e.g. CallMaster) are not supported."

Is this the reason that I am not able to register the Callmaster phones?

In the "Developing client-side ip call Recording Applications" (https://devconnect.avaya.com/public/download/AES/WhitePapers/AEServicesCallRecording_SVC4050.pdf) guide I noticed it states
"Note: It is not possible to register a DMCC device against a SIP extension. In practice, this means that the Multiple Devices method cannot be used to record calls at SIP extensions. However, it is possible to record calls at SIP extensions using the Service Observing or Single Step Conferencing methods, provided the extension is at an Avaya SIP station, such as a 1600 or 9600 series telephone, that supports third-party call control."

Has that changed in a recent release?

I am familiar with using dependent mode to record H323 stations and understand that you can not register the station unless a the station has already been registered. Is there a reason that we cannot use dependent mode with SIP stations? Are there any other differences between the behavior of SIP stations and H.323 stations when using multiple registraton?

I am trying to investigate possible ways of recording SIP stations and was wondering if it would be possible to perform a Single Step Conference or to Service Observe SIP stations though the Session Manager in the future. If not is there a similar method I should be looking into?


Thanks

Are there any plans for adding a Single Step Conference or Service Observe feature to the toolkit for Session Manager?