[cisco-voip] call forward all issue
smetsysocsic at gmail.com
smetsysocsic at gmail.com
Tue Oct 28 11:42:06 EDT 2008
First lemme make sure that i understand correctly, the PIN codes are
required by the TELCO, it's not client matter codes required by
callmanager, correct? If the codes are local CM codes, then you can
circumvent that by simply creating a new route pattern in a callforward PT,
CSS that doesn't require CMC.
I've never actually written an IPCC app like this and didn't give it much
thought when I said it. However, you should be able to simply create a new
app that dials the number that you want to forward to, pauses, then dials
the PIN. Give the app a trigger, then forward the phone to that trigger.
You could get a lot more intricate than that, but that's a start.
-Joe C.
On Oct 28, 2008 10:05am, Darren Ducote <ducotedt at stfran.com> wrote:
> I have IPCCx. Can you assist? How would I go about doing that?
>
>
>
> -----Original Message-----
>
> From: Joe Cisco [mailto:smetsysocsic at gmail.com]
>
> Sent: Tuesday, October 28, 2008 9:58 AM
>
> To: Darren Ducote
>
> Cc: cisco-voip at puck.nether.net
>
> Subject: Re: [cisco-voip] call forward all issue
>
>
>
> No. If you could it would circumvent the purpose of requiring a PIN.
>
> Having said that, if you have IPCC you could trick up an app to do it.
>
>
>
> -Joe C.
>
>
>
> On Tue, Oct 28, 2008 at 9:54 AM, Darren Ducote wrote:
>
> > Currently all of our PRI's require a pin for long distance. Is it
possible
>
> > to enter a pin code on a phone in the forward all option?
>
> >
>
> > ________________________________
>
> > This message contains confidential information and is intended only for
the
>
> > individual named. If you are not the named addressee you should not
>
> > disseminate, distribute or copy this e-mail. Please notify the sender
>
> > immediately by e-mail if you have received this e-mail by mistake and
delete
>
> > this e-mail from your system. E-mail transmission cannot be guaranteed
to be
>
> > secure or error-free as information could be intercepted, corrupted,
lost,
>
> > destroyed, arrive late or incomplete, or contain viruses. The sender
>
> > therefore does not accept liability for any errors or omissions in the
>
> > contents of this message, which arise as a result of e-mail
transmission.
>
> >
>
> > ***St. Francis Medical Center and affiliates encrypt email containing
>
> > Patient Health Information. You will receive a notice with instructions
on
>
> > how to open any encrypted email you receive. To learn more about this
click
>
> > Here
>
> > _______________________________________________
>
> > cisco-voip mailing list
>
> > cisco-voip at puck.nether.net
>
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>
> >
>
> >
>
>
>
> This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message, which arise as a result of e-mail
transmission.
>
>
>
>
>
> ***St. Francis Medical Center and affiliates encrypt email containing
Patient Health Information. You will receive a notice with instructions on
how to open any encrypted email you receive. To learn more, go to this web
site: http://userawareness.zixcorp.com/sites/index.php?b=141&type=1
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081028/092936cc/attachment-0001.html>
More information about the cisco-voip
mailing list