lelio at uoguelph
Jul 9, 2009, 11:37 AM
Post #10 of 10
(843 views)
Permalink
|
That's correct, if I were populate calling name ID, it would make it out as I set it to 99% of Canadian telephones because it's what _I_ populated it with. If the call were to terminate in the U.S., it would be a crap shoot, and basically be a lookup from the number I provide.
So in Canada, I guess, calling name and number don't always have to match.
The following lists the carriers in Canada. But these are probably more than just LECs and CLECs, it probably lists long distance carriers as well.
http://www.cnac.ca/data/CIC_List.htm
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt
----- Original Message -----
From: "Carlos Ortiz" <COrtiz [at] sscincorporated>
To: "Lelio Fulgenzi" <lelio [at] uoguelph>
Cc: "Cisco-VoIP PuckNetherNet" <cisco-voip [at] puck>
Sent: Thursday, July 9, 2009 2:26:45 PM GMT -05:00 US/Canada Eastern
Subject: RE: [cisco-voip] Caller ID clarification
Yeah - I meant if you send out “UOG – Test” from your phone would it actually make it all the way through to the destination. >From my understanding it’s not reliable in the US since the call usually passes through multiple carriers and some of the information is not passed along. Therefore we use this Local LEC database? You said that in Canada it’s determined by calling party. The only way for it to make it to the destination would be if the information is passed from carrier to carrier. How many different ones are there in Canada?
From: Lelio Fulgenzi [mailto:lelio [at] uoguelph]
Sent: Thursday, July 09, 2009 2:12 PM
To: Carlos Ortiz
Cc: Cisco-VoIP PuckNetherNet
Subject: Re: [cisco-voip] Caller ID clarification
If we were to turn on outbound caller ID, the internal callerID name configured on the phone would be sent to any Canadian carrier.
Not sure if that's what you were asking.
Apparently, w/ v7 and higher, there is an "ASCII" call display configuration on the DN that is used for PSTN outbound CallingID so it can be different than internal display. Haven't tested that in the least though.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt
----- Original Message -----
From: "Carlos Ortiz" <COrtiz [at] sscincorporated>
To: "Lelio Fulgenzi" <lelio [at] uoguelph>
Cc: "Cisco-VoIP PuckNetherNet" <cisco-voip [at] puck>
Sent: Thursday, July 9, 2009 2:00:39 PM GMT -05:00 US/Canada Eastern
Subject: RE: [cisco-voip] Caller ID clarification
I think the problem in the US is that the information is not passed from carrier to carrier consistently if at all. Therefore if a LEC doesn’t update its database you just get the same old information. Does the NAME and CID Number get propagated from you Call Mgr other to other carriers?
From: Lelio Fulgenzi [mailto:lelio [at] uoguelph]
Sent: Thursday, July 09, 2009 11:23 AM
To: Carlos Ortiz
Cc: Cisco-VoIP PuckNetherNet
Subject: Re: [cisco-voip] Caller ID clarification
In my bit of investigation, it's the called party's LEC that does the database lookup for the CallerID in the U.S. In Canada, it's up to the calling party to fill that information in. Not sure why the difference exists.
Basically, it's whomever updates the white pages last, or something like that. Good luck getting it working properly.
We have a hamburger franchise on campus and for the longest time, calls from our campus to the states were coming up as this hamburger franchise. Not sure how it got fixed, but it eventually sorted itself out. Likely because we updated the white pages.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt
----- Original Message -----
From: "Carlos Ortiz" <COrtiz [at] sscincorporated>
To: "Cisco-VoIP PuckNetherNet" <cisco-voip [at] puck>
Sent: Thursday, July 9, 2009 10:35:21 AM GMT -05:00 US/Canada Eastern
Subject: [cisco-voip] Caller ID clarification
We have a business unit that wants to send out a different caller ID name (ABC Company) from their location. According to ATT who is the PRI provider, they will accept whatever we send to them. I have a couple of questions:
1) Can this be done with CCM 4.1.3 and H.323 gateways? (if so - where do I configure)
2) From previously looking into this I understand that Caller ID at a residence is determined by a database lookup by the Local LEC. If that’s true, how could I get this database updated nationwide so that when we call our clients (all over the US) they get the name ABC company instead of the generic “Shelton, CT”.
Thanks,
Carlos
_______________________________________________ cisco-voip mailing list cisco-voip [at] puck https://puck.nether.net/mailman/listinfo/cisco-voip
CONFIDENTIALITY NOTICE: This e-mail transmission, including any attachments to it, may contain confidential information or protected health information subject to privacy regulations such as the Health Insurance Portability and Accountability Act of 1996 (HIPAA). This transmission is intended only for the use of the recipient(s) named above. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail and destroy the original transmission in its entirety without saving it in any manner.
Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
CONFIDENTIALITY NOTICE: This e-mail transmission, including any attachments to it, may contain confidential information or protected health information subject to privacy regulations such as the Health Insurance Portability and Accountability Act of 1996 (HIPAA). This transmission is intended only for the use of the recipient(s) named above. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail and destroy the original transmission in its entirety without saving it in any manner.
Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
|
