Telco Providers with CID Name 2

[mobiledynamics]

Currently researching different providers and would like some advice on providers. On my short list, MCI, Qwest & Paetec only do CID # and not CID Name is sent over NI2.

It's helpful to have CID Name IMO. In one of my short stints at another place, we had hosted PBX and the inbound name was really helpful.

Anyone know if ATT or XO offers CID with Name ?

 

[donb01]

I have ATT using ISDN PRI for local service and I only receive the digits and not the name. I don't know about other services (for business - it works for residential).

 

[jerryreeve]

ATT does offer CID with name both on PRI and on copper, of course it costs more (the basic CID is part of the PRI package but name is extra)

----------------------------
'Rule 29', "The enemy of my enemy is my enemy's enemy. No more. No less."
----------------------------
JerryReeve
Communication Systems Int'l
com-sys.com

 

[mobiledynamics]

In my research today, I'm getting mixed answers. From our sales engineers - wholesale Airespring- , they advised also that XO does not send it in addition to the ones listed above.

Interesting enough, Qwest direct says they do it in their *14 region in~state*, but anything outside of their *14 state region*, they don't.

I don't understand why Major Carriers like aformentioned DON'T send it as part of their service. From a business class circuit, one would assume business class services that is providing a more comprehensive value --- thus the reasoning for business rates--- for such service.

Against the rift of softswitchs-softpbxs, that DO dip into the CNAM and send it out across the board - inbound and outbound. When I mention softswitchs-softpbxs, I'm referring to some of the hosted voip products I've seen across the past couple of years.

 

[ISDNman]

CID with name was not part of the Original ISDN standards, so many PBXes don't support it in any case.

It was added later and does exist in some cases however.

On a related topic is will the carrier bother to do the lookup. A number of carriers are too cheap to do the lookup form alternative data bases so it does not show up for cell calls.

I think there is a very good class action suit on this failure to provide the paid-for service, but have not convinced any of ly lawyer friends to tak ethis on.

If you ask a better question you will get a better reply. Be specific so we can help!

 

[mobiledynamics]

I agree on the cheapness. I'm just going over 3-5 business hosted voip softswitches/pbx's I've see and all have always done the cnam lookup.

It really is a shame that the bigger, larger tier providers are not including it as part of their core CID functionality. Everyone appreciates a value service these days IMO.

 

[lopes1211]

An additional hurdle you will need to overcome is if the PBX will support it. Some displays are not large enough for both and/or will require you to pick if you want the name OR the number to display even if the LEC is sending you both. Add in some ACD features, coverage, call forwarding, etc, etc which all pbx system treat differently and phone display will show different info like "FORWARDED CALL FROM 111-222-3333". You can see how you can end up with truncated or unusual results. I don't think there is enough of benefit on the large business side for the LEC to do data dips even if 25% of the PBX's did support this.


-CL

 

[SYQUEST]

Here is a piece of information concerning CID on PRI from the Consultant/Vendor Group @ Pacific Bell/AT&T that I received back in February 2008:


Effective immediately, permanent outgoing Caller ID blocking will no longer be an available option. This change brings AT&T West in compliance with an FCC mandate on Caller ID. The FCC requires that if blocking is offered, the ability to unblock on a per call basis must also be present. This is not technologically possible with PRI. It may no longer be ordered or provisioned on new PRIs. This change standardizes our permanent blocking position & brings all 22 states into compliance with the FCC mandate on Caller ID.

NOTE: We will not proactively remove this capability from existing customers who might already have this capability. However, we will not install any new permanent blocking. Outgoing Caller ID blocking is a function of the CPE.

What Caller ID information is sent and received?

OUTGOING

NUMBER

· The Caller ID Number provided on calls originating from the Customer's equipment (PBX) is the Trunk Group Billing DN of the PRI unless the customer sends valid PBX Station ID.

· Valid PBX Station ID is defined as the telephone numbers to which the customer has subscribed to and are provided by Legacy SBC on that PRI group. This can be thought of as the DID numbers which are provisioned on the PRI(s).

