Page 1

 Basic SIP configuration

 Specific settings for SIP Service
 Specific configurations
 Trace related with SIP
 Trouble Shooting

Page 3
 There are currently three protocols widely used
in VoIP implementations the

 H.323 family of protocols – Intelligence and

control at every component.

 SIP - the Session Initiation Protocol (SIP) -

Intelligence and control at End Points only

 MGCP- Media Gateway Controller Protocol -

Intelligence and control at Network
components.
Page 3
 SIP Common Attributes PGM 210

 Enter DNS Address

- If Domain Name is used for SIP server, DNS Query will be sent to DNS
Address.

Page 4
 SIP TRUNK Status

Page 5
 PGM 126 _ User ID Attributes

 Enter Registration ID – check [CheckBOX] before saving data.

- Enter index number and Click [Load] - index1 is used in capture.
- Enter “Registration User ID” – ID@serveraddress.
- Enter “Authentication User ID” and “Authentication User Password”.
- Set “User ID Usage” – ON and set “User ID Register” – Register/Provision.

Page 6
 PGM 126 _ User ID Attributes

PGM 111 _ Station Attributes

Page 7
 PGM 133 -SIP CO Attributes

Page 8
 PGM 133 CO Attributes

 Soft Switch Type : It depends on the server type tested with LIK/eMG/UCP.
- Default : Normal
 Proxy Server Address : SIP Server Address - IP Address or Domain.
 Domain : SIP Server - IP Address or Domain.
Domain

Page 9
 PGM 133 CO Attributes

 P-Asserted-ID, Remote-Party-ID :
- Set Usage of P-Asserted-ID and Remote-Party-ID
 From ID, P-Asserted-ID, Contact, Remote-Party-ID
- Select outgoing CLI rule.

Page 10
 PGM 133
ID Settings Description
Extension • Follow PGM111 - SIP USER TABLE INDEX number.
SIP-User-ID Table • SIP USER TABLE INDEX number must be set PGM126-index.

Extension • Follow ISDN Outgoing CLI rule.

Outgoing CLI • PGM113, PGM151, PGM201 ..
Authorized • Follow PGM126 - Authorized Representative ID Table Index
Representative ID
• Follow PGM133 - SIP User ID Fixed Table Index
Fixed Table • Normally main ID will be used.

Original CLI • Use CLI of incoming Trunk. – Call Forward, Call Transfer case.

Extension • Follow PGM133 - ID Individuality- From ID.

Display Settings Description

• Use Station Name of related station.
- Normal outgoing call : name of outgoing station.
SYS RULE - Call forward : name of forwarding station
- Co-Co Call forward : name of attendant station.

Original • Use name received from incoming Trunk. If there is no name, CLI will be used as diaplay.

Page 11
 PGM 111 Station ID SIP Attribute

Page 12
 PGM 133

 Registration UID Range: Enter index number of PGM126 related with Registration ID

Page 13
 SIP UID Alloc Status

 User can see the ID allocation status.

Page 14
 SIP Registration Status

 User can see the Registration status.

- Register/Provision
- Registration Status in case of Register

Page 15
 SIP Trunk Status

 User can see the Admin Status for Trunk

- 150.150.131.207 for Trunk 7-8.
- sipconnect.qsc.de for Trunk 9-14.

Page 16
 Incoming call

 Incoming CLI is matched with PGM126 – index .

- Follow PGM 126 - Ring Route Type. (Below)
(ID Assigned station, Ring assignment, DID conversion, MSN-DID conversion)
 Incoming CLI is not matched with PGM126 – index .
- Follow ISDN rule. ->PGM145, PGM151.

Page 17
 Incoming call

 Incoming CLI is matched with PGM126 – index .

- Follow PGM 126 - Ring Route Type.
(ID Assigned station, Ring assignment, DID conversion, MSN-DID conversion)
 Incoming CLI is not matched with PGM126 – index .
- Follow ISDN rule. ->PGM145 (Below), PGM151.

Page 18
 Incoming call Incoming CLI is matched with PGM126 – index .
- Follow PGM 126 - Ring Route Type.
(ID Assigned station, Ring assignment, DID conversion, MSN-DID conversion)
 Incoming CLI is not matched with PGM126 – index .
- Follow ISDN rule. ->PGM145 , PGM151(Below).

Page 19
 SIP Phone Attributes For New Registration – PGM 211

Page 20
 Local Station User login for SIP Phone – PGM 443

Page 21
 Remote Station User login for SIP Phone – PGM 443

Page 22
 SIP Phone Provisioning – PGM 212

Page 23
 SIP Phone Provisioning – PGM 212

Page 24
 Trunk configuration

 Configure Basic SIP configuration between UCP and eMG80. Practice

SIP Trunk

