updateRemoteDestination request problem with attributes isMobilePhone and enableMobileConnect in 10.0 and later release

[jdrinkwater]

updateRemoteDestination request problem with attributes isMobilePhone and enableMobileConnect in 10.0 and later release

I am having problem setting the fields using the following request. Looks like the fields are not setting in the database when you use AXL request. Is this a problem for anyone?

  <axl:updateRemoteDestination xmlns:axl="http://www.cisco.com/AXL/API/10.0">

   <destination>222</destination>

   <isMobilePhone>false</isMobilePhone>

   <enableMobileConnect>false</enableMobileConnect>

  </axl:updateRemoteDestination>

Thanks,

Jung

[npetrele]

Hi Jung,

It should probably be giving you an error message (I don't get one either), but you need to add this tag (which is the category tag in the Web UI):

<enableUnifiedMobility>true</enableUnifiedMobility>

Then it will set both isMobilePhone and enableMobileConnect to false for you.

[jdrinkwater · Accepted solution]

Hi Nick,

Thanks for the answer!!

When I add the tag <enableUnifiedMobility> it does the values. When I issue getRemoteDestination request, I don't see this tag. How do I know the current state of this tag? Or is this value derived from other tags. Am I missing something?

Thanks!

Jung

[npetrele]

Hi Jung,

Yes, you'd think it would be one of the getRemoteDestination tags, but it's not.  I don't know the minds of the developers, but I suspect it's taken for granted if isMobilePhone and/or enableMobileConnect are true, since these two settings only matter if enableUnifiedMobility is also set to true.  Perhaps you're right that it's derived, then.

I'll ping the developers on this and see if they need to add that tag to getRemoteDestination. 

[jdrinkwater]

Thanks Nick as always!