This document was generated from CDN thread
Created by: Shaun McDonnell on 28-04-2010 06:46:10 PM
I have a customer who is using CUCM 7.1.3. Everytime my application attempts to send a 'startMedia' xml request message, the phone returns me a <CiscoIPPhoneError Number="1" />.
This doesn't make any sense to me as the error message it is returning isn't in the new 'Component API' format that I am expecting. Furthermore, this works on other customer's systems running the same version of CUCM.
Also, I know the startMedia XML message is correct as I am able to post the same message to a phone on a different CUCM install and it works fine.
Any idea what might be causing this to happen? Thanks.
-Shaun
Subject: RE: startMedia Component API
Replied by: David Staudt on 28-04-2010 08:08:13 PM
Error=1 suggests there is a formatting problem with the request - some phones are more lenient than others in allowing small variances.
Can you provide a network packet capture (Wireshark) of the sequence from the phone's PC switch port? This will show the exact request/response.
Subject: RE: startMedia Component API
Replied by: Shaun McDonnell on 28-04-2010 08:13:05 PM
Actually, now that I look at it further, it seems that the problem is with a 7960 phone. Do the 7960s even support 'startMedia' messages? Thanks.
-Shaun
Subject: RE: startMedia Component API
Replied by: David Staudt on 28-04-2010 09:22:56 PM
If you are referring to the 'RTPx:' URIs then yes: these are supported by 7940/60 phones.
Subject: RE: startMedia Component API
Replied by: Shaun McDonnell on 29-04-2010 12:16:11 AM
What about the Component APIs of <startMedia /> ?
-Shaun
Subject: RE: startMedia Component API
Replied by: David Staudt on 29-04-2010 04:12:53 AM
The <startMedia> request is a member of the 'Application' features added in 8.3(2) firmware for some newer model phones. According to table 5-1 in the 8.0 IPPS dev guide, the 7940/60 do not support these features.