Re: [asterisk-users] Re: Open CallerID Database?
Just out of interest: From former posts I understood that there is a CALLERID service in US (for an extra fee, I assume) that gives both number _and_ name of the caller...? I am aware of the fact that e.g. EuroISDN lines can transmit alphanumeric callerid (and in fact I already use that on an ISDN phone here that connects to an Asterisk - showing a few special names like wakeup call). Not for names yet, as I was too lazy to implement that. Does that also work over analogue lines? ISDN is america does the same thing, but in Canada( which could be like europe) the callerid is transfered on the SS7 ISUP message, so the owner of the number can provide their own callerid. In America though, this isn't the case. You can not transfer the callerid over the ISUP message, it must be looked up using TCAP(verisign) or IP servce(targus). It's not really getting the CallerID info to the local switch, but getting it updates in this database in the sky that we are forced to use. :) On 2/20/07, Anselm Martin Hoffmeister [EMAIL PROTECTED] wrote: Am Dienstag, den 20.02.2007, 16:33 -0700 schrieb Natambu Obleton: I would guess that registration would be by the telco for the blocks just like with reverse dns today, so then each telco would have a local server to manage their 'reverse' cnam lookup and the people in charge would be NANPA, just like how ARIN is regulated today. Although who owns the root namservers.. I wonder if ARIN and RIPE share ownership of them? Although now that i Think about it dns wouldn't work because want to deligate .. XXX-XXX-XYYY and XXX-XXX-XXYY and then there is single numbers. For that right now I do weird PTR CNAME to A record thing for single reverse dns. This would be little larger... ohh shit.. LNP. So now Qwest would need to deligate a single CNAM to me and crap..naw this will never work. I do not get your point here. Take ENUM. A made-up phone number like +49 (228) 91234567 would be found as 7.6.5.4.3.2.1.9.8.2.2.9.4.enum-something This means, you delegate the 2.1.9.8.2.2.9.4.enum-something to the telco that owns the 912 block in Bonn, Germany. Number portability screws this, as even single numbers out of a contiguous range of MSNs on a ISDN line can be moved over to another provider, with the others staying with the old provider. They would have to play well together, and that will fubar for sure (they even sometimes block the DSL frequencies on lines when a customer moves to another company, with unblocking taking a 14-day security period, because they can - there is no technical block, but the DSLAM manipulation database software will mark your DSL line as blocked, making moving to another provider a pain with up to 6 weeks without internet). In Germany we have an agency that manages all phone book data, and (nearly?) all the 411 type services (called 118xx here) buy data there. How they manage their data internally is none of my business (although I would guess it's something like MSSQL with an Access frontend, thinking about the Deutsche Telekom ;-). They will no way accept DNS-type queries for free. Some months ago, there was a heise.de (German IT newsticker) article about them charging enourmous sums, paying the real data storage and administration costs back by about factor 5 or so. Well-paying businesses rarely give away their business turnpoint. Any non-official system will suffer even worse inaccuracy than the providers' own and managed system (as someone else already wrote). Their data is quite bad enough. This relates, of course, to the fact that they may only reverse-lookup numbers to find names if the customer explicitely allowed them to do it, on the line rental agreement. There are usually several checkboxes, allowing you to get listed in phonebook, get listed in digital listings, and get listed for reverse lookup. For those who allow it there is a free web-frontend to reverse-lookup numbers, which is a pain to script-access, but it is possible. It suffers from problems with DIDs, as for example a shop might have the number 94144-0, and assigned the numbers up to 94144-29. If you try to lookup 9414488 (which might be a private person's analogue line, and this is absolutely valid in the German numbering system) it will return the wrong entry because the logic in their webinterface always assumes that 94144-0 means all numbers starting 94144- belong to that line. _That_ really sucks - you think business and then it's a friend calling for private talk. Just out of interest: From former posts I understood that there is a CALLERID service in US (for an extra fee, I assume) that gives both number _and_ name of the caller...? I am aware of the fact that e.g. EuroISDN lines can transmit alphanumeric callerid (and in fact I already use that on an ISDN phone here that connects to an Asterisk - showing a few special names like wakeup call). Not for names yet, as I was too lazy to implement that. Does that also work over analogue lines? BR Anselm
[asterisk-users] Re: Open CallerID Database?
BT == Brad Templeton [EMAIL PROTECTED] writes: BT Hey, we could even build a system where DNS can be used to take BT any phone number and look up data about it, not just a name, but BT even a URI to redirect calls to for it, a source of presence info BT and more. BT What a great idea! I may be missing sarcasm here, but the URI thing is known as ENUM. /Benny ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Re: Open CallerID Database?
ML == Mike Lynchfield [EMAIL PROTECTED] writes: ML With all other things said.. you might want a professional service ML for this like targusinfo.com ML Maintaining and running an operation like a cname web lookup thing ML is REALLY high overhead in terms of web traffic etc ML What happens when you get 30 ITSP/clients pulling 1000 calls each ML or 10 calls each per day.. You use DNS. ML that can easily go up to 1 mill requests per day , Not a problem with DNS. The technical problems are relatively easy to overcome. The other problems less so, probably. /Benny ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Re: Open CallerID Database?
RL == Richard Lyman [EMAIL PROTECTED] writes: RL TP'n to follow flow just like DNS, the 'root servers' would still RL see the high request hits, prior to passing off to local caching RL app. The DNS root servers are almost only loaded by irrelevant traffic. The root information is easily cacheable, so it is rare to have to actually ask the root servers. An ENUM-style solution would most likely not see much garbage traffic, and the relevant traffic is easily cacheable. I doubt that we will ever see such a solution though; there is too much invested in the old way of doing things. /Benny ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Re: Open CallerID Database?
Well caching is the way to go., bu then again most of the current solutions have this problem. John smit has a DID.. 514 555 1234 and closes account.. did sleeps for 3 months and new client Jane doe takes it.. Now how long should caching be ? this is a big problem ATM because some cache for 1 year others 1 day , they don't want to tell how long nor provider an API update method. On 20 Feb 2007 20:43:37 +0100, Benny Amorsen [EMAIL PROTECTED] wrote: RL == Richard Lyman [EMAIL PROTECTED] writes: RL TP'n to follow flow just like DNS, the 'root servers' would still RL see the high request hits, prior to passing off to local caching RL app. The DNS root servers are almost only loaded by irrelevant traffic. The root information is easily cacheable, so it is rare to have to actually ask the root servers. An ENUM-style solution would most likely not see much garbage traffic, and the relevant traffic is easily cacheable. I doubt that we will ever see such a solution though; there is too much invested in the old way of doing things. /Benny ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Mike Sales Manager http://www.voicemeup.com Making it happen 1.877.807.VOIP (8647) 1.514.312.7030 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Re: Open CallerID Database?
ML == Mike Lynchfield [EMAIL PROTECTED] writes: ML Well caching is the way to go., bu then again most of the current ML solutions have this problem. ML John smit has a DID.. 514 555 1234 and closes account.. did sleeps ML for 3 months and new client Jane doe takes it.. ML Now how long should caching be ? this is a big problem ATM because ML some cache for 1 year others 1 day , they don't want to tell how ML long nor provider an API update method. The actual records should have TTL's of a few hours, perhaps a day. The rest of the hierarchy can probably get away with longer TTL's, especially close to the root. It's the same thing with the root in regular DNS: You can cache the set of records in the root zone for a long long time, since noone is going to suddenly move all the .com nameservers. /Benny ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Re: Open CallerID Database?
Am Dienstag, den 20.02.2007, 14:54 -0500 schrieb Mike Lynchfield: Well caching is the way to go., bu then again most of the current solutions have this problem. John smit has a DID.. 514 555 1234 and closes account.. did sleeps for 3 months and new client Jane doe takes it.. Now how long should caching be ? this is a big problem ATM because some cache for 1 year others 1 day , they don't want to tell how long nor provider an API update method. Coming back to the DNS example, there are certain timeouts. I have to admit I cannot tell how exactly the timeout values work together, but you _can_ set an absolute timeout after which any cached data (counted from the moment of retrieval) is marked obsolete and a subsequent query occurs. If you set something in the 2-week-range (which may or may not be what many people use in DNS) you can be pretty sure that freshly assigned numbers do not have dangling cache records, assuming the 3 months gap before assigning the same number again. Assuming one could add an additional TXT record to enum, say name.0.6.0.7.x.x.x.enum.info. TXT Hoffmeister, Anselm Martin this would pretty much do the trick. I have no idea wether any standard describes name resolution via enum. The other way around would be more tricky btw., with all those John Smith around ;) BR Anselm ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Re: Open CallerID Database?
RL == Richard Lyman [EMAIL PROTECTED] writes: RL everytime you make a dns request, i agreed that it does not hit RL the root servers, but every time you request a NON-cached one you RL DO. Nope. If you request foo.com and you have up to two days earlier visited bar.com, you won't hit the root servers. Only the .com servers. RL so maybe your call center calls the same people every other day. RL ours do not, and i'm just guessing here, but i have to think that RL others here don't call the same people over and over and over RL millions of times within minutes/hours/days. yeah, you are right, RL i have no clue what i am talking about. People have a tendency to call other people in the same area codes more often than people in other area codes. That ought to help load on the root servers. Anyway, a single server can easily handle 1000 queries per second. If you add even 0.1 cent to the call setup fee to pay for the lookup and you keep the servers at 100 qps average, you are looking at $8640 a day per server. Or look at it the other way around, if you allocate $1000 a month to run a server, and that server performs at 100 qps average, each call costs you .0004 cent extra. /Benny ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Re: Open CallerID Database?
Benny Amorsen wrote: RL == Richard Lyman [EMAIL PROTECTED] writes: RL everytime you make a dns request, i agreed that it does not hit RL the root servers, but every time you request a NON-cached one you RL DO. Nope. If you request foo.com and you have up to two days earlier visited bar.com, you won't hit the root servers. Only the .com servers. which would make it 'NON-cached' RL so maybe your call center calls the same people every other day. RL ours do not, and i'm just guessing here, but i have to think that RL others here don't call the same people over and over and over RL millions of times within minutes/hours/days. yeah, you are right, RL i have no clue what i am talking about. People have a tendency to call other people in the same area codes more often than people in other area codes. That ought to help load on the root servers. that is if your caller base are residential. call centers do not follow this. Anyway, a single server can easily handle 1000 queries per second. If you add even 0.1 cent to the call setup fee to pay for the lookup and you keep the servers at 100 qps average, you are looking at $8640 a day per server. Or look at it the other way around, if you allocate $1000 a month to run a server, and that server performs at 100 qps average, each call costs you .0004 cent extra. which if you want redundancy (like was mentioned already)... using the 'root servers' as a *model* someone would have to have this expense/headache to maintain /Benny i'm not sure why i seem to be unable to get my point across (even with multiple attempts), so i will just not try. good luck ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Re: Open CallerID Database?
So how does this start? I mean it wouldn't be hard to modify dns server to use 3/3/4 format ip address... or it would need to be 3/3/3/4 for international right and someone wrote a module for asterisk look up that way and then I took my SS7 connection and setup a GTT gateway to a server so that real telco's could query it over SS7 and use my other CNAM provider as backup so that people could make me their main connection, but alas... most cnam providers don't allow you to resale lookups. Time to move on, but it would be kewl to start a revolution. :) On 2/20/07, Anselm Martin Hoffmeister [EMAIL PROTECTED] wrote: Am Dienstag, den 20.02.2007, 14:54 -0500 schrieb Mike Lynchfield: Well caching is the way to go., bu then again most of the current solutions have this problem. John smit has a DID.. 514 555 1234 and closes account.. did sleeps for 3 months and new client Jane doe takes it.. Now how long should caching be ? this is a big problem ATM because some cache for 1 year others 1 day , they don't want to tell how long nor provider an API update method. Coming back to the DNS example, there are certain timeouts. I have to admit I cannot tell how exactly the timeout values work together, but you _can_ set an absolute timeout after which any cached data (counted from the moment of retrieval) is marked obsolete and a subsequent query occurs. If you set something in the 2-week-range (which may or may not be what many people use in DNS) you can be pretty sure that freshly assigned numbers do not have dangling cache records, assuming the 3 months gap before assigning the same number again. Assuming one could add an additional TXT record to enum, say name.0.6.0.7.x.x.x.enum.info. TXT Hoffmeister, Anselm Martin this would pretty much do the trick. I have no idea wether any standard describes name resolution via enum. The other way around would be more tricky btw., with all those John Smith around ;) BR Anselm ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Re: Open CallerID Database?
Quoting Natambu Obleton [EMAIL PROTECTED]: So how does this start? I mean it wouldn't be hard to modify dns server to use 3/3/4 format ip address... or it would need to be 3/3/3/4 for international right and someone wrote a module for asterisk look up that way and then I took my SS7 connection and setup a GTT gateway to a server so that real telco's could query it over SS7 and use my other CNAM provider as backup so that people could make me their main connection, but alas... I think you have the format of the address space reversed conceptually but the idea would work - the countrycode, area code etc are like the .com in dns and then exchange like the 2ld, and number like the hostname. the only modification would be to set different root servers for this sort of parallel system, and have someone actually in charge to delegate the subdomains etc. registering a domain name has cost for the admin part of it, but is someone really going to pay to register a phone number they already pay for ? (the administration has to be paid for somehow) I am not trying to criticize, but just pointing out the realities of making it work. most cnam providers don't allow you to resale lookups. Time to move on, but it would be kewl to start a revolution. :) On 2/20/07, Anselm Martin Hoffmeister [EMAIL PROTECTED] wrote: Am Dienstag, den 20.02.2007, 14:54 -0500 schrieb Mike Lynchfield: Well caching is the way to go., bu then again most of the current solutions have this problem. John smit has a DID.. 514 555 1234 and closes account.. did sleeps for 3 months and new client Jane doe takes it.. Now how long should caching be ? this is a big problem ATM because some cache for 1 year others 1 day , they don't want to tell how long nor provider an API update method. Coming back to the DNS example, there are certain timeouts. I have to admit I cannot tell how exactly the timeout values work together, but you _can_ set an absolute timeout after which any cached data (counted from the moment of retrieval) is marked obsolete and a subsequent query occurs. If you set something in the 2-week-range (which may or may not be what many people use in DNS) you can be pretty sure that freshly assigned numbers do not have dangling cache records, assuming the 3 months gap before assigning the same number again. Assuming one could add an additional TXT record to enum, say name.0.6.0.7.x.x.x.enum.info. TXT Hoffmeister, Anselm Martin this would pretty much do the trick. I have no idea wether any standard describes name resolution via enum. The other way around would be more tricky btw., with all those John Smith around ;) BR Anselm ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users Jon Pounder _/_/_/ _/_/ _/ _/_/_/ _/_/ _/_/_/_/ _/_/_/ _/ _/ _/_/_/ _/ _/_/ _/_/ _/_/ _/ _/_/ _/_/ _/ _/_/_/ _/_/ _/_/_/_/ _/_/_/ _/_/ _/_/_/_/ Inline Internet Systems Inc. Thorold, Ontario, Canada Tools to Power Your e-Business Solutions www.inline.net www.ihtml.com www.ihtmlmerchant.com www.opayc.com This message was sent using IMP, the Internet Messaging Program. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Re: Open CallerID Database?
I would guess that registration would be by the telco for the blocks just like with reverse dns today, so then each telco would have a local server to manage their 'reverse' cnam lookup and the people in charge would be NANPA, just like how ARIN is regulated today. Although who owns the root namservers.. I wonder if ARIN and RIPE share ownership of them? Although now that i Think about it dns wouldn't work because want to deligate .. XXX-XXX-XYYY and XXX-XXX-XXYY and then there is single numbers. For that right now I do weird PTR CNAME to A record thing for single reverse dns. This would be little larger... ohh shit.. LNP. So now Qwest would need to deligate a single CNAM to me and crap..naw this will never work. On 2/20/07, Jon Pounder [EMAIL PROTECTED] wrote: Quoting Natambu Obleton [EMAIL PROTECTED]: So how does this start? I mean it wouldn't be hard to modify dns server to use 3/3/4 format ip address... or it would need to be 3/3/3/4 for international right and someone wrote a module for asterisk look up that way and then I took my SS7 connection and setup a GTT gateway to a server so that real telco's could query it over SS7 and use my other CNAM provider as backup so that people could make me their main connection, but alas... I think you have the format of the address space reversed conceptually but the idea would work - the countrycode, area code etc are like the .com in dns and then exchange like the 2ld, and number like the hostname. the only modification would be to set different root servers for this sort of parallel system, and have someone actually in charge to delegate the subdomains etc. registering a domain name has cost for the admin part of it, but is someone really going to pay to register a phone number they already pay for ? (the administration has to be paid for somehow) I am not trying to criticize, but just pointing out the realities of making it work. most cnam providers don't allow you to resale lookups. Time to move on, but it would be kewl to start a revolution. :) On 2/20/07, Anselm Martin Hoffmeister [EMAIL PROTECTED] wrote: Am Dienstag, den 20.02.2007, 14:54 -0500 schrieb Mike Lynchfield: Well caching is the way to go., bu then again most of the current solutions have this problem. John smit has a DID.. 514 555 1234 and closes account.. did sleeps for 3 months and new client Jane doe takes it.. Now how long should caching be ? this is a big problem ATM because some cache for 1 year others 1 day , they don't want to tell how long nor provider an API update method. Coming back to the DNS example, there are certain timeouts. I have to admit I cannot tell how exactly the timeout values work together, but you _can_ set an absolute timeout after which any cached data (counted from the moment of retrieval) is marked obsolete and a subsequent query occurs. If you set something in the 2-week-range (which may or may not be what many people use in DNS) you can be pretty sure that freshly assigned numbers do not have dangling cache records, assuming the 3 months gap before assigning the same number again. Assuming one could add an additional TXT record to enum, say name.0.6.0.7.x.x.x.enum.info. TXT Hoffmeister, Anselm Martin this would pretty much do the trick. I have no idea wether any standard describes name resolution via enum. The other way around would be more tricky btw., with all those John Smith around ;) BR Anselm ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users Jon Pounder _/_/_/ _/_/ _/ _/_/_/ _/_/ _/_/_/_/ _/_/_/ _/ _/ _/_/_/ _/ _/_/ _/_/ _/_/ _/ _/_/ _/_/ _/ _/_/_/ _/_/ _/_/_/_/ _/_/_/ _/_/ _/_/_/_/ Inline Internet Systems Inc. Thorold, Ontario, Canada Tools to Power Your e-Business Solutions www.inline.net www.ihtml.com www.ihtmlmerchant.com www.opayc.com This message was sent using IMP, the Internet Messaging Program. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Re: Open CallerID Database?
Am Dienstag, den 20.02.2007, 16:33 -0700 schrieb Natambu Obleton: I would guess that registration would be by the telco for the blocks just like with reverse dns today, so then each telco would have a local server to manage their 'reverse' cnam lookup and the people in charge would be NANPA, just like how ARIN is regulated today. Although who owns the root namservers.. I wonder if ARIN and RIPE share ownership of them? Although now that i Think about it dns wouldn't work because want to deligate .. XXX-XXX-XYYY and XXX-XXX-XXYY and then there is single numbers. For that right now I do weird PTR CNAME to A record thing for single reverse dns. This would be little larger... ohh shit.. LNP. So now Qwest would need to deligate a single CNAM to me and crap..naw this will never work. I do not get your point here. Take ENUM. A made-up phone number like +49 (228) 91234567 would be found as 7.6.5.4.3.2.1.9.8.2.2.9.4.enum-something This means, you delegate the 2.1.9.8.2.2.9.4.enum-something to the telco that owns the 912 block in Bonn, Germany. Number portability screws this, as even single numbers out of a contiguous range of MSNs on a ISDN line can be moved over to another provider, with the others staying with the old provider. They would have to play well together, and that will fubar for sure (they even sometimes block the DSL frequencies on lines when a customer moves to another company, with unblocking taking a 14-day security period, because they can - there is no technical block, but the DSLAM manipulation database software will mark your DSL line as blocked, making moving to another provider a pain with up to 6 weeks without internet). In Germany we have an agency that manages all phone book data, and (nearly?) all the 411 type services (called 118xx here) buy data there. How they manage their data internally is none of my business (although I would guess it's something like MSSQL with an Access frontend, thinking about the Deutsche Telekom ;-). They will no way accept DNS-type queries for free. Some months ago, there was a heise.de (German IT newsticker) article about them charging enourmous sums, paying the real data storage and administration costs back by about factor 5 or so. Well-paying businesses rarely give away their business turnpoint. Any non-official system will suffer even worse inaccuracy than the providers' own and managed system (as someone else already wrote). Their data is quite bad enough. This relates, of course, to the fact that they may only reverse-lookup numbers to find names if the customer explicitely allowed them to do it, on the line rental agreement. There are usually several checkboxes, allowing you to get listed in phonebook, get listed in digital listings, and get listed for reverse lookup. For those who allow it there is a free web-frontend to reverse-lookup numbers, which is a pain to script-access, but it is possible. It suffers from problems with DIDs, as for example a shop might have the number 94144-0, and assigned the numbers up to 94144-29. If you try to lookup 9414488 (which might be a private person's analogue line, and this is absolutely valid in the German numbering system) it will return the wrong entry because the logic in their webinterface always assumes that 94144-0 means all numbers starting 94144- belong to that line. _That_ really sucks - you think business and then it's a friend calling for private talk. Just out of interest: From former posts I understood that there is a CALLERID service in US (for an extra fee, I assume) that gives both number _and_ name of the caller...? I am aware of the fact that e.g. EuroISDN lines can transmit alphanumeric callerid (and in fact I already use that on an ISDN phone here that connects to an Asterisk - showing a few special names like wakeup call). Not for names yet, as I was too lazy to implement that. Does that also work over analogue lines? BR Anselm ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
