Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
679
Views
0
Helpful
5
Replies

addRemoteDestinationProfile - missedCallLogging and consecutiveRingSetting on line element

stephan.steiner
Spotlight
Spotlight

‎01-28-2015 11:22 AM

Hi

Could it be that these two properties are not being taken into account? If I set them as follows

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/10.5">

  <soapenv:Header/>

  <soapenv:Body>

  <ns:addRemoteDestinationProfile sequence="1">

  <remoteDestinationProfile>

  <name>RDP_testing</name>

  <description>Added rdp profile SGRO</description>

  <product>Remote Destination Profile</product>

  <class>Remote Destination Profile</class>

  <protocol>Remote Destination</protocol>

  <protocolSide>User</protocolSide>

  <callingSearchSpaceName uuid="{DBBD54BA-AFDC-F929-67BF-AEA95C281A39}">CSS_intern</callingSearchSpaceName>

  <devicePoolName uuid="{1B1B9EB6-7803-11D3-BDF0-00108302EAD1}">Default</devicePoolName>

  <networkHoldMohAudioSourceId>51</networkHoldMohAudioSourceId>

  <userHoldMohAudioSourceId>1</userHoldMohAudioSourceId>

  <lines>

  <line>

  <index>1</index>

  <display>display name</display>

  <dirn>

  <pattern>7306</pattern>

  <routePartitionName>p_phones</routePartitionName>

  </dirn>

  <ringSetting>Ring</ringSetting>

  <consecutiveRingSetting>Flash Only</consecutiveRingSetting>

  <displayAscii>testline 7601</displayAscii>

  <e164Mask>058777XXXX</e164Mask>

  <mwlPolicy>Use System Policy</mwlPolicy>

  <maxNumCalls>2</maxNumCalls>

  <busyTrigger>1</busyTrigger>

  <callInfoDisplay>

  <callerName>true</callerName>

  <callerNumber>false</callerNumber>

  <redirectedNumber>false</redirectedNumber>

  <dialedNumber>true</dialedNumber>

  </callInfoDisplay>

  <recordingFlag>Call Recording Disabled</recordingFlag>

  <audibleMwi>Default</audibleMwi>

  <speedDial/>

  <partitionUsage>General</partitionUsage>

  <associatedEndusers>

  <enduser>

  <userId>testuser</userId>

  </enduser>

  </associatedEndusers>

  <missedCallLogging>false</missedCallLogging>

  <recordingMediaSource>Gateway Preferred</recordingMediaSource>

  </line>

  </lines>

  <callInfoPrivacyStatus>Default</callInfoPrivacyStatus>

  <userId>testuser</userId>

  <ignorePresentationIndicators>false</ignorePresentationIndicators>

  <rerouteCallingSearchSpaceName uuid="{BC3B6B1C-ADF4-2B1D-F723-4A927AAFFE89}">CSS_UNRESTRICTED</rerouteCallingSearchSpaceName>

  <useDevicePoolCgpnTransformationCss>true</useDevicePoolCgpnTransformationCss>

  <userLocale>English United States</userLocale>

  <networkLocale>Switzerland</networkLocale>

  <dndOption>Call Reject</dndOption>

  <dndStatus>false</dndStatus>

  </remoteDestinationProfile>

  </ns:addRemoteDestinationProfile>

  </soapenv:Body>

</soapenv:Envelope>

Then do a get, the values do not match my addRemoteDestinationProfile command

