...
In a pure SIP Environment, the DISPLAYNAME part contains the users name as text, the USER part contains either the username, but also often the extensions or caller-id. Most SIP providers use the following mapping:
| Header Part | Usage |
|---|---|
| FROM_USER | Authentication Username |
| PAI_USER | caller-id |
| PPI_USER | caller-id |
| FROM_DISPLAYNAME | not used |
| PAI_DISPLAYNAME | not used |
| PPI_DISPLAYNAME | not used |
The caller-id itself has also varying possibilities of formatting. The caller-id has typically the following structure:
...
the most varying element can be the "international-prefix", which is often just a plus "+" sometimes it may also be a double zero "00". The following examples show the varying options for the caller-id "+492593890"
| Name | International Prefix | International Code | National Code | Base Number | Extension |
|---|---|---|---|---|---|
| International Number with plus | + | 49 | 30 | 259389 | 0 |
| International Number with double zero | 00 | 49 | 30 | 259389 | 0 |
| International Number without prefix | 49 | 30 | 259389 | 0 | |
| National Number (note: 0 as National Prefix) | 030 | 259389 | 0 | ||
| Unknown Number / Local Number - without prefixes | 259389 | 0 |
Most providers do only accept one of the above variants, in order to display the correct caller-id or even to forward the call at all.
ISDN
In ISDN the OAD and OAD2 fields represent the caller-id. They are comparable to the P-Asserted-Id and P-Preferred-Id Headers in SIP. The OAD Information elements carry additional information about the type of the caller-id. There are the following so called type-of-numbers:
- unknown
- local
- national
- international
Depending on the type of number, the caller-id itself must be in the right format, otherwise the PBX / Carrier displays the wrong caller-id or even doesn't forward the call at all. The following table shows for the caller-id "0049302593890" how the type-of-number affects notation of the caller-id:
| Type of Number | Sample Callerid | Description |
|---|---|---|
| unknwon | 2593890 | caller-id without any prefixes |
| local | 2593890 | caller-id without any prefixes |
| national | 302593890 | caller-id with national prefix (without leading 0) |
| international | 49302593890 | caller-id with international prefix and national prefix (without leading zeroes) |
Gateway Conversion
The beroNet Gateway has also the ability to match dialplan rules against the caller id. It uses the Source in the dialplan for matching and the NewSource to generate the caller id for the outbound technology.
This document describes how to configure the caller id matching and output behaviour of the beroNet Gateway.
Contents
...
...
New Dialplan
The the beroNet Gateway Dialplan allows to match the dialed Number (Destination) and the Callerid (Source) against Patterns. It also allows to modify the Destination and Callerid, for example to put a prefix (like 0) before a Number. Each Dialplan Rule can carry additional Configuration options that are only valid for this rule. With these tools it is possible to modify the call handling behavior of the beroNet Gateway per Destination Number or per CallerID. One usage example is to enable or disable CLIR per Destination prefix.
...