· If valid PBX Station ID is sent to the Legacy SBC Switch (central office), that number will be passed and displayed on the recipient's Caller ID equipment.

· The Trunk Group Billing DN is the TN associated with the Direct Outward Dial USOC on the Customer Service Record.

NAME

· The Name provided on outgoing calls is the Main Listed Name on the PRI Account.

· No other name can be sent.

· Multiple names cannot be sent.

BLOCKING OUTGOING NAME AND/OR NUMBER

· Blocking of Outgoing Caller ID is not available via PRI translations.

· Outgoing Caller ID blocking is a function of PBX/CPE.



INCOMING



· Caller ID Number on Incoming Calls works the same as it does with POTS service. Depending on the Region, this may be a standard or optional, billable feature.

· Caller ID with Name on Incoming Calls is an optional, billable feature

· NOTE: Only available with NI-2 service in DMS and EWSD switches.

· 5/8/07 Update: 5ESS switches may be provisioned as either Custom or NI-2.

Can different names/Directory Listings be sent out with the telephone number?

· YES. SE offers an optional feature called “Secondary Calling Name Delivery”.

· NO. E, MW, SW, W - Only the main listed name associated with the PRI being used to complete the outgoing call will be the name displayed. Additional listings are not displayed. No other user-controlled names can be sent.

Can outgoing Caller ID be blocked on all calls made over an ISDN PRI?

· NO. PRI translations may not be set up to block outgoing Caller ID. Permanent Caller ID Blocking is not available.

Can just the customer’s Name be blocked on outgoing Caller ID?

· NO. We have no methods or procedures developed that enables that.

Why is permanent Caller ID blocking not available on ISDN PRI?

· U.S. privacy laws provide protection against the disclosure of a person's phone number without their permission. To comply, the FCC mandated that all phone companies must provide ways for the residential consumer to control the display of their caller ID information.

· The FCC also requires if blocking is in place, the ability to unblock must also be present.

·

http://www.epic.org/privacy/caller_id/fcc_final.html

·

http://www.fcc.gov/Bureaus/Common_Carrier/News_Releases/1995/nrcc5049.txt

·

http://ftp.fcc.gov/cgb/consumerfacts/callerid.html

· Example: Customers are able to block their phone number on a per call basis from being displayed on a Caller ID device by dialing * 67 before dialing the telephone number.

· The AT&T policy is based on FCC Docket 91-281. The FCC requires if permanent blocking is in place, the ability to unblock by dialing *82 must also be present.

· The ability to dial *67 or *82 is only possible on line side services and not available on trunks.

· PRI is a trunk side service. A PRI provisioned with permanent blocking on it would not be able to turn it off (i.e., unblock) on a per call basis. That would be in violation of the FCC docket.

Are there any other options available that would allow Caller ID blocking?

· YES. Caller ID blocking is a PBX/CPE function.

· The CPE vendor would decide what code the station user would send (could be *67) to block the Caller ID on a per call basis.

· The CPE can also be set up to permanently block all out going Caller ID in the Setup Message by setting the Presentation Indicator to Restricted.

What if the CPE doesn’t offer a feature to block Caller ID?

· The Telcordia documents for Custom PRI (5E and DMS) and NI-2 PRI all specify that Caller ID Blocking is a function of the PBX/CPE.

· The privacy indicator is sent by the CPE over the D Channel in the call Setup Message.

· Controlling the delivery of Caller ID from the customer’s own CPE is a far superior option.

· The customer has total control over which stations are flagged for privacy and which are not.

· Most CPE allow stations selective dialing to turn Caller ID on and off.

· Most CPE can also allow assigning rules for Caller ID delivery by station number or by a group of numbers.

· Legacy SBC switches will honor the privacy indicator and will not pass Caller ID name or number.

· The called party’s Caller ID message will be ANONYMOUS or PRIVATE.