Sta(1000) UCP(10.10.10.2) eMG(20.20.20.2) Sta(1000)

Tel : 12341000 Tel : 56781000

Page 25
 Trunk configuration

 Configure Basic SIP configuration with F/W device. Practice

- Set Port Forwarding in each F/W – SIP port and RTP
ports
- Set F/W IP in PGM102 - Firewall IP Address and PGM132 - Firewall IP
Address.
UCP:
-. Slot number of VOIM (2402)

eMG80:
-. Slot number of VOIB (14)

UCP(10.10.10.2) FW(192.168.1.1) FW(192.168.1.2) eMG(20.20.20.2)

Sta(1000) Sta(1000)
GW(10.10.10.254) GW(20.20.20.254)

Tel : 12341000 Tel : 56781000

Page 26
 SIP Group for SIP Trunk Control

All SIP Trunk will be grouped based on PGM133 – Proxy Server Address.
- For Co 1~24, Proxy Server Address is 192.168.131.200.
- For Co25~48, Proxy Server Address is 150.150.150.200.
- Then two SIP trunk Group will be stored.  Co range must be sequential.

Trunk:1~24, 192.168.131.200 Trunk:25~48, 150.150.150.200

From 192.168.131.200

INVITE From INVITE From

192.168.131.200 150.150.150.200

Incoming SIP Call will be distributed

based on Server Address

Page 27
 PGM133 - SIP Trunk Group

It is independent with PGM140 – CO/IP Group.

- SIP Trunk Group setting is just used in SIP Trunk.
With different PGM133-SIP Trunk Group value, it will be treated as different SIP Group
even though PGM133-Proxy Server Address is same.

SIP Trunk Group 1, Reg UID : 1-2 SIP Trunk Group 2 Reg UID : 3-4
1~24, 192.168.131.200 25~48, 192.168.131.200

INVITE with UID 1 or 2 INVITE with UID 3 or 4

Incoming SIP Call will be distributed

based on Server Address & Reg UID in
PGM126

Page 28
 PGM133 –Diversion Recursing
Some Proxy Server supports 302 response for Call Forward.

Recursing None Recursing

302 Moved
OFF: 2 Trunk
Temporary ON: Send 302
will be seized - Server control
for Call forward outside Parties

Two SIP Trunks No SIP Trunk

are used is used

Page 29
 PGM133 – Send REFER for Transfer

Some Proxy Server supports REFER message for Transfer.

P133, “Send Refer for Transfer”

REFER
OFF: 2 Trunk ON: Send REFER
will be - Server control
seized for outside Parties
transfer

Two SIP Trunks No SIP Trunk

are used is used

Page 30
 PGM133 – SIP User ID SELECTION

PGM111- SIP USER TABLE INDEX, SIP USER TABLE INDEX2, SIP USER TABLE
INDEX3 are used for different service provider.

PGM111

PGM126

Page 31
 PGM133 – SIP User ID SELECTION

Server:1.1.1.1 Server:2.2.2.2 Server:3.3.3.3

1~24, Server: 1.1.1.1 25~48, Server: 2.2.2.2 49~72, Server: 3.3.3.3

PGM133 - SIP User ID SELECTION PGM133-SIP User ID SELECTION PGM133-SIP User ID SELECTION
SIP USER TABLE INDEX SIP USER TABLE INDEX2 SIP USER TABLE INDEX3

INVITE with index1 ID INVITE with index2 ID INVITE with index3 ID

(From : [email protected]) (From : [email protected]) (From : [email protected])

From ID will be selected by SIP User ID SELECTION

Page 32
 PGM133 – Secondary Proxy Server

 PGM133-Soft Switch Type : KT, KT Centrex.

- Follow specific redundancy flow.
 PGM133-Soft Switch Type : Normal
- PGM133-Redundancy Usage : Fail Over – If there is no response from Proxy Server.
-PGM133-Redundancy Usage : Load Balancing – Use Proxy Server and Secondary Proxy
Server evenly.

primary server secondary server

Fail Over

Page 33
 PGM133 – Soft Switch Type(DNS REDUN), PGM210 - DNS SRV Usage

 DNS Service Query is performed to get IP address.

 System sends INVITE to all IP addresses evenly.
 System accepts INVITE from all IP addresses.
 Example : Server Domain : sipconnect.qsc.de
