Introduction
The beroNet Gateway is a modular SIP Gateway, which translates the SIP Protocol according to RFC3261 [1] into the protocols of the following technologies:
...
Each of these technologies has at least 1 Information Element which contains the caller-id. Since SIP is a rather loosely defined protocol standard, there are different recommendations and drafts which define in which Header element the caller-ids can or must be present. The following table shows which kind of Information elements or Header Elements are popular and often used in which technology:
| technology | caller id options |
|---|---|
| SIP | Headers: From:, P-Preferred-Identity:, P-Asserted-Identity:, Remote-Party-Id: |
| ISDN | Information Elements: OAD, OAD2, QSIG Name |
| Analog | Information Elements: Caller ID, Calling Name |
| GSM | Information Elements: Caller ID |
Besides the amount of different fields which contain "the" caller-id, there are also additional sub elements or degrees of freedom, which are discussed in the following chapters.
Caller-Id Formats
SIP
Each SIP Header which may contain "the" caller-id has follows the same structure:
"DISPLAYNAME" <USER@SERVER>
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.
...