[cisco-voip] JTAPI - Route Address from Endpoint

[Wes Sisk]

MJ,

There is a Cisco extension to redirect functionality gives you the option of
either
preserving or resetting the original called ID when performing a redirect.

See the CiscoRouteSession and
DONOT_RESET_ORIGINALCALLED
          This could be parameter value for PreferedOriginalCalled Option,
it specifies not to reset OriginalCalled


/Wes

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of MJ Bunkowske
Sent: Wednesday, October 26, 2005 8:56 AM
To: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] JTAPI - Route Address from Endpoint


Thanks for the response, Wes.

It seems like a "normal" routed call to me, however I don't actually know
the process it goes through to route the call. Do you know where those
parameters are defined? Is there an ini file or something that ICM uses that
I could look at?

I've also been told that certain events (specifically
CallCtlConnAlertingEv/CallCtlConnEstablishedEv) would carry the original
called# and others wouldnt, however in tests each event contains the exact
same calling/called/currentcalling/currentcalled information.

When monitoring the route point the call events contain the appropriate
calling address but its never passed to the endpoint. Its possible to
monitor each route point and store callIds with call info, but that gets
messy in a hurry with varous call scenarios.

Thanks again...

>From: "Wes Sisk" <wsisk at cisco.com>
>To: "MJ Bunkowske" <bunkowm at hotmail.com>, <cisco-voip at puck.nether.net>
>Subject: RE: [cisco-voip] JTAPI - Route Address from Endpoint
>Date: Tue, 25 Oct 2005 12:20:48 -0400
>
>I'm not much of a jtapi programmer, but have done considerable support of
>CM
>call control and JTAPI.
>
>It would depend on the parameters used to redirect the call from the CTI
>Route Point to the destination.  A 'normal' redirect will leave the
>original
>called party number (ocdpn) in place and this can be queried as one of the
>attributes of the call presented to the destination.
>
>/Wes
>
>-----Original Message-----
>From: cisco-voip-bounces at puck.nether.net
>[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of MJ Bunkowske
>Sent: Tuesday, October 25, 2005 8:22 AM
>To: cisco-voip at puck.nether.net
>Subject: [cisco-voip] JTAPI - Route Address from Endpoint
>
>
>I know there isn't a lot of JTAPI discussion going on here, but there has
>been some in the past so...
>
>Using JTAPI 1.2 with Cisco CallManager 3.3 (and 4.1).
>
>Is there a way for an app monitoring only the destination (endpoint) device
>to to get the Address of the device that routed the call (the
>RouteAddress)?
>
>For example:
>A client calls an 800 number connected to a route point. The route point
>routes that call to a destination device (the endpoint). I'd like to
>retreive the 800 number associated with that route point from events on the
>endpoint that's being monitored.
>
>The addresses I can retreive are:
>Call.getCalledAddress() - returns the address of the monitored device (the
>endpoint).
>Call.getCallingAddress() - returns the address of the originator of the
>call
>(the client address).
>Call.getLastRedirectedAddress() - returns null
>No other methods seem relevant (unless I'm missing something).
>
>Any comments/suggestions are welcome. Thanks.
>
>_________________________________________________________________
>Express yourself instantly with MSN Messenger! Download today - it's FREE!
>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip
>

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip