EasyManua.ls Logo

iPECS UCP - Page 478

iPECS UCP
689 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
iPECS eMG80 & eMG800 & UCP
Administration and Programming Manual Issue 1.6
463
Table 4.4.8.6-1 SIP User ID ATTRIBUTES
ATTRIBUTE DESCRIPTION RANGE DEFAULT
The Authentication name from the provider must be entered
for proper SIP registration.
Authentication User
Password
The SIP Service Provider may require authentication of the
user for registration and at other times during call setup.
The Authentication password from the provider must be
assigned for proper SIP registration.
Max. 32
characters
Contact Number
The Contact header of SIP messages is populated with the
specified SIP User ID.
Max. 16
characters
Contact Display Name
The Display Name specified is used for the Contact header
Name field.
Max. 21
characters
Associative Station
Number
Not used. Station number
User ID Register
The SIP Trunks are provided in two formats
1) Registered: the system must register for service
often using Authentication
2) Provision: the provider sends all SIP messages to a
fixed IP; the system does not register for service.
Register/
Provision
Provision
Authorized
Representative ID
Table Index
The User Id can be assigned an index of another User ID.
When the SIP CO is configured to employ the Authorized
Representative Id as the SIP “From” or “Contact” header,
the indexed User ID is employed.
eMG80:0~140
eMG800:0~1200
UCP:0~2400
0
User ID Usage
If registration is enabled (User ID Register above) the
iPECS can send the User ID or Authorized Representative
ID to the SIP Proxy to register the ID. Otherwise, only the
Authentication Name and password are used.
OFF
ON
OFF
Ring Route Type
Incoming calls from a SIP trunk can be routed
1) to the ID assigned Station (any station with any of the
SIP
User ID Table Indices in PGM 111 matching the incoming
SIP User Id),
2) based on CO/IP Ring assignments (PGM 144),
3) using DID treatment defined below, or
4) follow the MSN Table routing (PGM 145).
ID Assigned
Station/
Ring Assignment/
DID Conversion/
MSN-DID
Conversion(PGM
145)
ID
assigned
Station
DID Conversion Type
When the Ring Route above is defined as DID, the system
will send the call to a destination based on the DID
conversion selected here. The digits in the SIP User ID may
be used “as is” to identify the desired station, modified
based on the DID Digit mask below and routed to the
resulting station or the modified DID number can be used as
an index to the Flexible DID Conversion Table, PGM 231 to
route the call.
DID Digit
Conversion/
Use as is’/
Modify Using
Flexible DID
Conversion Table
Use as is
Number of Digits (2-4)
Expected from DID
Circuit
When DID Digit Conversion or Flexible DID Conversion
Table routing is used, the number of digits received is
defined in this field.
2-4 3
DID Digit Mask
(4digits: *,#,0-9
When DID Digit Conversion or Flexible DID Conversion
Table routing is used, the digit conversion is defined in this
field. For each of the four (4) digits, use “*” to accept any
digit, “#” to delete the digit, or a digit 0-9 to replace the digit.
4 Digits: *, #, 0-9 #***
SMS Received Station
Number
When an SMS is received for this User Id, the Station to
receive the SMS must be defined.

Table of Contents

Other manuals for iPECS UCP

Related product manuals