iPECS UCP600 - Page 281

iPECS eMG80/100& eMG800 & UCP & vUCP
Administration and Programming Manual Issue 2.5
267
Table 4.4.8.3-1 SIP CO ATTRIBUTES
ATTRIBUTE
DESCRIPTION
RANGE
DEFAULT
Called ID
Selection
For call routing, the “SIP Request” or “To” header will be
employed by the system as the “Called Party ID.”
Request URI, To ID
Refer to
description
Request
URI
SIP Timer set
T1 Timer
First retransmission timer in case of No Reply.
0.5 / 1 / 2
0.5 (Sec)
Miscellaneous set
Drop Busy
Station
While busy, the system can be configured to terminate a station
call and accept and connect any new call from the SIP Trunk. For
special use, it is available only in Italy.
No
Yes
No
Ignore INBAND
DTMF
In some situations, DTMF tones from the connected party may be
received along with the DTMF Type specified above. This can
cause errors in detection, such as double digits. In this case, the
system can be configured to ignore Inband DTMF signals. If
selected as the “DTMF Type” above, do not disable Inband
signals, as this may disable DTMF detection.
No
Yes
No
SIP Trunk
Group
Multiple SIP User ID ranges may register with the SIP CO, for
example, SIP COs from different providers. When different SIP
User ID ranges are required on a SIP CO, a different SIP Trunk
Group should be assigned to each range. Note this has no
relationship with the CO/IP Line Group.
0~71 (0:Normal, 1-71:Check To header)
Refer to
description
0
Send Refer for
Transfer
The system can employ the SIP Refer method to forward or
transfer incoming calls to an “Off-net” location if supported by the
SIP Service Provider.
No
Yes
No
CN Payload
Insert
When Comfort Noise generation is desired, the system will
provide a Comfort Noise Payload during periods of silence.
No
Yes
No
Ignore 180
after 183
If the option is Yes, an appropriate ringback tone may be played
to the calling party when the called party's phone is alerting
without changing the internal or system ringback tone. For
example, when placing a call from the USA to Korea, the caller
hears a Korean ringback tone.
No
Yes
No
Add
“user=phone”
parameter
For outgoing SIP call, "user=phone" will be added in the Request
URI of INVITE.
No
Yes
No
Advice of
Charge
When assigned, The system estimates the call cost for display on
the phone with appropriate regional protocol support.
No Service, SIP AOC
Refer to
description
No Service
TGID Usage
Usage of “trgp” and “trunk-context” parameter in Contact header
in INVITE
 YES: “trgp” and ‘trunk-context” are added in the Contact
header.
 NO: “trgp” and ‘trunk-context” are not used.
No
Yes
No