|
Home > Archive > Voice over IP Cisco > March 2006 > Call forwarding applications
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Call forwarding applications
|
|
| Philip Walenta 2006-03-25, 9:46 am |
| A while back I wrote a quick/featureless app to forward non-primary lines on
phones from the phones.
Based on several discussions I've had with various folks, I am now
considering writing one or two improved versions of this app.
Based on some feedback, here are the two I'm considering:
1. "Service button" based - hit the services button on the phone (or URL
button linked directly to the service), select the line (based on what's
available on the phone originating the request), enter the extension/number
to forward to and done. Unforwarding will work the same way. App would
check to see if the line selected is already forwarded/not forwarded.
2. "IPCC express" based - call a CTI route point on IPCC, prompt asks for
number to forward to/or unforward. IPCC server executes request, and gives
feedback for success/no success. App would check to see if the line
selected is already forwarded/not forwarded.
Any further feedback on these ideas would be greatly appreciated. If I go
forward with either of these, I'd expect some results in a month or so.
Philip Walenta
email: pwalenta@wi.rr.com
cell: 262.951.1941
| |
| Ed Leatherman 2006-03-25, 9:46 am |
| Is it possible to check against the dial plan from a script to make sure
they enter a valid forward target, like it does when you press the CFWDAll
softkey?
On 3/24/06, Philip Walenta <pwalenta@wi.rr.com> wrote:
>
> A while back I wrote a quick/featureless app to forward non-primary lines
> on phones from the phones.
>
> Based on several discussions I've had with various folks, I am now
> considering writing one or two improved versions of this app.
>
> Based on some feedback, here are the two I'm considering:
>
> 1. "Service button" based - hit the services button on the phone (or URL
> button linked directly to the service), select the line (based on what's
> available on the phone originating the request), enter the extension/number
> to forward to and done. Unforwarding will work the same way. App would
> check to see if the line selected is already forwarded/not forwarded.
>
> 2. "IPCC express" based - call a CTI route point on IPCC, prompt asks for
> number to forward to/or unforward. IPCC server executes request, and gives
> feedback for success/no success. App would check to see if the line
> selected is already forwarded/not forwarded.
>
> Any further feedback on these ideas would be greatly appreciated. If I go
> forward with either of these, I'd expect some results in a month or so.
>
> Philip Walenta
> email: pwalenta@wi.rr.com
> cell: 262.951.1941
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
| |
| Voll, Scott 2006-03-25, 9:46 am |
| I like the services button option. And I look forward to whatever you
end up doing. Thanks for what you're doing.
Scott
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Philip Walenta
Sent: Friday, March 24, 2006 6:51 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Call forwarding applications
A while back I wrote a quick/featureless app to forward non-primary
lines on phones from the phones.
Based on several discussions I've had with various folks, I am now
considering writing one or two improved versions of this app.
Based on some feedback, here are the two I'm considering:
1. "Service button" based - hit the services button on the phone (or URL
button linked directly to the service), select the line (based on what's
available on the phone originating the request), enter the
extension/number to forward to and done. Unforwarding will work the
same way. App would check to see if the line selected is already
forwarded/not forwarded.
2. "IPCC express" based - call a CTI route point on IPCC, prompt asks
for number to forward to/or unforward. IPCC server executes request,
and gives feedback for success/no success. App would check to see if
the line selected is already forwarded/not forwarded.
Any further feedback on these ideas would be greatly appreciated. If I
go forward with either of these, I'd expect some results in a month or
so.
Philip Walenta
email: pwalenta@wi.rr.com
cell: 262.951.1941
|
|
|
|
|