[cisco-voip] CRA and CTI Port Groups

[Kevin Thorngren]

Hi Paul,

You shouldn't perform any forwarding with the CTI Ports.  The CTI 
application is controlling the call and the port.  If you configure 
forwarding on them then the CTI app will become confused as the 
CallManager process has taken over the call.

Many 3rd party voicemail systems use TAPi to integrate with CallManager 
and will register their own CTI RP and CTI Ports and will accept the 
calls.  Otherwise you will probably need to use a GW with analog or PRI 
interface to the voicemail system.

What voicemail systems are you using?

What protocol(s) does your voicemail system use to integrate with CCM?

Kevin
On Jul 18, 2005, at 8:11 PM, Paul Yago wrote:

> Hello,
>
> Using CRA, I'm trying to create a pilot point (JTAPI Trigger) which
> distributes inbound calls to various 3rd party Voice Mail Servers 
> (VMs).
>
> I created a JTAPI trigger (3100) that will access the members of a CTI
> Port Group which contains 2 CTI ports (3001 and 3002). And with those
> CTI ports, I'm using "Forward All" to access the VMs. The problem I'm
> having is that when one of the VMs is full (CTI Route Point triggers 
> the
> busy) the busy state is not being transferred back to the JTAPI trigger
> in time, and it seems that a blind transfer is being made. So when one
> VM is full, I get a busy signal, rather than it passing the call on to
> the 2nd VM.
>
> How are the CTI ports intended to be used? Should one use them only to
> forward to another extension, or is there something else?
>
> I'm not using scripting capability yes. Is it possible to do this
> without running an application and a script?
>
> Thanks,
> Paul
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>