[cisco-voip] TEHO legals and CLID

[Ahmad, Habib]

You make a good point dennis, Verizon SIP circuits in the northern Virginia are a tied down to only numbers that belong to the end client. We had an issue where we could not do mobility since the caller ID passed on was the callings parties, we had to change the caller ID to the main number so Verizon could pass it through.

Habib Ahmad
System Consultant
703.248.4056 Office
703.875.8005  Fax
Habib.Ahmad at corebts.com<mailto:Habib.ahmad at corebts.com>
www.corebts.com<http://www.corebts.com/>
- Need support/scheduling?
- Customer Service Phone: 703.248.4050
- FallsChurchCustomerSupport at corebts.com<mailto:FallsChurchCustomerSupport at corebts.com>

[cid:image001.png at 01CA4841.39DF4C90]
Doing what you like is freedom, Liking what you do is happiness.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Dennis Heim
Sent: Thursday, October 08, 2009 12:18 AM
To: Voice Noob; 'Tired Banchini'; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] TEHO legals and CLID

For the CLID, it just depends on how your provider provisions the outbound CLID screening table. ATT is the past has left it open while Verizon locks it down to numbers on that circuit or trunk group. I know that some SIP providers also do not filter outbound CLID.

Dennis Heim
Network Voice Engineer
CDW  Advanced Technology Services
11711 N. Meridian Street, Suite 225
Carmel, IN  46032

317.569.4255 Office
317.569.4201 Fax
317.694.6070 Cell
dennis.heim at cdw.com<mailto:dennis.heim at cdw.com>
www.berbee.com<http://www.berbee.com/>

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voice Noob
Sent: Wednesday, October 07, 2009 11:30 PM
To: 'Tired Banchini'; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] TEHO legals and CLID

What country are you in? In the US you can do TEHO all day long.


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tired Banchini
Sent: Wednesday, October 07, 2009 4:39 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] TEHO legals and CLID

Hi everyone.

I was wondering if anyone can advise or point me in the direction of some authoritative documentation on the legal implications of TEHO, if any... in global context, or at least with major continents?

My loose understanding as this all on-net (intra-company) calls are legal; must admit I get conflicting opinions, although majority suggest this is OK. In terms of TEHO, i.e. break out, opinion seems a little more blurred... is there any authoritive references on this anyone can advise of?

Also again my experience limited in this field, in the same context, TEHO and CLID. I would kind of anticipate th
at large carriers would expect to see specific DDI ranges or routes as CLID on access truunks into there cloud and hence will block numbers that don't match the expected CLIDs, I have seen this with some SPs, again I am not sure if this is just a loose best practice or where it becomes mandatory.... can anyone offer any worldly advice please....?

Thanks in advance
TB


CONFIDENTIALITY NOTICE:  This E-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information.  Please do not copy, forward, or print this E-mail message or any attachments unless you are the intended recipient.  If you are not the intended recipient, please immediately notify the sender by telephone at (866) 588-5697 and permanently delete and destroy all copies and printouts of this E-mail message and/or attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091008/c1bbd24b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7163 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091008/c1bbd24b/attachment.png>