59642320-[Sipm_SipTimerCallBack] DNS Redun, now!!!(Provider:2)
59642320-Sipm_GetDnsQueryResult Start: sipconnect.qsc.de
59642331-Sipm_SipResolverReportDataEv : mode=TRANSPORT BY NAPTR, nextmode=TRANSPORT BY 3WAY SRV, query=sipconnect.qsc.de
59642339-Sipm_SipResolverReportDataEv : mode=TRANSPORT BY 3WAY SRV, nextmode=IP BY HOST, query=sipconnect.qsc.de
59642339-Sipm_SipResolverReportDataEv Srv:1, Host:2, IP:0
59642339-Sipm_SipResolverReportDataEv : srv=_sip._udp.sipconnect.qsc.de (SIP service query)
59642339-Sipm_SipResolverReportDataEv : host=duro01.sipconnect.qsc.de, priority:10, weight:10, port:5060, proto:0
59642346-Sipm_SipResolverReportDataEv IP_BY_HOST: 213.148.136.222(providerIndex:2, NumHost:1)
59642346-Sipm_SipResolverReportDataEv IP_BY_HOST(mode:NAPTR): 1-st Server:213.148.136.222
59642346-Sipm_SipResolverReportDataEv : mode=IP BY HOST, nextmode=IP BY HOST,
query=duro01.sipconnect.qsc.de
59642346-Sipm_SipResolverReportDataEv Srv:0, Host:1, IP:0
59642346-Sipm_SipResolverReportDataEv : host=duro02.sipconnect.qsc.de, priority:20, weight:10, port:5060, proto:0
59642354-Sipm_SipResolverReportDataEv IP_BY_HOST: 213.148.136.190(providerIndex:2, NumHost:0)
59642354-Sipm_SipResolverReportDataEv IP_BY_HOST(mode:NAPTR): 0-st Server:213.148.136.190
59642354-Sipm_SipResolverReportDataEv : mode=IP BY HOST, nextmode=Undefined,
query=duro02.sipconnect.qsc.de

Page 34
 PGM133 – Soft Switch Type(DNS REDUN), PGM210 - DNS SRV Usage

 List of service provider using DNS REDUN.

- (1)sip-corporate.tele2.se, (2)nexvortex.com, (3)sipconnect.qsc.de

 Set PGM210 – Primary DNS Address.

 Set PGM210 – DNS SRV Usage.
 Set PGM133 – Soft Switch Type : DNS REDUN.
 Set PGM133 – Proxy Server Address : nexvortex.com.
 Set PGM133 – Domain : nexvortex.com.
 Press PGM133 – [REGISTER] button.
 Check IP Addresses resolved in system trace or ethereal trace.

Page 35
  SIP trunk is provided by an Internet Service provider (ISP) and its network is divided
from default network (internet) by using second router device.

Local: 10.10.10.0/24
Internet Router 1
IP: 10.10.10.254

UCP

FW: 4.3.2.1 IP: 10.10.10.2

SIP Trunk VOIM

Router 2
IP: 10.10.10.10
ISP

FW: 1.2.3.4IP: 10.10.10.253 default route

static route

Page 36
  The static routes feature can be used to communicate with second broadband network.
So you need to know the network address of SIP and media servers from ISP.

Page 37
 Dual Broadband

 Static Route, VOIM/VCIM/VVMU/VOIB8-24

Page 38
 Dual Broadband

 SIP Signaling
1) UCP sends SIP packets to router 2 by static route.
2) Configure the firewall IP address of router 2 and enable ‘USE Board IP for SIP’ field for the
dedicated SIP trunk. (green line)
 Media Exchange Between VOIM and SIP Media Server
VOIM sends RTP packets to SIP media server by static router.
 Media Exchange Between VOIM and Remote Device
Configure the firewall IP address of router 1 at ‘RTP Packet Relay Firewall IP Address’ field.
(yellow line)
Local: 10.10.10.0/24
Internet Router 1
IP: 10.10.10.254
UCP
FW: 4.3.2.1 IP: 10.10.10.2

SIP Trunk VOIM

Router 2
IP: 10.10.10.10
ISP
IP: 10.10.10.253
FW: 1.2.3.4 default route
static route
Page 39
 Dual Broadband with WANU

 Router1 and Router2 are separated network.

 WANU must control SIP and RTP packets to relay Local and WAN network.
- Refer WANU_Overview.ppt for WANU setting.

Local: 10.10.10.0/24
Internet Router 1
IP: 10.10.10.254

UCP

FW: 4.3.2.1 IP: 10.10.10.2

IP: 10.10.10.10

SIP Trunk VOIMW

Router 2
WAN IP:
ISP
20.20.20.20
IP: 20.20.20.254
FW: 1.2.3.4
default route
static route

Page 40
 Dual Broadband with WANU

 Router IP address of UCP will be WANU local IP.

Page 41
 Dual Broadband with WANU

 Router IP address of VOIM will be WANU local IP.

 Set Firewall IP and Relay Firewall IP.
 Set USE Board IP for SIP

Page 42
SIP Service in T-NET

 SIP Trunk is used in T-NET configuration.

