i ran sample in intellij idea, it has no problem, but if i build Artifacts and run it in console ( java -jar xxx.jar), it throws exception

May 16, 2018 3:44:22 PM com.avaya.mvap.svcproxy.prov.RemoteServiceProvider initServiceProviderImpl

INFO: CMAPI SERVER IP=192.168.11.230: CMAPI SERVER PORT=4721

Exception in thread "main" java.lang.NoSuchMethodError: org.exolab.castor.xml.Marshaller.setCstaXSDEdition(I)V

        at com.avaya.mvcs.proxy.CstaMarshaller.marshal(CstaMarshaller.java:146)

        at com.avaya.mvcs.proxy.CstaMarshallerNode$CstaMarshallerThread.run(CstaMarshallerNode.java:215)

        at com.avaya.mvcs.proxy.CstaMarshallerNode.processPacket(CstaMarshallerNode.java:113)

        at com.avaya.mvcs.proxy.AbstractPipelineNode.process(AbstractPipelineNode.java:130)

        at com.avaya.mvcs.proxy.Pipeline$PipelineSubscriber.inform(Pipeline.java:452)

        at com.avaya.common.eventservice.UnfilteredSubscription.notify(UnfilteredSubscription.java:70)

        at com.avaya.common.multicaster.Multicaster.notify(Multicaster.java:386)

        at com.avaya.common.channel.Channel.publish(Channel.java:115)

        at com.avaya.common.eventservice.EventService.publish(EventService.java:124)

        at com.avaya.common.eventservice.EventServiceManager.publish(EventServiceManager.java:156)

        at com.avaya.common.eventservice.Publisher.publish(Publisher.java:110)

        at com.avaya.mvcs.proxy.XmlGatewayClient.handleRequest(XmlGatewayClient.java:190)

        at com.avaya.mvcs.proxy.Pipeline.handleRequest(Pipeline.java:346)

        at com.avaya.mvcs.proxy.ClientProxy.routeRequest(ClientProxy.java:627)

        at com.avaya.mvcs.proxy.CstaSessionManagementServiceProxy.routeRequest(CstaSessionManagementServiceProxy.java:57)

        at com.avaya.mvcs.proxy.CstaSessionManagementServiceProxy.startApplicationSession(CstaSessionManagementServiceProxy.java:103)

        at com.avaya.mvcs.proxy.SessionManagementServiceProxy.startApplicationSession(SessionManagementServiceProxy.java:232)

        at com.avaya.mvcs.proxy.SessionManagementServiceProxy.startApplicationSession(SessionManagementServiceProxy.java:187)

        at com.avaya.mvcs.proxy.ClientProxy.sessionStart(ClientProxy.java:360)

        at com.avaya.mvcs.proxy.ClientProxy.<init>(ClientProxy.java:272)

        at com.avaya.mvap.svcproxy.prov.RemoteServiceProvider.initServiceProviderImpl(RemoteServiceProvider.java:197)

        at com.avaya.mvap.svcproxy.prov.ServiceProviderBuilder.getCmapiServiceProvider(ServiceProviderBuilder.java:195)

        at com.avaya.mvap.svcproxy.prov.ServiceProviderBuilder.getServiceProviderType(ServiceProviderBuilder.java:180)

        at com.avaya.mvap.svcproxy.prov.ServiceProviderBuilder.getServiceProviderImpl(ServiceProviderBuilder.java:112)

        at com.avaya.cmapi.ServiceProvider.getCmapiServiceProvider(ServiceProvider.java:404)

        at com.avaya.cmapi.ServiceProvider.getServiceProvider(ServiceProvider.java:390)

        at MyTest.main(MyTest.java:103)

how can i solve it ?

Avaya have written a version of Marshall.java that includes this method. It is important that your VM picks this version rather than the original.

I suspect that your Artifacts environment is picking up the standard castor library before the Avaya version. Make sure that avaya-castor-override.jar appears in your classpath before castor-1.0-xml.jar.

Martin

Thanks, it works. :)

i tested three ip phones (105, 135, 107) to record, tow has no problem, but 107 occurs every time.

May 17, 2018 1:30:28 PM com.avaya.mvcs.proxy.XmlGatewayClient processPacket

WARNING: 

java.lang.NoSuchMethodException: ch.ecma.csta.binding.CSTAErrorCode.getEventListenerId()

	at java.lang.Class.getMethod(Class.java:1786)

	at com.avaya.mvcs.proxy.XmlGatewayClient.processPacket(XmlGatewayClient.java:446)

	at com.avaya.mvcs.proxy.AbstractPipelineNode.process(AbstractPipelineNode.java:130)

	at com.avaya.mvcs.proxy.Pipeline$PipelineSubscriber.inform(Pipeline.java:452)

	at com.avaya.common.eventservice.UnfilteredSubscription.notify(UnfilteredSubscription.java:70)

	at com.avaya.common.multicaster.Multicaster.notify(Multicaster.java:386)

	at com.avaya.common.channel.Channel.publish(Channel.java:115)

	at com.avaya.common.eventservice.EventService.publish(EventService.java:124)

	at com.avaya.common.eventservice.EventServiceManager.publish(EventServiceManager.java:156)

	at com.avaya.common.eventservice.Publisher.publish(Publisher.java:110)

	at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread.run(CstaUnmarshallerNode.java:266)

	at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:57)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

	at java.lang.Thread.run(Thread.java:748)



May 17, 2018 1:30:28 PM com.avaya.mvcs.proxy.XmlGatewayClient processPacket

WARNING: 

java.lang.NoSuchMethodException: ch.ecma.csta.binding.CSTAErrorCode.getEventListenerId()

	at java.lang.Class.getMethod(Class.java:1786)

	at com.avaya.mvcs.proxy.XmlGatewayClient.processPacket(XmlGatewayClient.java:446)

	at com.avaya.mvcs.proxy.AbstractPipelineNode.process(AbstractPipelineNode.java:130)

DeviceID: [107:S8800:192.168.11.100:0]  startEvent

	at com.avaya.mvcs.proxy.Pipeline$PipelineSubscriber.inform(Pipeline.java:452)

	at com.avaya.common.eventservice.UnfilteredSubscription.notify(UnfilteredSubscription.java:70)

 starting Audio: remote=/172.16.11.102:10034, codec=g711U, packetsize=20, protocol=none

	at com.avaya.common.multicaster.Multicaster.notify(Multicaster.java:386)

Setting speaker codec to g711U, and packetSize to 20

	at com.avaya.common.channel.Channel.publish(Channel.java:115)

	at com.avaya.common.eventservice.EventService.publish(EventService.java:124)

	at com.avaya.common.eventservice.EventServiceManager.publish(EventServiceManager.java:156)

	at com.avaya.common.eventservice.Publisher.publish(Publisher.java:110)

	at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread.run(CstaUnmarshallerNode.java:266)

	at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:57)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

	at java.lang.Thread.run(Thread.java:748)

this problem is NoSuchMethodXXXXX, i don't know why this happened. tested on Intellij IDEA.

That looks more complex than can be handled on the forum. If you open a tech support ticket, I may be able to help you more with it. Please note, for non-paid members, there may be a fee for this service.

Martin

there are two types ip phone: 9630, 1608-I, 9630 is ok, 1608-I throws exception, same code and same operation. what's the difference between them ?

For 16XX phones, Communication Manager sends binary 1 followed by =to the display when the first call appearance goes off-hook. For other phone types, Communication Manager sends "a=". Binary 1 is not printable in XML so AE Services generates an exception and sends a coreCastor message to the application. It looks like the JAVA SDK is not handling this message very well.

The workaround is to configure your phone as a 96XX or 46XX.

Martin

i see, another question:

the AES version is 6.3.1, i use java api 6.3.1 to connect it , it's ok. but if i use 7.1.3 to connect, it can't connect aes.

prop.setProperty(CmapiKeys.SESSION_PROTOCOL_VERSION, APIProtocolVersion.VERSION_6_3_1);

both api protocol version are 6.3.1.

but the dashboard can connect it, why ?

I don't know why you cannot connect - I am able to connect 7.1.3 to my 6.3.3 AE Services.

I should point out that, what the product house calls "forward compatibility", was broken in DMCC Java SDK 7.1.1. Therefore, I recommend that you do not use any DMCC Java SDK later than 7.1.0 with an older AE Services.

Martin

using 7.0 api also can't connect aes 6.3.1, but this is not important now. there are three type ip phone: 9608, 9630, 1608-I,

two ip phones(9630, 1608-I) have this problem, using 9608 dials 9630 or 1608-I and and answered it, it will receive 1st starting audio, if i hang up 9608 first, it received stop audio and start audio, stop audio. so it will receives two MediaStartEvent and MediaStopEvent. waht is the problem?

Lamp 263 is now flashing.

The phone was answered

Extension: [107:S8800:192.168.11.100:0] 

 starting Audio: remote=/172.16.11.102:10052, codec=g711U, packetsize=20, protocol=none

Setting speaker codec to g711U, and packetSize to 20

Lamp 263 is now on.

The call has been established.

Lamp 263 is now off.

The other person hung up

Hung up the phone

 stopping Audio

