NEC Electra Elite IPK II System User Manual page 603

Electra Elite IPK II
The LAN/WAN connection is provided by a 10 Base-T/100 Base-TX Ethernet connector. This

connector is a single 10/100 mbps Ethernet Connector. This port has Auto-Medium Dependent
Interface Crossover (MDIX) to allow using either a straight-through Ethernet cable for connection
to a PC or a crossover Ethernet cable.
Duplex mode (Auto, Full, or Half) and speed (10/100 mbps) are configured via Elite IPK II KSU

Programming.
Default UDP listen port for SIP Trunk is 5060.

IPK II SIP supports 100 rel option

(IETF draft-ietf-sip-session-timer-10.txt).
IPK II SIP supports Early Media.

IPK II SIP restricts an outgoing call under the following conditions:

SIP configuration failed

SIP registration failed

CPUII and MG16 Link down

Lack of MG16 DSP resource

Lack of MG16 bandwidth

IPK II SIP supports MD5 Authentication flow for a SIP server. (Refer to IETF RFC 3261 for more

information).
IPK II SIP supports multi-UAs registration for one SIP server.

IPK II SIP Trunk supports a DNS resolution access and an IP address direct access for SIP server.

(Refer to IETF RFC 3261 for more information).
IPKII SIP Trunk can connect a SIP server over NAPT router by one IP address.

IPK II SIP can transport DTMF digits in-band according to IETF RFC 2833, or by using

uncompressed codec such as G.711 (Configured in system programming).
IPK II SIP Trunk supports the sub-address feature with SIP trunk interconnection. (IPK II SIP Trunk

to IPK II SIP Trunk).
Conditions
If Program 10-29-01 : SIP Proxy Setup – Outbound Proxy is set to 0 (Off), then all other

programs under 10-29 must be manually configured to default values.
The IPK II does not support the simultaneous use of a SIP Trunk inter-connection and a

SIP Trunk carrier connection modes. If connection between IPK II systems is desired while
working with the SIP providers, then both IPK II systems must individually register such a
service provider.
IP Trunk (SIP) – MG16
and Session Timer option
(IETF RFC 3262)
Document Revision 4C
2 - 579