<?xml version='1.0' encoding='UTF-8'?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

  <soapenv:Body>

  <ns:getRemoteDestinationProfileResponse xmlns:ns="http://www.cisco.com/AXL/API/10.5">

  <return>

  <remoteDestinationProfile ctiid="79" uuid="{6B08E5A6-3890-48E6-CB50-8450958B86DF}">

  <name>RDP_testing</name>

  <description>Added rdp profile SGRO</description>

  <product>Remote Destination Profile</product>

  <model>Remote Destination Profile</model>

  <class>Remote Destination Profile</class>

  <protocol>Remote Destination</protocol>

  <protocolSide>User</protocolSide>

  <callingSearchSpaceName uuid="{DBBD54BA-AFDC-F929-67BF-AEA95C281A39}">CSS_intern</callingSearchSpaceName>

  <devicePoolName uuid="{1B1B9EB6-7803-11D3-BDF0-00108302EAD1}">Default</devicePoolName>

  <networkHoldMohAudioSourceId>51</networkHoldMohAudioSourceId>

  <userHoldMohAudioSourceId>1</userHoldMohAudioSourceId>

  <lines>

  <line uuid="{C49A45E3-583F-6351-1857-8B452097DBCA}">

  <index>1</index>

  <label/>

  <display>display name</display>

  <dirn uuid="{83B08C35-EB20-BB52-E08E-E567CCAB16E7}">

  <pattern>7306</pattern>

  <routePartitionName uuid="{82056F6A-7CF2-48DA-BDEB-9E17B12DE19D}">p_phones</routePartitionName>

  </dirn>

  <ringSetting>Ring</ringSetting>

  <consecutiveRingSetting>Use System Default</consecutiveRingSetting>

  <ringSettingIdlePickupAlert />

  <ringSettingActivePickupAlert />

  <displayAscii>testline 7601</displayAscii>

  <e164Mask>058777XXXX</e164Mask>

  <dialPlanWizardId />

  <mwlPolicy>Use System Policy</mwlPolicy>

  <maxNumCalls>2</maxNumCalls>

  <busyTrigger>1</busyTrigger>

  <callInfoDisplay>

  <callerName>true</callerName>

  <callerNumber>false</callerNumber>

  <redirectedNumber>false</redirectedNumber>

  <dialedNumber>true</dialedNumber>

  </callInfoDisplay>

  <recordingProfileName/>

  <monitoringCssName/>

  <recordingFlag>Call Recording Disabled</recordingFlag>

  <audibleMwi>Default</audibleMwi>

  <speedDial />

  <partitionUsage>General</partitionUsage>

  <associatedEndusers>

  <enduser>

  <userId>testuser</userId>

  </enduser>

  </associatedEndusers>

  <missedCallLogging>true</missedCallLogging>

  <recordingMediaSource>Gateway Preferred</recordingMediaSource>

  </line>

  </lines>

  <callInfoPrivacyStatus>Default</callInfoPrivacyStatus>

  <userId>testuser</userId>

  <ignorePresentationIndicators>false</ignorePresentationIndicators>

  <rerouteCallingSearchSpaceName uuid="{BC3B6B1C-ADF4-2B1D-F723-4A927AAFFE89}">CSS_UNRESTRICTED</rerouteCallingSearchSpaceName>

  <cgpnTransformationCssName/>

  <automatedAlternateRoutingCssName/>

  <useDevicePoolCgpnTransformCss>true</useDevicePoolCgpnTransformCss>

  <userLocale>English United States</userLocale>

  <networkLocale>Switzerland</networkLocale>

  <primaryPhoneName/>

  <dndOption>Call Reject</dndOption>

  <dndStatus>false</dndStatus>

  <mobileSmartClientProfileName/>

  </remoteDestinationProfile>

  </return>

  </ns:getRemoteDestinationProfileResponse>

  </soapenv:Body>

</soapenv:Envelope>

Labels:
0 Helpful
5 Replies 5

amoherek
Cisco Employee
Cisco Employee

‎02-03-2015 03:52 PM

Hi Stephan,

When you create a new remote destination profile, you have the option of adding a line by <line> or  <lineIdentifier>. I don't believe the intent of addRemoteDestinationProfile is to ALSO be able to change the property values of those lines. I can double check with the team, but I'm pretty sure this is why the changes aren't going into effect. You would normally update a line's configuration via updateLine.

thanks,

Adrienne

0 Helpful

stephan.steiner
Spotlight
Spotlight
In response to amoherek

‎02-04-2015 12:34 AM

Adrienne

I think we have a misunderstanding there.. the naming is a bit unfortunate, given that we have what is called in ccmadmin a 'DirectoryNumber', and in AXL, you get that object using getLine/addLine/updateLine. And in a phone, device Profile and remote Destination Profile, we have a tag called <lines>.. and it contains a refernce to a Directory number (<dirn>), and inside the <line> tag, a bunch of properties that ccmadmin Shows in a Directory number (when editing a Directory number associated to a device), but they really are part of the device as far as axl is concerned (they are in the devicenumplanmap table in the database).

Graphically speaking, under <lines><line>, we have this object: XPhoneLine

addRemoteDestinationProfile-cucm105.PNG

Note that the tags I mentioned are part of it.. thus, you should be able to set them using addRemoteDestinationProfile (and addPhone, addDeviceProfile - the same tags can be used for those two commands, but they fail for addRemoteDestinationProfile).

I hope that explains what I mean.. I really mean tags that are part of the remote Destination Profile, not the Directory number (those I can set just fine using addLine/updateLine).

0 Helpful

npetrele
Cisco Employee
Cisco Employee

‎02-04-2015 11:39 AM

Hi Stephan,

If you navigate through the CUCM web interface, go to a remote destination profile, and then click on the line to review the line, you'll see that the checkbox to log missed calls is not there.  I assume this is because CUCM has no control over the logging of missed calls on a remote line (such as a home landline or cell phone).  You'll only see that option when you edit a line for a CUCM device/phone. 

So it doesn't surprise me that the option isn't saved.  I'm not sure why the missed call tag is even available with remoteDestinationProfile. Perhaps it is because it's defined by XPhoneLine as you pointed out, so it's there because it's part of the default definition of a line. 

0 Helpful

stephan.steiner
Spotlight
Spotlight
In response to npetrele

‎02-09-2015 10:18 AM

@Nicholas: In this case, shouldn't the documentation be updated to not list those tags in the add/updateRemoteDestination commands?

0 Helpful

npetrele
Cisco Employee
Cisco Employee
In response to stephan.steiner

‎02-10-2015 07:31 AM

Personally, I'd update the docs to say that such-and-such tags are ignored for remote destination profiles because...etc.  That retains the consistency of the Line information.  That would be my personal preference, but your mileage may vary.

0 Helpful
Customers Also Viewed These Support Documents