[cisco-voip] quick question on calls to unprogrammed numbers...
Voll, Scott
Scott.Voll at wesd.org
Mon Jan 8 10:30:21 EST 2007
I'm guessing right now it's coming from the Telco.
You could setup a caught all 7xxx to send it to the main number (7000)
or send it to Unity and have some kind of greeting from there.
Since 7xxx doesn't match as well as a DN 7321 if they dial 7321 they get
the person they call but if 7456 is not connected to a phone it will go
to the 7xxx pattern and work as needed.
Scott
________________________________
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Reimers
Sent: Monday, January 08, 2007 7:23 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] quick question on calls to unprogrammed numbers...
One of my users asked a question that I think no one has noticed...
He wondered why it is that when you call a # on our system that is not
allocated, you get:
"Your call cannot be completed as dialed"
instead of
"You have reached a number that is not in service. Please check the
number you dialed and try again"
Or something like that..
It did make me think -- where is that message coming from that defaults
when you misdial...
we might want to specifically program that message to say something a
little more informative, like
'you have reached a number that is not available on the phone system.
Please hang up and dial 7000 for assistance in locating the person you
are trying to reach"
thanks, Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070108/eabe8e0c/attachment.html
More information about the cisco-voip
mailing list