Thanks for that guys. I'll give the custom context a go.
I could use an outbound route - but Im a pedantic person and I'd like it
displayed properly in FOP and for CLID matching purposes as well.
Also, I concur re the '9 prefix'. I just dont use it. :)
Greg MacLellan wrote:
Adrian Carter wrote:
Hey guys,
Does anyone know of a nice way to clean up CLID on all calls coming
in a certain trunk? One of our PRI providers drops off the 0, which
means that matching and 'one-click-call-return' are broken because it
appends 'half' the Area Code to the CLID (In Australia, area codes are
prefaced 0NXXXXXXXX).
Is it out of the question to just append 0 to this using a route? Ie,
0+NXXXXXXXX
I'm not sure how phone numbers are dialed there, so maybe this doesn't
really make sense.
On the subject, the "call return" thing is one of the reasons I
advocate not using 9-prefix dialing, which for some reason so many
people still use. There's nothing wrong with having both, of course
(espessially when migrating from another PBX that was limited to
9-prefix). It's nice to be able to just dial a number (or press the
"dial" button when viewing a missed calls list on a phone that
supports it) and be connected.
That said, I'd agree with Julian's suggestion of the custom inbound
context if you can't just use outbound dialing rules.
-Greg MacLellan
--
Adrian Carter
Technical Manager
Leading Edge Internet
Web http://www.lei.net.au http://support.lei.net.au
Direct +61 2 6163 6162 Support 1 300 662 415
E-mail cartera-NSfxlkMYp1MQrrorzV6ljw@xxxxxxxxxxxxxxxx
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
|
