Author Message
DeepakBrar
Joined: Feb 12, 2010
Messages: 0
Offline
I am getting an Invalid Parameter return when trying to generate a third party device ID in the dashboard. The use case is a need to initiate a call to a customer (and detect when it is connected).

Now, for 'Get Dev Id.', this is the XML back and forth:

Outgoing XML 2
<?xml version="1.0" encoding="utf-8"?>
<GetDeviceId xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.avaya.com/csta">
<switchName>AVAYACLAN3</switchName>
<extension>4372</extension>
</GetDeviceId>
-----------------------
Incoming XML 2
<?xml version="1.0" encoding="UTF-8"?><GetDeviceIdResponse xmlns="http://www.avaya.com/csta"><device typeOfNumber="other" mediaClass="voice" bitRate="constant">4372::AVAYACLAN3:0</device></GetDeviceIdResponse>

The switch server name is 'AVAYACLAN3' and this works. However, when I try the 3rd party ID, here is the out and incoming XML:

Outgoing XML 3
<?xml version="1.0" encoding="utf-8"?>
<GetThirdPartyDeviceId xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.avaya.com/csta">
<switchName>AVAYACLAN3</switchName>
<extension>4372</extension>
</GetThirdPartyDeviceId>
-----------------------
Incoming XML 3
<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><operation>invalidParameterValue</operation></CSTAErrorCode>

Is there some sort of configuration that needs to be done?
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
looks like you have used the switch connection's name in as a DNS name where you would provision the CLAN or something...

here is a 3rd party get device ID request/response... note the location of the switch connection name in the response..after the first colon, not the second. It does not align with yours... I suggest you revisit the AE Services Administration and Maintenance guide in the section where it describes setting up switch connections for DMCC>

<?xml version="1.0" encoding="utf-8"?>
<GetThirdPartyDeviceId xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.avaya.com/csta">
<switchName>JtbCMSim</switchName>
<extension>32131</extension>
</GetThirdPartyDeviceId>
-----------------------
Incoming XML 3
<?xml version="1.0" encoding="UTF-8"?>
<GetThirdPartyDeviceIdResponse xmlns="http://www.avaya.com/csta">
<device typeOfNumber="other" mediaClass="notKnown" bitRate="constant">32131:JtbCMSim::0</device>
</GetThirdPartyDeviceIdResponse>

here is a first party get device ID exchange. note the IP address after the second colon, that is my CLAN/procr that I will register with from the H.323 Gatekeeper list associated with the switch connection.

<?xml version="1.0" encoding="utf-8"?>
<GetDeviceId xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.avaya.com/csta">
<switchName>JtbCmSim</switchName>
<extension>32131</extension>
</GetDeviceId>
-----------------------
Incoming XML 8
<?xml version="1.0" encoding="UTF-8"?>
<GetDeviceIdResponse xmlns="http://www.avaya.com/csta">
<device typeOfNumber="other" mediaClass="voice" bitRate="constant">32131:JtbCmSim:135.9.65.129:0</device>
</GetDeviceIdResponse>
DeepakBrar
Joined: Feb 12, 2010
Messages: 0
Offline
I discussed this with our AE Services administrator, and there is some confusion as to where the problem lies. I never get a deviceID with *anything* in the second spot (between the first and second colon), that goes for the first-party main device ID in the dashboard as well (the one that succeeds). But I am able to do first-party stuff like dial digits, etc. So apparently I can do that without the 'switch connection name' in the second spot of the device ID?
I am at the point in my own code where I can initiate a call, but I need to know when it connects. So I try to set up a thirdpartycontroller monitor and pass it the device ID I got from the standard getdeviceid call, and I get this error in the callcontrollerstartmonitorresponse callback:

<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><operation>generic</operation></CSTAErrorCode>

So I think I am back to the start once again, namely the problem with not being able to get a 3rd-party call control id.

Any ideas? I think the root of the problem must be a setup issue where the second spot on the device ID is never filled in - what does that mean? If I use an IP on the 1st-party getdeviceid, it has the IP in the third spot, if I use a DNS name it has that name in the third spot, but nothing ever in the 2nd spot.

I noticed something in the docs about how a standard device ID can also work as a 3rd-party device ID sometimes? What is the setup to allow that to happen?

Thx for the help.
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
it means you are using DNS names, and the administrator has not provisioned the H.323 Gatekeeper list associated with the switch connection name. It may also mean that the administrator may well have the same switch connection name as the DNS name for the system making things fairly confusing. Sit down with the Administration and Maintenance guide for AE Services, and go through the section about configuring for DMCC and Call Control services while you are logged into the AES OA&M web interface.

Your problem is not just 3rd party device IDs.
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
PS, I have never seen things configured this way. Consult the Administration manual to make sure DNS is fully supported in this context.
DeepakBrar
Joined: Feb 12, 2010
Messages: 0
Offline
Got this working finally, we were using the wrong IP/DNS - the CLAN instead of the H.323 gatekeeper. Thanks for your help.
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
yea!

not sure I understood what you found wrong though. If you get a chance to post it perhaps it may help someone else who has made the same mistake.
Go to:   
Mobile view