- LM VOIU/VOIM is controlled by CM Server.
- After connection, REGISTER will be sent to server by CM server.

CM
Server ISP - SIP Trunk
REGISTER, INVITE, OPTIONS …

LM
SIP
Server
RTP
2017. 10. 13
|
SIP Service in T-NET

 SIP Trunk is used in T-NET configuration.

- LM VOIU/VOIM is controlled by LM Server by disconnection.
- After disconnection, REGISTER will be sent to server by LM server.

CM
Server ISP - SIP Trunk

REGISTER, INVITE, OPTIONS …

LM
SIP
Server
RTP
2017. 10. 13
|
 Network Configuration

 Check if F/W device is installed and where F/W device is located.

- (1) Server is located outside of F/W - F/W IP must be used or SIP ALG feature is needed in F/W
.
- (2) Server is located inside of F/W or connected using public IP – Local IP must be used.

(1)
ISP - SIP
Trunk

(2)
ISP - SIP
Trunk

Page 45
 Network Configuration

 Server is located outside of F/W

- Is SIP ALG feature used in F/W device?
- If SIP ALG feature malfunctions, mute problem happens.
- SIP ALG must change ip address in SIP message – contact, via, media ip
address.
- SIP ALG must relay SIP message and RTP packets.

UCP:10.10.10.2 FW:150.150.150.95

ISP - SIP
Trunk

SIP ALG has own Table to

forward packet and change IP
address

Page 46
 Network Configuration

 Server is located outside of F/W

- Is it possible to disable SIP ALG feature?
- Some F/W can not disable SIP ALG feature.
- Is it possible to set Port Forwarding?

VOIM:10.10.10.1
0

FW:150.150.150.95

ISP - SIP
Trunk
UCP:10.10.10.2

Local IP:port Public IP:port

10.10.10.2:5060 150.150.150.95:5060 SIP signaling port

10.10.10.10:10000 150.150.150.95:10000
~10048 ~10048
RTP port

Port forwarding Table

Page 47
 Trace

Page 48
 Trae

Page 49
 Trace

Page 50
 SIP Registration Log

 Maintenance – Trace – SIP RegUnreg Log View.

- SENDFAIL(6) : No Response from server for REGISTER message.
- Check network problem or server side.
- FAIL(6) – 404 : “404 Not Found” from server for REGISTER message.
- Check ID and password with server.
- REG(5) : “200OK” from server for REGISTER message.
- System is successfully registered.

Page 51
 SIP Registration Log

 If you see the below case, we can say that network or server is unstable in that time.
- SENDFAIL(7)
- FAIL(7)
- REG(5)
…

Reg
1: TERMINATED
2: REGISTERING
Reg Fail
3: REDIRECTED
4: UNAUTHENTICATED
Reg
5: REGISTERED
6: FAILED Reg Fail
7: SEND_FAILURE
Reg

Page 52
 SIP Authentication Log

 Maintenance – Trace – SIP Auth Log View.

- Data Time IP SIP_Method
ID
- 22 Sep 2017 17:20:00 IP:66.23.129.253 ID:0709235149 INVITE
- 22 Sep 2017 17:21:16 IP:103.26.173.4 ID:0734560650 INVITE
 If there are many logs from unknown Ips, consider hacking trial.
- For more information for security, refer security session.

Page 53
 SIP call disconnection after 30 seconds

 SIP stack will disconnect incoming call if final ACK is not received.
- This kind of problem is related with Contact IP address in 200OK contact
header.
 Check which ip address must be used in your configuration.

Contact Header Rule

PGM132-USE PGM132-Firewall PGM133-Firewall PGM102-Firewall
Board IP for SIP IP Address(VOIM) IP Apply IP Address Contact IP Address

Dual O O O Don’t care VOIM Firewall IP

Broadband
case O Other Cases VOIM Local IP

Normal firewall X Don’t care O O UCP Firewall IP

case
X Other Cases UCP Local IP

Page 54
 SIP call disconnection after 30 seconds

 UCP IP is 10.180.240.220 and VOIM IP is 10.180.240.228.

 Customer set PGM132 – USE Board IP for SIP for VOIM (Turn off USE Board IP)
 Contact IP has VOIM Local IP.

Page 55
 SIP call has one-way mute problem.

 When SIP ALG feature is set in F/W, VOIM Local IP can be used.
 When Port Forwarding rule is used, VOIM Firewall IP must be used.
 If user has mute problem even RTP IP is right, Wireshark trace in front of UCP and
VOIM will be helpful to find error.
- Sometimes F/W device blocks RTP packet from server side.

SDP IP rule
PGM132-Firewall PGM133-Firewall
IP Address(VOIM) IP Apply SDP IP Address

O O VOIM Firewall IP

Don’t care X VOIM Local IP

Page 56