search for: lidb

Displaying 9 results from an estimated 9 matches for "lidb".

Did you mean: lib
2005 Jan 09
5
Little confused about Caller ID
...lso known as ADSI) Here is the US, I cannot speak for other countries. When party A places a call to Party B. Party A's Telco picks up the number, either from a table on the switch or passed from the PRI from Party A. Then on the far side (Party B's Telco) the Telco does a lookup in the LIDB (Line Information Data Base) and associates a name with a number. This information is then passed as Part II CLID. I have simplified the process, leaving out many processes along the way but it should give some insight as to how the Name actually shows up on the other end. Most Telcos do not rece...
2006 Jun 02
3
All non US 48 area codes?
Is there a list somewhere or a way to find the following: 1- All non US 48 area codes which can be dialed as 1+10 2- All strange area codes which are used for premium services such as 900-XXX-XXXX 3- Anything else that should be restricted if one was to restrict all calls to US 48 only I have found many list but it's tough looking at the entire list of area codes and pulling out each of them
2005 Mar 22
2
Is there a way to get inserted into an LEC's CLI DB?
Does anyone know if there's a service out there to -- for a fee -- inject our DID into the LEC's CLI database so a called party gets our associated name? /rg
2005 Sep 14
0
MAX PRI for single server (was:Not enoughlinesavailable for Asterisk implemetation)
...but the TNT will not pass it through the PRI to my * box. > Am I understanding correctly that calling name information also does not > work with SIP? Calling name does work with SIP. There is an issue with calling name delivery form a 5E to a TNT/APX if the 5E is configured to do end office LIDB dips for calling name (like qwest communications does it). The TNT does not understand the way that the 5E sends "information following operation" and subsequent facility IE containing the CNAM. BUT if you are seeing the CNAM on the TNT that may not be the issues, if this problem is prese...
2005 Sep 08
1
MAX PRI for single server (was: Not enoughlinesavailable for Asterisk implemetation)
...artially populated TNT to one * box and not need another sip proxy, you can also have a failover sip proxy configured but not active unless the primary fails to respond. Both the TNT and APX have issues with calling name delivery over PRI when connected to a Lucent 5ESS configured to do end office LIDB dips, so calling party name on inbound calls can be a bear, look to connect to a Nortel DMS if you have the option -- go figure the LUCENT media gateways work better with Nortel class 5's than then they do with lucent class 5's. Have you learned something I have not about how to get all of...
2006 May 01
12
CallerID Name problem
I'm having trouble getting callerid name to show up on my phones (Cisco 7960 and a few softphones) When I look in the CDR database I see the name but not on any phone when being called. I'm running Asterisk SVN-trunk-r7498 built on 2006-04-30 15:11:39 UTC Any help would be great !
2008 Aug 21
1
DSS1 vs SS7
Hi, I am requesting for a E1 connection from my telco. They are asking if I want DSS1 or SS7, and I am stuck here. Could someone tell me the difference between the two? How should I decide which one to use? Thanks in advance for your help. Mark -------------- next part -------------- An HTML attachment was scrubbed... URL:
2008 May 28
7
Cisco Gateway sending call to * without CID Name
Hi All, I have a Cisco 2600 PRI gateway being hosted on an Asterisk server. The PRI on the cisco is pointing to a customer legacy PBX, the SIP VoIP side of the cisco is pointing to an Asterisk server (1.2.X). In Asterisk, the SIP peer is setup with callerid="some name"<5551212> In a SIP call from the cisco to asterisk, there is no CID name info in SIP debug, so Asterisk
2005 Aug 19
4
any ISDN/PRI signaling experts out there?
I have officially engaged in a pissing contest with the local Telco over PRI calling name delivery. The telco publishes their calling name delivery over PRI feature as being bellcore gr-1367-core compliant. The gr-1367-core spec states that the calling name is to be included as a facility IE in the setup message, or sent in a subsequent facility IE message with an indicator in the setup message