[cisco-voip] MWI via JTAPI

[Kevin Thorngren]

CallManager should signal call proceeding (CallState=12) back to the 
device dialing MWI when the MessageWaitingManager has found the DN to 
turn MWI on/off.  I am not sure how you would check this via JTAPI.

Kevin

On Jul 12, 2006, at 6:24 PM, Paul Yago wrote:

>
> Hello,
>  
> Via JTAPI, I’m currently using setting the MWI light on phones by 
> using configured Message Waiting Extensions and modified calling 
> numbers. And I’m wondering if there is anyway to get an 
> acknowledgement that the MWI light was successfully activated.
>  
> Scenario:
> Application CTI Port: 2001
> Application CTI Route Point: 2101
> Extension on which to set MWI: 8001
> Message Waiting Number for ON: 9000
>  
> I place a call from 2001 and have it routed via 2101. Within the CTIRP 
> routeEvent I modify the calling party number to 8001 and have the call 
> routed to 9000. This always successfully activates the MWI light when 
> I observe the phone. However, I have no way of acknowledging that the 
> MWI light was affected when I’m not observing the phone. And it’s 
> difficult to create a failure case. Non existent DNs produce the same 
> events as existent DNs.
>  
> The CallCtlConn… events are only shown for 2101 and 2001, but not for 
> 8001 or 9000. I don’t know why. But if I had these I could accept 
> either a CallCtlConnEstablishedEv or a ConnConnectedEv as an ACK.
>  
> Does anyone know how I can get some kind of verification that the 
> light was affected?
>  
> Thanks,
> Paul
>  
>  
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 4189 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20060712/da76a77a/attachment.bin