AddH323Gateway AXL Example.

Unanswered Question
Jun 16th, 2008

Hello, Anyone have a working ADDh323Gateway?

I keep getting: "The specified Protocol Side is not valid for this device"

Which doesnt make sense because here is my ADD post... also here is a matching GET post showing the same protocol to protocol side to device relationship... what is going on?

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <axl:addH323Gateway xmlns:axl="http://www.cisco.com/AXL/1.0" xsi:schemaLocation="http://www.cisco.com/AXL/1.0 http://192.168.200.200/schema/axlsoap.xsd" sequence="1234"> <gateway uuid=""><name>Test</name><description>Test</description><product>H.323 Gateway</product><model>H.323 Gateway</model><class>Gateway</class><protocol>H.225</protocol><protocolside>Network</protocolside><devicePoolName>Default</devicePoolName></gateway> </axl:addH323Gateway> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

---

GET

---

<gateway>

<uuid>{4091AAA2-AEDD-4856-9DA9-4E95B1C6777C}</uuid>

<name>Training01</name>

<description>Training01</description>

<product>H.323 Gateway</product>

<model>H.323 Gateway</model>

<class>Gateway</class>

<protocol>H.225</protocol>

<protocolSide>Network</protocolSide>

<callingSearchSpaceName />

<devicePoolName>Default</devicePoolName>

<networkLocation>Use System Default</networkLocation>

<networkHoldMOHAudioSourceId>0</networkHoldMOHAudioSourceId>

<userHoldMOHAudioSourceId>0</userHoldMOHAudioSourceId>

<loadInformation />

<versionStamp />

<traceFlag>false</traceFlag>

<mlppDomainId>-1</mlppDomainId>

<mlppIndicationStatus>Off</mlppIndicationStatus>

<preemption>Disabled</preemption>

<retryVideoCallAsAudio>true</retryVideoCallAsAudio>

<waitForFarEndH245TerminalSet>true</waitForFarEndH245TerminalSet>

<mtpRequired>false</mtpRequired>

<callerIdDN />

<callingPartySelection>Originator</callingPartySelection>

<callingLineIdPresentation>Default</callingLineIdPresentation>

<displayIEDelivery>false</displayIEDelivery>

<redirectOutboundNumberIE>false</redirectOutboundNumberIE>

<redirectInboundNumberIE>false</redirectInboundNumberIE>

<enableInboundFaststart>false</enableInboundFaststart>

<enableOutboundFaststart>false</enableOutboundFaststart>

<codecForOutboundFaststart>G711 u-law 64K</codecForOutboundFaststart>

<significantDigits>99</significantDigits>

<calledPartyIENumberType>Cisco CallManager</calledPartyIENumberType>

<callingPartyIENumberType>Cisco CallManager</callingPartyIENumberType>

<calledNumberingPlan>Cisco CallManager</calledNumberingPlan>

<callingNumberingPlan>Cisco CallManager</callingNumberingPlan>

<tunneledProtocol>None</tunneledProtocol>

<pathReplacementSupport>false</pathReplacementSupport>

</gateway>

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
risiprekel Mon, 06/16/2008 - 12:17

NEVERMIND.

CASE will get you everytime. Notice it should be protocolSide not protocolside.

Actions

This Discussion