User`s manual
SIP User's Manual 374 Document #: LTRT-83303
Mediant 1000 & Mediant 600
ini File Parameter Description
For ETSI ISDN variant, the following Number Plan and Type combinations (Plan/Type) are supported
in the Destination and Source Manipulation tables:
0,0 = Unknown, Unknown
9,0 = Private, Unknown
9,1 = Private, Level 2 Regional
9,2 = Private, Level 1 Regional
9,3 = Private, PISN Specific
9,4 = Private, Level 0 Regional (local)
1,0 = Public(ISDN/E.164), Unknown
1,1 = Public(ISDN/E.164), International
1,2 = Public(ISDN/E.164), National
1,3 = Public(ISDN/E.164), Network Specific
1,4 = Public(ISDN/E.164), Subscriber
1,6 = Public(ISDN/E.164), Abbreviated
For NI-2 and DMS-100 ISDN variants the valid combinations of TON and NPI for calling and called
numbers are (Plan/Type):
0/0 - Unknown/Unknown
1/1 - International number in ISDN/Telephony numbering plan
1/2 - National number in ISDN/Telephony numbering plan
1/4 - Subscriber (local) number in ISDN/Telephony numbering plan
9/4 - Subscriber (local) number in Private numbering plan
SecureCallsFromIP
For a description of this parameter, refer to ''Advanced Parameters'' on
page 166.
AltRouteCauseTel2IP
This ini file table parameter configures SIP call failure reason values
received from the IP side. If a call is released as a result of one of these
reasons, the device attempts to locate an alternative route to the call in
the 'Tel to IP Routing' table (if Proxy is not used) or used as a redundant
Proxy (when Proxy is used).
The format of this parameter is as follows:
[AltRouteCauseTel2IP]
FORMAT AltRouteCauseTel2IP_Index =
AltRouteCauseTel2IP_ReleaseCause;
[\AltRouteCauseTel2IP]
For example:
[AltRouteCauseTel2IP]
AltRouteCauseTel2IP 0 = 486; (Busy Here)
AltRouteCauseTel2IP 1 = 480; (Temporarily Unavailable)
AltRouteCauseTel2IP 2 = 408; (No Response)
[\AltRouteCauseTel2IP]
Notes:
The 408 reason can be used to specify no response from the remote
party to the INVITE request.
This parameter can include up to 5 indices.
For defining the Reasons for Alternative Routing table using the Web
interface, refer to ''Reasons for Alternative Routing'' on page 209.
For an explanation on using ini file table parameters, refer to
''Structure of ini File Table Parameters'' on page 293.