All About Caller ID

All About Caller ID

OUTBOUND CALLER ID

Outbound caller ID is handled differently for on-net calls and off-net calls.

An on-net call is a call from one phone on the Cloud9Phone network to another phone on the Coredial network.
So for example if a customer calls you, the service provider, that is an on-net call.
On-net calls are processed in the Cloud9Phone NOC and do not involve the PSTN.

An off-net call is a call to a phone not on the Cloud9Phone network,
Off-net calls by definition are pushed out to a carrier on the PSTN.

Outbound On-net Calls
Outbound caller ID for an on-net call will be the CNAM field on the main Settings page in the portal.
Contrary to the mouseover tool tip on the main settings page, the CNAM on this page does NOT override the CNAM on the Phone Number detail page.

Outbound Off-net Calls

Outbound caller ID for an off-net call to the PSTN will be the CNAM field on the Phone Number detail page in the portal.

What happens on the terminating end is that the carrier performs a "dip" or lookup on the number we pulse out in the Invite,

and they display a Caller ID to their customer based on that lookup. 

Typically the lookup or "dip" is performed with TNSI, a third-party database where the CNAM data in our portal is stored.

If the terminating carrier fails to dip from TNSI and performs a lookup on their own database:

the caller may not see the correct caller ID and in that case the terminating carrier must be contacted to resolve.

The Caller ID Storage Setting setting must be enabled to allow the CNAM in the phone number page to be stored with TNSI.

If this is not set no changes in the CNAM will be pushed out to TNSI.

To push a CNAM out again to TNSI from the Phone Number page:

1. Make a change in the CNAM such as adding a space and hit Save,

2. Restore the correct CNAM, then hit Save again.

>>>>>>>>>>>>>>>>>  It is not sufficient to just Save this page, you must make a change in the CNAM and then restore it.

Then it will say something like (Pending update on 2/17/2014 02:00:00 PM) which means it will push out to the TNS or Bandwidth database at 2pm.

From there it goes into their queue(s) to be updated which can take 48-72 hours.\

___________________________________________________________________________ 

INBOUND CALLER ID

To display inbound caller ID to your customer, enable "Caller ID Name lookup for customer" feature in the main Settings page.

Inbound caller from most carriers invokes a dip in the TNSI database to extract the Caller ID.

This transacts at the SBC (session border controller) which receives the call and passes it to the feature server.

The dip looks like this. The SBC appends the caller ID to the Invite and passes it to the feature server.

Feb 14 09:16:26 SBC01 /usr/sbin/opensips[22516]: INFO: Received valid TNS reply (on_reply_route[21]): "Peter Gibbons" sip:+18883332222@sip.cloud9phone.com for Call-ID (672002588_70222573@75.100.75.100)
Feb 14 09:16:26 SBC01 /usr/sbin/opensips[22516]: INFO: TNSi (failure_route[21]): Call-ID (672002588_70222573@75.100.75.100)
Feb 14 09:16:26 SBC01 /usr/sbin/opensips[22516]: INFO: Did CNAM lookup (branch_route[21]): Adding CNAM ("Peter Gibbons") to call from (sip:+18883332222@75.100.75.100:5060) Call-ID (672002588_70222573@75.100.75.100)
Feb 14 09:16:29 SBC01 /usr/sbin/opensips[22545]: INFO: Main routing (route): method (ACK) r-uri (sip:2155554444@64.94.196.25:5060) f-uri (sip:+18883332222@75.100.75.100:5060) from-ip (75.100.75.100) Call-ID (672002588_70222573@75.100.75.100)
Feb 14 09:19:10 SBC01 /usr/sbin/opensips[22519]: INFO: Main routing (route): method (BYE) r-uri (sip:2155554444@64.94.196.25:5060) f-uri (sip:+18883332222@75.100.75.100:5060) from-ip (75.100.75.100) Call-ID (672002588_70222573@75.100.75.100)