IP Service shows "Requesting" then times out

Version 1
    This document was generated from CDN thread

    Created by: Dane Warner on 12-06-2009 05:24:21 PM
    I don't normally work with IP Phone services, but a customer has asked for something specific. I'm trying to get a sample SDK service, Clock, to work on my lab phones. When I select Clock, I get "Requesting" at the bottom for about a minute and a half, then "Host not Found".
    This is CallManager 7 (7.0.0.39771-4), 7960G phones (8.09 firmware). The SDK is loaded on my laptop, web server running, IP connectivity seems fine, I've doublechecked the URL in the services page, set up according to documentation (http://xxx.xxx.xxx.xxx/CiscoIPServices/clock/clock.asp.
    Can anyone tell me what I'm missing? The application for the customer is something different, but I need to at least get a sample app working first.
    Thanks

    Subject: RE: IP Service shows "Requesting" then times out
    Replied by: David Staudt on 12-06-2009 05:38:41 PM
    Sounds like something in the network config.  Some things to check:
     
    - Firewall is disabled (or configured) to allow inbound connection to the webserver
    - You can browse to the service's URL from a web browser (use the exact same URL as provisioned in UCM).  You should see the XML in your browser window.
    - Phone may not have correct DNS settings - either correct DNS config on the phone or use an IP address in the services URL instead of a host name
     
    A network packet capture (i.e. Wireshark on a PC connected to the phone's extra switch port) may give you some clues about the request the phone is making and why the network is unable to satisfy the request.  Please feel free to attach here if you can't spot anything.

    Subject: RE: IP Service shows "Requesting" then times out
    Replied by: Dane Warner on 12-06-2009 06:26:31 PM
    David,
    Thanks. Firewall on the laptop was the culprit. If I can pick your brain some more, the application that the customer wants is to be able to listen to a police radio dispatch on their IP phones. I've been given documentation on setting up a multicast stream of an analog audio output connected to a port on an E&M card on the voice gateway.
    Here's the voice port and dial peer config:
     
    voice-port 0/1/0
     voice-class permanent 1
     operation 4-wire
     signal immediate
     timeouts call-disconnect 3
     connection trunk 111
     music-threshold -30
     
    dial-peer voice 1 voip
     destination-pattern 111
     session protocol multicast
     session target ipv4:237.111.0.0:22222
     ip qos dscp cs5 media
     vad aggressive
     
    Here's the .asp file that someone else sent me:
     
    <%@ Language=JavaScript %>
    <%
        var serverName = Request.ServerVariables("SERVER_NAME");
        var ipaddr = String(Request.QueryString("ipaddr").Item);
        var port = String(Request.QueryString("port").Item);
        Response.ContentType = "text/xml";
    %>
    <CiscoIPPhoneMenu>
    <Title>Monitor Dispatch</Title>

    <SoftKeyItem>
    <Name>Play</Name>
    <URL>RTPMRx://237.111.0.0:22222</URL>
    2
    </SoftKeyItem>
    </CiscoIPPhoneMenu>
    The application starts, I get a Play button which mutes the mic and turns on the phone's speaker, but no audio coming out (I've got a telco buttset connected to the E&M port.
    I'm confused about the variables at the top of the .asp file. What server am I supposed to be referencing? The web server? CallManager?
    Sorry to throw so much stuff out there but I need to wrap up the test as soon as possible.
     
    Thanks again....

    Subject: RE: IP Service shows "Requesting" then times out
    Replied by: David Staudt on 16-06-2009 03:04:15 PM
    It looks like the XML for the phone is ok - backed by the observation that the phone seems to do the right thing: mutes and starts to receive media.  I'm not sure what the variables at the top of the script are for - they look vestigial.
     
    Probably the problem is in the IOS-side configuration - unfortunately I don't have much experience there.  If you obtain a Wireshark packet capture (via a PC connected to the phone's extra switch port) you should be able to confirm that multicast RTP packets are making it to the phone (or not.)