Creating Trunks - Snom ONE IP Technical Manual

Deploying the snom ONE IP Telephone System
130
Over the last few years, providers have developed different methods of representing
these two numbers:
•
RFC 3325 describes a way to represent these two numbers. In most cases, it
makes sense to use the
From header in the INVITE represents the display number, while the
Asserted-Identity
tation can be done with the
changes only the name of the header from
Preferred-Identity
•
No Indication: This method simply discards the display number and uses
only the network number in the
the provider cannot handle any other method. The disadvantage here is clearly
that any redirection information gets lost.
•
Remote-Party-ID: This method is described in a draft that expired years
ago; however, there is still a lot of equipment outside that is supporting this
method. In this case, the
number, while the
•
RFC 3325, but don't hide: This method should not be used. It has been used
in environments where the fields have gotten mixed up, and it is creating even
more confusion.
•
To strip the first digit from a DID number, you can use the pattern
9]*)!\1!u!100

Creating Trunks

This procedure shows you how to create trunks.
1. From the domain where the trunk will be used, click the Trunks tab.
2. Enter a name for the trunk. You can name the trunk anything you prefer (e.g.,
company name, department, etc.). The name must consist of alphanumeric
characters and may contain spaces.
P-Asserted-Identity
header has the network number. A similar represen-
P-Preferred-Identity
. The rest remains the same, as in the first method.
From
From header in the INVITE represents the network
P-Asserted-Identity
(default destination would be 100).
header. In this case, the
header. The system
P-Asserted-Identity
header. This method is a fallback when
header is the display number.
P-
to P-
!1([0-