Calling Party Name and Numbers

The Peeredge SBC supports both calling party name and numbers. The name (up to 15 characters) displayed to PSTN users is often not the name provided in the customer’s SIP Invite message sent to the Peeredge SBC. Most TDM-based PSTN service providers have or subscribe to a Calling Name (CNAM) database service.  These service providers query this database during the call setup for the calling party name based on the telephone number provided in the To Headers of the SIP Invite and will use the name returned by the CNAM query. Several PSTN service providers require the telephone number in the To header to be formatted as a national or e.164 number. The name pulled from the CNAM database will be the name associated with the telephone number(s) when the order was placed for the new or existing numbers ported to the 46 Labs Peeredge SBC. 46 Labs recommends that the customer set the Caller Name field in the SBC/PBX’s line appearance for each directory number to the same name assigned in the CNAM database to avoid confusion.

The Peeredge SBC supports both the Privacy Asserted-Identity (PAI) and the Remote‑Party-ID (RPID) headers in SIP Invite messages. However, 46 Labs’s PSTN vendor partner is configured to ignore Remote‑Party-ID (RPID) headers in SIP Invite messages. These headers are used to pass Calling Line ID Presentation and Calling Name Presentation information. 46 Labs recommends configuring SBC/PBX to send PAI headers.

Calling Party Numbers

The Peeredge SBC delivers the calling party number to the customer SBC/PBX for all inbound calls in e.164 or plain number (1 + 10 digit) format for non-international calls, based on how the service is configured or ordered.  However, 46 Labs recommends all inbound and outbound calls are delivered and sent in an e.164 format. The SBC/PBX should be configured to normalize the calling party number to the desired format for presentation to the endpoint (IP Phone, voicemail, etc.).