Hi Joel,

You're right, the isue happened at a customer site.
I will tell the customer to start the described service process.

But because the problem occurs in combination with our recording application, the customer forces us to resolve the issue.

It is very important for us to see the progress in solving this problem, and also to get the patch, if required.

Please can you confirm, that this issue is definitely caused by Avaya and not by our application?

Ragrds,
Claus

We are working with release 4.2.1.
(r4-2-1-20-5-0)

Hello,

our application uses DMCC CallControl services and MediaControl services.

After successfully registering the listeners, the application runs for some time without any problems.
But several times a day, the application unexpectedly receives a ServerConnectionDownEvent.

Each time this event occurs, we can find the following entries in the AES mvap-error.log:

2009-03-09 12.53.39,767 com.avaya.cs.callcontrol.delegs.CCSEventHandler eventDistributorException
WARNING: Unexpected exception from the CCS event distributor. Shutting down session and removing listeners.
java.lang.ArrayIndexOutOfBoundsException: 2 > 1
   at java.util.Vector.insertElementAt(Vector.java:558)
   at ch.ecma.csta.binding.CompoundCallState.addLocalConnectionState(CompoundCallState.java:86)
   at com.avaya.cs.callcontrol.delegs.Csta1To3.snapshotDeviceResponseInfo1to3(Csta1To3.java:492)
   at com.avaya.cs.callcontrol.handlers.SnapshotDeviceConfHandler.generateResponse(SnapshotDeviceConfHandler.java:69)
   at com.avaya.cs.callcontrol.handlers.CallControlConfHandler.handleConf(CallControlConfHandler.java:149)
   at com.avaya.java.tsapiInterface.TSInvokeID.setConf(TSInvokeID.java:49)
   at com.avaya.java.tsapiInterface.TsapiEventDistributor.handleEvent(TsapiEventDistributor.java:119)
   at com.avaya.java.tsapiInterface.TsapiEventQueue.run(TsapiEventQueue.java:96)

In consequence, all listeners are forced to unregister and our application has to re-register all devices.

How can we find out the reason for those connection problems?

Ragards,
Claus

John,

thanks for the information.

Please can you explain the license restriction in more detail.
What kind of licenses are included? And how is it possible to bind the included licenses to specific applications?

Our application mainly needs TSAPI Basic licenses (for CallControlServices) and IP_API_A licenses (for MediaControl).
Are there any restrictions in installing these license types on a CM Express?

Regards,
Claus

I have an additional question concerning the license issue:
Wha

Hello,

please, can anyone tell us the new scheduled release date for the upcoming CM 5.2 ?

Initially, the release has been targeted for Feb 2, 2009.

Thanks.

Regards,
Claus

Hello,

we've developed a DMCC-based call recording solution that is working fine win a full-featured CM and AES environment.

Now we need to know, if the whole DMCC functionality is also provided by a Communication Manager Express solution, which is an integrated single-server system for small & medium business.

The product description of CM Express tells us, that there is an 'AES for CTI' included, but we do not know, if this AES is fully compatible with a standalone AES.

Regards,
Claus.

Hello,

our recording application uses SSC to connect a softphone to a call that we want to record.
After the SSC is established, the RTP packets are sent out to the target address/port, that are set during initialization of the soft phone.

Now the question:
Is there a way to have the calls RTP packets sent to two different target adresses simultaneously, without connecting a second softphone to the call?

Regards,
Claus

Hi John, hi Nick,

are there any news concerning the release date of CM 5.2?

Regards,
Claus

Hi Nick,

Can you please give us a status update for that issue?

Will there be a CM fix in the near future that retrieves the dialed digits out of the ISDN INFORMATION messages and provides them to the DMCC interface as called number?

What about the implementation of NetworkReachedEvent you've mentioned earlier. Will it be definitely included in AES 5.0? Is there already a scheduled release date for AES 5.0?

Unfortunately, we're now in a situation, that the number of an external called party is delivered correctly in the EstablishedEvent at one of our cutomer installations in the Netherlands (you've been involved in that case a few weeks ago).
On the other hand, we still do not get the external number on our lab system in Germany.

We are not sure, but it seems that the dutch ISDN behaves different from the german ISDN at that point.

Regards,
Claus

Hi Nick,

As requested, I've created a ticket in DevConnect (#05310).
Hope that helps to accelerate this issue.

Thanks.

Regards,
Claus

Hi Nick,

the number of our customers, that are complaining about the missing external numbers, increases steadily.

Is there any chance to accelerate the realease of the CM fix you've mentioned in your last postings?

Is CM 5.2 release still scheduled for Feb 2009?

Regards,
Claus

Hi Dave,

Thank you for that information.

Is it planned to support 'ButtonPressedEvent' with DMCC in the near future?

Regards,
Claus

Hello,

The AES 4.2 Programmers Guide says 'You cannot choose independent or dependent dependency mode with SIP endpoints'.

What is the reason for that restriction?
Is there a plan to support SIP phones in these modes in an upcoming AES release?

Regards,
Claus

Hi Dave,

I'm not sure if we are talking about the same thing.

So let me try to explain, what we want to do.

Assume we have two Extensions A and B, talking with each other. After A while, a button sequence (e.g. '123#') is pressed on ext. A.
Now we want our application to get informed about the event, that the buttons '123#' have been pressed on ext. A.

To use 'ButtonPressedEvent' is not possible, as this event is not implemented in DMCC yet.

So we've tried to use ToneCollectionServices and attached ToneCollectionListeners to both devices.
The result is, that we now get informed about the button presses by receiving TonesRetrievedEvents for both extensions. But unfortunately, we still are not able to detect, on which extension these buttons are actually pressed.

Is there a way to find out the source of button presses with DMCC?

Regards,
Claus

Yes, I mean the dial-pad buttons.

Claus