RE: Image & Input Box on Cisco 7961

RE: Wireless Phone Registered with CUCM

2012-04-12T18:19:56Z

The registration timeout is the 'worst case' scenario, where the device simply stops responding from UCM perspective. In some scenarios, like roaming, administrative de-registration, end-user poweroff (perhaps), UCM may get a positive signal or TCP connection loss from the network, which allows it to clean up the registration more quickly (even immediately.)

RE: Wireless Phone Registered with CUCM

2012-04-12T18:12:19Z

Under System/Service Parameters, select Cisco Callmanager (Active) service.

RE: Send Text message to IP Phone

2012-04-11T21:26:07Z

You will need to use IP Phone Service API insofar as you must POST a valid CiscoIPPhoneExecute XML object to the phone in order for it to properly display the message. This is a simple HTTP POST, however and can be accomplished from virtually any programming environment with network capabilities.

RE: Wireless Phone Registered with CUCM

2012-04-10T19:53:07Z

In the best case if the phone actually signals a de-registration, then UCM should mark it as such almost immediately. In the case where the phone does not shut down cleanly, UCM will wait for 3 missed keepalive signals - this keepalive interval defaults to 30 seconds, but is controlled by the 'Station Keepalive Interval' service parameter.

RE: Writing a CUCM Customised Corporate Directory

2012-04-03T17:36:53Z

As CUAE is now End of Life, I would recommend looking into the IP Phone Services XML API for using the phone screen XML browser with a web backend. The SDK has several samples along those lines: http://developer.cisco.com/web/ipps/docs

RE: Trigger for received Media

2012-03-13T21:17:45Z

It sounds like by 'receiving an audio stream' at a low level this would be RTP packets arriving at a listening socket? If this is your requirement, I don't think CUAE can trigger from this. You could create a CUAE provider using .NET code that does this, and then exports an event to the CUAE framework for processing there...

RE: How to lock the IP phone

2012-01-27T18:12:13Z

I had forgotten that the Idle URL had a configurable timer - that would be a potentially simpler approach :)

RE: How to lock the IP phone

2012-01-26T17:51:26Z

AXL would be the right request, sending a new which CSS has been configured in UCM to dial 911/operator only. Triggering this after 1 minute idle can best be accomplished via a CTI API (TAPI or JTAPI) to monitor the phone's call events in real time. When your app detects that all calls have been idle for > 1 minute, execute the AXL change as above

RE: Unable to pass DTMF tones to called IVR while services screen or any ot

2011-09-22T21:51:01Z

With the XML application visible and in focus, keypad input will be directed to the application, not the the phone UI - per my understanding the behaviour your describe is per design...no configuration to modify this behaviour.

RE: JTAPI Load Balancing

2011-01-07T23:28:21Z

Apparently load-balancing across CTI-Managers is not necessary and there is no real facility for this (at least without sacrificing failover, as you suggest.)

RE: JTAPI Load Balancing

2011-01-06T20:36:38Z

