[cisco-voip] JTAPI - Route Address from Endpoint

[MJ Bunkowske]

Thanks Wes. You've been a huge help. I didn't see that in the javadocs 
before and I know at least its possible to change the behavior (at least in 
JTAPI).

However, I'm not actually routing the call, the Cisco ICM is handling that. 
I've been looking for parameters to change in the ICM so it would keep the 
original called party the same. The following registry entries to ICM look 
good but haven't worked:

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<ICM customer>\PG<PG 
number>\PG\CurrentVersion\JGWS\jgw1\JGWData\Dynamic\RedirectCalledAddressOption

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<ICM customer>\PG<PG 
number>\PG\CurrentVersion\OPC\CallControl\pim<PIM 
number>\NewCallOffersUpdateDNIS

Do you (or anyone else) know of any others I could try? I'm having trouble 
finding documentation for these entries...

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: Thu, 3 Nov 2005 11:14:01 -0500
>
>MJ,
>
>One correction, In the jtapi javadocs index you can find the version of
>redirect that specifies whether or not to preserve the original called
>party:
>
>redirect
>public javax.telephony.Connection redirect(java.lang.String
>destinationAddress,
>                                            int mode,
>                                            int callingSearchSpace,
>                                            java.lang.String
>preferredOriginalCalledParty)
>                                     throws
>javax.telephony.InvalidStateException,
>
>javax.telephony.InvalidPartyException,
>
>javax.telephony.MethodNotSupportedException,
>
>javax.telephony.PrivilegeViolationException,
>
>javax.telephony.ResourceUnavailableExceptionThis method overloads the
>CallControlConnection.redirect() method. It takes three new parameters --
>redirectMode, callingSearchSpace, preferredOriginalCalledParty. The
>redirectMode is used to select which type of redirect to perform, and the
>callingSearchSpace is used to instruct the implementation to use either the
>calling party's search space or the redirect controller's search space.
>The redirectMode parameter may be:
>CiscoConnection.REDIRECT_DROP_ON_FAILURE
>CiscoConnection.REDIRECT_NORMAL
>Read above for a description of what each of these means.
>The callingSearchSpace parameter may be:
>CiscoConnection.DEFAULT_SEARCH_SPACE
>CiscoConnection.CALLINGADDRESS_SEARCH_SPACE
>CiscoConnection.ADDRESS_SEARCH_SPACE
>Read above for a description of what each of these means.
>NOTE: The callingSearchSpace parameter may be specified when the redirect
>controller is a RouteAddress. It will be ignored for all other address
>types.
>PreferredOriginalCalledParty parameter may be: a DN which will be the
>originalCalledParty field when call is offered to destinationAddress.
>
>/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
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/