We're receiving this error when trying to register a device through DMCC. We've compared the switch connection settings on this AES box with another AES box that works fine and don't see any differences. We don't even have a H323 GK defined on the AES box having this problem or one of our other AES boxes that are working fine. The AES box with the error below is 6.2, the working AES box is 6.1.

2013-10-02 16.45.20,707 :T-76: com.avaya.platform.broker.impl.AsyncServiceMethodImpl invoke
WARNING: Exception when calling method.invoke
java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:601)
   at com.avaya.platform.broker.impl.AsyncServiceMethodImpl.invoke(AsyncServiceMethodImpl.java:164)
   at com.avaya.workflow.impl.RouterImpl.routeRequest(RouterImpl.java:97)
   at com.avaya.mvcs.proxy.CstaRouter.routeRequest(CstaRouter.java:173)
   at com.avaya.mvcs.proxy.CstaRouterService.routeRequest(CstaRouterService.java:141)
   at com.avaya.mvcs.proxy.CstaRouterNode.processPacket(CstaRouterNode.java:349)
   at com.avaya.mvcs.proxy.AbstractPipelineNode.process(AbstractPipelineNode.java:130)
   at com.avaya.mvcs.proxy.Pipeline$PipelineSubscriber.inform(Pipeline.java:427)
   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:123)
   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:255)
   at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:56)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
   at java.lang.Thread.run(Thread.java:722)
Caused by: ch.ecma.csta.errors.InvalidParameterValueException: java.lang.IllegalArgumentException: [swlink1:0.0.0.0:52323:0] No GK IP address is available for switch=swlink1
   at com.avaya.cmapi.intsvc.CstaTerminalImpl.register(CstaTerminalImpl.java:451)
   at com.avaya.cmapi.intsvc.CstaTerminalImpl.registerTerminal(CstaTerminalImpl.java:652)
   at com.avaya.cmapi.extsvc.H323RegistrationServices.registerTerminal(H323RegistrationServices.java:100)
   ... 22 more
Caused by: java.lang.IllegalArgumentException: [swlink1:0.0.0.0:52323:0] No GK IP address is available for switch=swlink1
   at com.avaya.mvcs.station.h323.ras.DefaultTerminalDevice.privateRegisterDevice(DefaultTerminalDevice.java:686)
   at com.avaya.mvcs.station.h323.ras.DefaultTerminalDevice.registerDevice(DefaultTerminalDevice.java:634)
   at com.avaya.mvcs.station.h323.H323Station.privateRegisterDevice(H323Station.java:307)
   at com.avaya.mvcs.station.h323.H323Station.registerDevice(H323Station.java:285)
   at com.avaya.mvcs.station.h323.H323Station.registerSharedDevice(H323Station.java:251)
   at com.avaya.mvcs.terminal.h323.TerminalH323.privateRegisterDevice(TerminalH323.java:387)
   at com.avaya.mvcs.terminal.h323.TerminalH323.registerDevice(TerminalH323.java:288)
   at com.avaya.mvcs.terminal.h323.TerminalH323.registerSharedDevice(TerminalH323.java:234)
   at com.avaya.cmapi.intsvc.TerminalSession.registerDevice(TerminalSession.java:174)
   at com.avaya.cmapi.intsvc.CstaTerminalImpl.register(CstaTerminalImpl.java:437)
   ... 24 more

Firstly, RegisterTerminal is case sensitive. Make sure the switch name is correct.

Secondly, try restarting the DMCC service. New GK configuration will not take effect until the service has been restarted.

Martin

The switch name is correct and we tried restarting both the TSAPI and DMCC services

I forgot to add that we do have the tracing levels set to finest so if it would help to provide the entire dmcc-trace file, I can do that.

Chack that you can make a Third Party call using the DMCC Test utility on the AE Services Web Interface. It's under the Utilities -> Diagnostics -> AE Services menu.

If that doesn't work, try using the TSAPI Test utility to make the call.

I dont see a DMCC test utility but the TSAPI test utility worked

If you want me to take a look at your traces, you can open a ticket using the "Technical Support" menu. As you are a Registered Developer, there will be a fee for this service.

Martin