CallXML 2.0 Development Guide

| TOC

This documentation is for CallXML 2, which has been superceded by CallXML 3. The CallXML 2 language is not being updated any longer. CallXML 3, however, has many new features and is actively being enhanced. If you're writing a new CallXML application, you should use CallXML 3. Click here for the CallXML 3.0 documentation.

Introduction to CallerID

We all know how callerID works from an end-user perspective: our phone rings, we check the callerID, see it's the ex-girlfriend, and let the answering machine take a message. We can also grab the callerID and the calledID in CallXML, so we can beef up the answering machineapplication in our previous lesson to programatically disconnect the psychotic ex-girlfriend whenever she calls. And then we get a restraining order.

We can access these two bits of information by utilizing a few built-in session variables of CallXML, most notably, the session.callerid and session.calledid variables. We can use these variables to catch who called our app, and what number they dialed to reach the app, anywhere in our application by using the standard $Varname; syntax, as illustrated below:

$session.callerid;

You don't have to be a Nobel Prize winner to figure this one out, as it is pretty cut and dried. Let's get our hands dirty and start work on the next Lesson, shall we?

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page

Answering machine Hello world

| TOC

CallerID and CalledID