· Note: The actual message displayed on the Called Party’s end varies by manufacturer.

Aren’t ANI (Automatic Number Identification) DNIS (Dialed Number Identification Service) and Caller ID the same thing?

· NO. While these terms are often used interchangeable, they are actually completely different services / technologies.



ANI

· Automatic Number Identification is part of a standard set of voice features called Feature Group D and primarily used for billing purposes between telecommunications carriers.

· ANI is billing information that is sent along with a call that identifies the calling party’s billing telephone number (and other call information) before the call is connected.

· For example, businesses such as call centers subscribe to ANI service. They pay for incoming caller's telephone numbers to be sent to them simultaneously with their incoming toll free service calls.

· Class 5 Trunking does not pass ANI.



DNIS

· DNIS stands for Dialed Number Identification Service. DNIS Provides the ability to identify the dialed Toll Free Service number on a call-by-call basis. Local PRI does not support DNIS.



Caller ID

· Caller ID is a locally provided service that is available between a group of central offices for call identification purposes.

· ANI and Caller ID both use the Signaling System 7 (SS7) digital information network.

· With PRI, SS7 data is transmitted via the D Channel. This is referred to as “out of band” signaling. The signaling information is not carried on the same path as the actual call.

· With Lines and Trunks, ANI is sent in the same communications path or bandwidth as the call. This is referred to as “In Band” signaling.

· NOTE: Digital Trunking services (DTS-E, Multipath, SuperTrunk, DLS) utilize DTMF (Dual Tone Multi-Frequency) signaling protocols. DTMF is not compatible with SS7. Delivery of ANI or Caller ID to or from the digital trunk subscriber cannot be accomplished.

· DTMF type signaling is an in band signaling protocol. All of the call set up and charge information is sent on the same communications path as the actual call.

· SS7 is an out of band signaling protocol. The SS7 network is a separate data network designed to maximize the efficiencies of the network used for actual user information (voice or data). The call set up and charge information is sent on the SS7 network. If the distant end is available and can accept the call, then and only then is a connection path established on the PSTN network for call completion.

· Unlike Caller ID, the ANI information is not accessible to the typical phone user and therefore cannot be blocked by the subscriber. Blocking of the ANI information is not possible. ANI is used for long distance billing and call location identification when calling 911.

· Applications for ANI, DNIS and/or Caller ID.

· Call centers who have phone systems with CTI (Computer Telephony Integration) capabilities. Inbound Caller ID, ANI and/or DNIS is used to route the call to the appropriate department or agent. Searches in the call center’s database allows valuable customer background information to be presented to the agent with the call for more personalized call handling.

Does PRI support ANI (Automatic Number Identification)?

· NO. ANI is used for billing purposes between carriers. Caller ID is a locally provided service that is available between a group of central offices for call identification purposes

Does PRI support Customer Provided Calling Party Numbers (CPN)?

· AT&T’s policy is we will pass the telephone number we receive over the PRI from the CPE as the CPN as long as the number received is a valid DID number associated with that PRI trunk group.

· AT&T does not guarantee that non-valid PRI numbers will be forwarded as the CPN. In those situations, the telephone number associated with the specific PRI trunk group will be sent out as the CPN.

Why is no name sent sometimes when the customer provides CPN?

· If the customer provided CPN is not a telephone number provisioned on the PRI, there is no method for our locally provided database to know who the customer is in order to add the name.
***------------------------------------------

This should clarify some of misinformation about CID and PRI service that has floated around the forums for some time. At least in relation to the current "AT&T" ILEC footprint, but I would assume other ILECs are probably very similar.

....JIM....

 

[RikRodgers]

And noone's given you a star yet?

Well deserved. Most of my customers are in ATT territory.

Thanks for the good info.

 

[dialtonebone]

PAETEC does do incoming name/number. I have the service myself, it took a bit of extra work to get it turned on. Specifically something on there side needed to be activated I remember.

As for outgoing, PAETEC only lets you control the number. Most providers are like this though.