Skip to main content

Original Caller ID

Posted by moshe on Mon, 12/22/2008

is it possible the have the original caller's caller id when using feature code/ring group and using a single external number or multi external phone numbers or it doesn't matter


Submitted by eeman on Tue, 12/23/2008 Permalink

Passing caller-id off your network is entirely dependent on your dial-tone provider. The FCC has begun cracking down on caller-id spoofing and some news stations have reported a recent surge in faked 'school closings' where the caller-id was used to verify the validity of the call. Your provider may restrict your calls to a single caller-id OR they may allow only numbers assigned to you as DID. Have you tested the 'preserve original callerID' option of a forwarded call in the user portal?

Submitted by moshe on Tue, 12/23/2008 Permalink

im using thirdlane MTE

while forwarding the calls using the webportal and select send original caller's caller id works fine, but when i'm using feature to ring to my cell and home phone it does not pass along the original caller's caller id is there a way to set it up it should

thanks

Submitted by eeman on Tue, 12/23/2008 Permalink

there is no way to do this without writing code, because your huntlist creates a new leg of the call using chan_local in your dialplan which subsequently executes your tl-dialout-base script where the callerid is getting defined. The code that overrides the callerid is based on the caller (handsets) database preferences in astdb. Since your huntlist is not a true source extension there is no database key to check.

If you know how to write dialplan you could write a new, but simpler, outbound script that doesn't set any callerid; and create a unique outbound route that uses that script (example _7NXXNXXXXXXX where the 7 gets stripped and reformatted to what your ITSP expects). Then you would specify this unique dial in your huntlist to access that outbound route.