[quote]Hi, 1) Each cluster is able to handle 13k monitored devices (CTI resources). Is that correct? [/quote] Scalability depends on hardware, software version and usage pattern and can vary considerably. See the 'scalability' white papers here: [url=http://developer.cisco.com/web/jtapi/docs]http://developer.cisco.com/web/jtapi/docs[/url]. Note that the [quote] 2) What makes a monitored device "monitored"? Is it when an observer for the device? In JTAPI documentation, a Terminal, Provider, Call and Address object all have addObserver method. Which observer makes the device "monitored"? [/quote] UCM must create an internal 'station' object (memory/CPU) whenever a device must be monitored for events. For JTAPI this means adding a terminal or address observer. [quote] 3) How about addCallObserver method? [/quote] This should impact only the local JTAPI client, and will not consume additional UCM CTI resources once the device is already open [quote] 4) Let's assume 1 monitored device consumes 1 CTI resource. Which of the method calls (or all of them) would consume CTI resource? [/quote] Any observer that ends up receiving events from the device requires a station object for the device on UCM. So terminal observer or address observer will consume a CTI resource. Note that once the device is open - say, for terminal observer - adding an address observer does not usually consume a CTI resource, as the device is already 'open'. See the scalability docs for details, as a device with many addresses will at some point consume an additional resource. Beyond this, in later UCM versions efficiencies have improved scalability in certain scenarios, so that things like observing the same device with multiple CTI clients can be 'free', etc. The CTI resource/scalability mechanism is intended to provide guidance around performance impact, it's not an exact science nor is it strictly enforced by UCM. The main authority for calculating overall CTI impact on a cluster wll be the UC Capacity Tool (see the scalability docs for details) - this is what sales teams and TAC will use to design or support customer installations.

RE: retrieve Missed Call/Received Call history list.

2010-12-16T10:41:19Z

Well you are correct in that the phones do not access the CDR repository. They do store missed calls, etc. locally and populate the screens from their internal data - they do not access UCM. There are no APIs or web pages available on the local phone to get at this data - primarily as the XML serices have not been fully secure.

RE: How to lock the IP phone

2010-11-09T22:01:51Z

This type of request comes up every so often, and usually the need for total restriction is always tempered by the need for 911 - as this should be available at all times to anyone. The indicated solution usually is to use the AXL SOAP API with your application to change the available calling search space on the device, so that the phone can only call 911. You could also implement this so that the app used the Extension Mobility API to login a dummy E/M user, who had CSS for 911 only, had a special set of services that only pointed to the unlock app, etc. Beyond the more or less standard admin config options - dial plan changes, E/M, line provisioning, services provisioning: available via AXL - there is no mechanism to take direct control of the physical buttons on the device.

RE: Send one row of text to IP Phone

2010-09-28T18:26:02Z

Unfortunately you can't modify the screen text when the call plane (which has the telephony buttons) is visible. A possibility would be to present an XML application screen with custom softkeys that mimic the telephony buttons. The custom softkeys could be programmed to make an HTTP request to a back-end CTI-based (TAPI/JTAPI) application which the invokes the actual call control command for the phone.

RE: Send one row of text to IP Phone

2010-09-28T15:13:23Z

The call plane - which includes the call-interaction softkeys, From display etc. - is not modifiable via XML applications. XML apps live in a separate 'services' or 'application' plane where they may control the display and softkeys for their purposes, but not directly interact with calls.

RE: Call Manager Simulator

2010-09-20T18:49:50Z

The old CM simulator is long defunct. Now that UCM can be installed in a VMWare virtual machine, this is the best way to start a lightweight lab, though you do need to obtain the UCM installation media. If you're a member of the CDN partner program, please take a look at the discount purchase programs: http://developer.cisco.com/web/partner/discount-purchase-programs

RE: Moving text

2010-08-18T19:37:45Z

The short answer is 'No.' Slightly longer answer: this is possible using the TAPI phoneSetDisplay API. Please read the notes/caveats associated with this feature in the TAPI Developer Guide: http://developer.cisco.com/web/tapi/docs Note also that this feature has been deprecated and is not supported on 69xx/89xx/99xx models and newer.

RE: Send Execute Error

2010-08-18T05:33:21Z

It doesn't look like either of the pcap's provided captured anything useful. There is no relevant HTTP traffic I can find in the phone pcap, and the only thing present in the CUAE pcap is a TCP handshake (but no further messaging) from something to the phone (172.19.52.79.) If we can get the pcap from phone startup through a test run, we can verify the phone's authentication configuration (seen in the config file the phone downloads during bootup via TFTP) and see exactly why authentication is failing from the phone side.

RE: Send Execute Error

2010-08-11T03:15:29Z

Can you provide the phone model numbers and firmware versions, as well as a network packet capture (Wireshark) from the phones' extra PC switch port?

RE: Image & Input Box on Cisco 7961

2010-08-05T01:21:50Z

Only CiscoIPPhoneInput allows for 'field' type data input - there is no version which includes the ability to include an image. XML services objects cannot be combined - only one type is displayed at a time.