Lamp 263 is now on.

The call has been established.

Extension: [107:S8800:192.168.11.100:0] 

 starting Audio: remote=/172.16.11.102:10038, codec=g711U, packetsize=20, protocol=none

Setting speaker codec to g711U, and packetSize to 20

Lamp 263 is now off.

The other person hung up

Hung up the phone

 stopping Audio

I suggest you put a DMCC Call Control monitor on 107 and sun "list trace station 107" on Communication Manager. These should give you a clearer picture of what is happening.

Martin

Is this the ip phone's problem? 105 (9630) receive cleared event twice.

Connection Cleared Event: 45

   Dropped Connection Id: Device Id: 117:S8800::0 Call Id:2137

   Releasing Device Id: 117:S8800::0

   User Data as String: 

   User Data as Text: 

   Event Cause:normalClearing

Connection Cleared Event: 45

   Dropped Connection Id: Device Id: 105:S8800::0 Call Id:2137

   Releasing Device Id: 105:S8800:192.168.11.100:0

   User Data as String: 

   User Data as Text: 

   Event Cause:normalClearing

Connection Cleared Event: 45

   Dropped Connection Id: Device Id: 105:S8800::0 Call Id:2139

   Releasing Device Id: 105:S8800:192.168.11.100:0

   User Data as String: 

   User Data as Text: 

   Event Cause:normalClearing

9630 can use call control monitor, 9608 return error, i don't know why ?

Start Monitor Response (Third Party Call Control):25 Error:<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><subscribedResourceAvailability>generic</subscribedResourceAvailability></CSTAErrorCode>

The second Connection Cleared event for 105 is for a different call (CallID 2139). This is probably due to some feature or configuration that you have set on one of the phones, but I do not know what one. If you run a 'list trace station' on 105, it may help you to figure it out.

From the TSAPI Programmers Reference:

GENERIC_SUBSCRIBED_RESOURCE_AVAILABILITY (41)
The request has failed for one of the following reasons:
– A required feature has not been provisioned or enabled. For example:
? The deviceID corresponds to a station with type “CTI” and the “CTI Stations” feature is not enabled on Communication Manager.
? The deviceID corresponds to a non-CTI station administered without hardware (AWOH) and the “Phantom Calls” feature is not enabled on Communication Manager.
? The deviceID corresponds to a SIP station, and the “Type of 3PCC Enabled” administered for the station is not set to “Avaya”.
? The device ID corresponds to a SIP station, and there is an off-pbx-telephone station-mapping administered for deviceID on Communication Manager.
– The TSAPI Service could not acquire the license(s) needed to satisfy the request.

Martin

list trace station 107 (1608-I) , 107 has two call id

10:06:22 TRACE STARTED 05/30/2018 CM Release String cold-03.0.124.0-21053

10:06:27     Calling party station      117 cid 0x964

10:06:27     Calling Number & Name 117 lijianwei, li

10:06:27     dial 107

10:06:27     ring station      107 cid 0x964

10:06:27     G711A ss:off ps:20

             rgn:1 [172.16.11.111]:34784

             rgn:1 [172.16.11.102]:10004

10:06:27     G711MU ss:off ps:20

             rgn:1 [172.16.11.149]:4726

             rgn:1 [172.16.11.102]:10028

10:06:27     xoip options: fax:T38 modem:PT tty:US  uid:0x34008b

             xoip ip: [172.16.11.102]:10028

10:06:29 SIP>PUBLISH sips:117@aura.chenguan.cn SIP/2.0

10:06:29     Call-ID: 802a9074cc60e8189815bfca2200

10:06:29     active station      107 cid 0x964

10:06:29 SIP<SIP/2.0 200 OK

10:06:29     Call-ID: 802a9074cc60e8189815bfca2200

10:06:30     idle station      117 cid 0x964

10:06:30     G711A ss:off ps:20

             rgn:1 [172.16.11.111]:34784

             rgn:1 [172.16.11.102]:10032

10:06:30     G711MU ss:off ps:20

             rgn:1 [172.16.11.149]:4726

             rgn:1 [172.16.11.102]:10002

10:06:30     xoip options: fax:T38 modem:PT tty:US  uid:0x34008b

             xoip ip: [172.16.11.102]:10002

10:06:30     idle station      107 cid 0x965

I still think you have enabled some feature on Communication Manager that is causing a second call to appear.

One thing that I think you should try is to create two new H.323 stations, of type 9620 and test with these. You may have some parameter changed in the existing stations that are causing the call flow to change. New, clean stations, may not have the same issue.

If you need further support on this, please open a tech support ticket. I have given as much help as I can on the forum.

Martin