Upload
lavada
View
44
Download
0
Embed Size (px)
DESCRIPTION
SIP IOT program. 2008 Mar 13 th ~ 14 th. Panasonic Communications Co.,Ltd Office Network Company Network SE Team. 【SIP IOT】SIP Interoperability Testing. ■ Background : - PowerPoint PPT Presentation
Citation preview
SIP IOT program
Panasonic Communications Co.,Ltd
Office Network Company
Network SE Team
2008 Mar 13th ~ 14th
【【 SIP IOTSIP IOT 】】 SIP Interoperability SIP Interoperability TestingTesting
■ ■ Background Background :: SIP is different from ISDN or other telephone network interface.SIP is different from ISDN or other telephone network interface.
There is no Type Approval Organization. There is no Type Approval Organization. In most cases the Providers does not give us their specification. In most cases the Providers does not give us their specification. There are some specifications like RFC3261 but they are “Request For There are some specifications like RFC3261 but they are “Request For Comment”. The literature is ambiguous and manufactures take it with their own Comment”. The literature is ambiguous and manufactures take it with their own interpretation.interpretation.
(( This is the reason that people say SIP has a dialect.This is the reason that people say SIP has a dialect. ) )
■ ■ Purpose of this testing Purpose of this testing :: To check TDE/TDA is perfectly match to the provider or not.To check TDE/TDA is perfectly match to the provider or not.
To check the restrictions. To check the restrictions.
■ ■ Purpose of this training Purpose of this training :: Learning the test items (call procedures).Learning the test items (call procedures).
Learning the checking points.Learning the checking points.
- Provider choice!Find out a good partner (provider).Getting 2 accounts for interoperability testing.
- Account is usable?PCC check the account and reply to Sales Company with TDE/TDA config. (( Actually it takes about 3 days now.)Actually it takes about 3 days now.)
- Start SIP IOT!Sales Company start SIP IOT.Sales Company send the report and captured data.
- AnalysisPCC analyses the SIP IOT result and reply to Sales Company FT is available or not.
- Start FT!Sales Company start Field Trial for 10 working days.Inquiring to the dealer and customer the usability.
- Final Decision! When you have a confident, start sales!
【【 SIP IOT procedureSIP IOT procedure 】】
Open SIP account
SIP Interoperability Testing
1-day check by PCC
Field Trial at the end user.
PCC checks the data
Approve ?
Blue: PCC, Purple: Sales Company
Please feed back the report to PCC
【【 Testing EnvirmentTesting Envirment 】】
PSTN
ISP/ITSP
SIP PhoneSIP Phone
WiresharkWiresharkWiresharkWireshark
TelecomTelecom
FAXFAX
SLTSLT
MobileMobile
L2 SwitchL2 Switch L2 SwitchL2 Switch
FAXFAX
Equipments ListEquipments List
2 DSL Lines : DSL line x2 + 2 accountsTDE : TDE with 2 PTsSIP phone : PCC recommend Snom300 or 320
Router x2 : It depends on provider. If there is no recommendation from the provider then PCC recommend Cisco1800 or Cisco800 for Router 2 too.
L2 Switch x2 : Port mirroring function is mandatory PCC recommend HP1800
PC x2 : Wireshark should be installedFAX : G3
RouterRouterRouterRouter
Account infoAccount info
VAD: Voice Activity Detection If it work correctly then voice packet traffic become reduced so it is good.But it rarely cause a trouble. Bad voice quality or call cut off.
STUN / SBC.Please refer the “Programming Manual for SIP”.
Management site: It is used for checking the charge or choosing the phone services.CLIP: Calling Line Identification PresentationCLIR: Calling Line Identification RestrictionStar code is a special code which provider support.In case of Bellshare (German provider) *67 is used for CLIR.When you call *67+area code + phone number then it become a CLIR call.
There are other way to stop Caller ID sending if provider support. Logging into the provider web site (using 05) and CLIP off.(Some provider permit user to change some setting on their management site.)
[ITSP Essential information]
1 Provider name
2 Provider type ISP or Carrier
3 Type of the network Closed / Open4 Provider URI http:// 5 Management site http://
> Login ID
> Login Password
6 Address (Country)
7 Area code
8 The method of an international call
[Service interface functionalities]
10 CLIP* Support
11 CLIR* Support
Star Code for CLIP/CLIR
WEB setting
12 FAX relay (T.38) Support
13 DTMF (RFC2833) Support
14 Hold Support
15 Transfer Support
16 Conference Support
17 DDI Support
18 VAD* Support
19 STUN Support
> If yes then Server name
20 SBC (Session Border Controller) Support
[SIP Telephone Settings Essential information] <Server Settings>
30 Proxy Server <compulsory>
31 Proxy Server port
32 Registrar Server
33 Domain Name
<Account Settings 1>
40-1 SIP Account <compulsory>
41-1 Authentication ID <compulsory>
42-1 Authentication Password <compulsory>
43-1 Incoming Number <compulsory>
44-1 DDI Number
<Account Settings 2>
40-2 SIP Account <compulsory>
41-2 Authentication ID <compulsory>
42-2 Authentication Password <compulsory>
43-2 Incoming Number <compulsory>
44-2 DDI Number <Codec Settings> 50 Codec 51 Packet Interval 52 VAD 53 DTMF relay
*NAT Traversal type*NAT Traversal type
SIP Service Provider
SIP Server STUN Server
SIP Service Provider
SIP Server
SIP Service Provider
SBC
SIP Server
*NAT: Network Address Translation
*SBC: Session Boarder Controller
STUN Method Fixed Global IP address Method SBC* Method
TDE
NAT Router
Local Area Network
MediaServer
ProxyServer
SIP PhoneSIP Phone
WiresharkWireshark
L2 SwitchL2 Switch L2 SwitchL2 Switch
TDETDE
RouterRouterRouterRouter
192.168.2.9192.168.2.10
217.10.79.23 217.10.68.75 Media Server217.10.68.75
TDE (DSP)192.168.2.10
Proxy Server217.10.79.23
TDE (MPR)192.168.2.9
SBC
* SBC: Session Border Controller
61.199.255.PCC
DSL modemDSL modem
SBC (Nat Off) method
SBC (Nat Off) method: outgoing call
INVITE Request
192.168.2.9 : 35060 -> 217.10.79.23:5060
INVITE Request
61.199.255.PCC:32844 -> 217.10.79.23:5060
180 Ringing Response
192.168.2.9 : 35060 <- 217.10.79.23::5060
180 Ringing Response
61.199.255.PCC:32844 <- 217.10.79.23:5060
RTP
61.199.255.PCC:33436 <- 217.10.68.75:59876
TDE
MPR : 192.168.2.9DSP : 192.168.2.10
200 OK Response
192.168.2.9 : 35060 <- 217.10.79.23:5060
200 OK Response
61.199.255.PCC:32844 <- 217.10.79.23:5060
RTP
61.199.255.PCC:12128 <- 217.10.68.75:59876
RTP
192.168.2.10 : 12128 <- 217.10.68.75:59876
RTP
192.168.2.10 : 12128 -> 217.10.68.75:59876
RTP
61.199.255.PCC:33436 -> 217.10.68.75:59876
BYE Request
61.199.255.PCC:32844 <- 8217.10.79.23:5060
BYE Request
192.168.2.9 : 35060 <- 217.10.79.23:5060
NAT Table (NAPT Enable)
Inside local Inside global Outside global Timeout
192.168.2.9:35060 61.199.255.PCC:32844 217.10.79.23:5060 300s
192.168.2.10:12128 61.199.255.PCC:33436 217.10.68.75:59876 300s
Global IP : 61.199.255.PCC
NAPT
NAPT
NAT Router
LAN
side
WAN
side
SIP Server
Media Server
217.10.79.23 217.10.68.75
SBC
Default interval time is 20s
Register Request
192.168.2.9 : 35060 -> 217.10.79.23:5060
NAT Table (NAPT Enable)
Inside local Inside global Outside global Timeout
192.168.2.9:35060 61.199.255.PCC:32844 217.10.79.23:5060 300s
192.168.2.10:12130 61.199.255.PCC:33099 217.10.68.75:47620 300s
Register Request
61.199.255.PCC:32844 -> 217.10.79.23:5060
200 OK Response
192.168.2.9 : 35060 <- 217.10.79.23:5060
200 OK Response
61.199.255.PCC:32844 <- 217.10.79.23:5060
RTP
61.199.255.PCC:33099 <- 217.10.68.75:47620
TDESIP
Server
MPR : 192.168.2.9DSP : 192.168.2.10
INVITE Request
192.168.2.9 : 35060 <- 217.10.79.23:5060
Keep Alive (Blank UDP)
61.199.255.PCC:32844 -> 217.10.79.23:5060
INVITE Request
61.199.255.PCC:32844 <- 217.10.79.23:5060
RTP
192.168.2.10 : 12130 <- 217.10.68.75:47620
RTP
192.168.2.10 : 12130 -> 217.10.68.75:47620
RTP
61.199.255.PCC:33099 -> 217.10.68.75:47620
Media Server
Global IP : 61.199.255.PCC 217.10.79.23 217.10.68.75
Keep Alive (Blank UDP)
192.168.2.9 : 35060 -> 217.10.79.23:5060
200 OK Response
192.168.2.9 : 35060 -> 217.10.79.23:5060
200 OK Response
61.199.255.PCC:32844 -> 217.10.79.23:5060
NAPT
NAPT
NAT Router
LAN
side
WAN
side
SBC
SBC (Nat Off) method: incoming call
STUN method
SNOM phone217.10.68.75
Proxy Server217.10.79.23
TDE192.168.2.9
TDE218.116.146.6
217.10.68.75
STUNServer
ProxyServer
SIP PhoneSIP Phone
WiresharkWireshark
L2 SwitchL2 Switch L2 SwitchL2 Switch
TDETDE
RouterRouterRouterRouter
192.168.2.9192.168.2.10
217.10.79.23
61.199.255.PCC
DSL modemDSL modem
STUN method: Registration
Register Request
192.168.2.9 : 35060 -> 217.10.79.23:5060
NAT Table (NAPT Enable)
Inside local Inside global Outside global Timeout
192.168.2.9:33478 61.199.255.PCC:33791 217.10.79.2:10000 300s
192.168.2.9:35060 61.199.255.PCC:33472 217.10.79.23:5060 300s
Register Request
61.199.255.PCC:33472 -> 217.10.79.23:5060
200 OK Response
192.168.2.9 : 35060 <- 217.10.79.23::5060
200 OK Response
61.199.255.PCC:33472 <- 217.10.79.23:5060
TDESIP
Server
MPR : 192.168.2.9DSP : 192.168.2.10
STUN Server
Global IP : 61.199.255.PCC 217.10.79.23 217.10.79.2
STUN Binding Request
61.199.255.PCC:33791 -> 217.10.79.2:10000
STUN Binding Request
192.168.2.9 : 33478 -> 217.10.79.2:10000
STUN Binding Response
61.199.255.PCC:33791 <- 217.10.79.2:10000
STUN Binding Response
192.168.2.9 : 33478 <- 217.10.79.2:10000
Via: SIP/2.0/UDP 61.199.255.PCC:35060;branch=z9hG4bK00001010;rport
Contact: sip:[email protected]:35060
Contact: <sip:[email protected]:35060>;expires=3600
NAPT
NAT Router
LAN
side
WAN
side
Attribute: MAPPED-ADDRESS
Port: 33791 (Port No. is not used.)
IP: 61.199.255.PCC
Attribute: MAPPED-ADDRESS
Port: 33791 (Port No. is not used.)
IP: 61.199.255.PCC
STUN method: outgoing call
INVITE Request
192.168.2.9 : 35060 -> 217.10.79.23:5060
NAT Router
INVITE Request
61.199.255.PCC:33472 -> 217.10.79.23:5060
180 Ringing Response
192.168.2.9 : 35060 <- 217.10.79.23::5060
180 Ringing Response
61.199.255.PCC:33472 <- 217.10.79.23:5060
RTP
61.199.255.PCC:16000 <- 218.116.146.6:54920
TDE
MPR : 192.168.2.9DSP : 192.168.2.10
200 OK Response
192.168.2.9 : 35060 <- 217.10.79.23:5060
200 OK Response
61.199.255.PCC:33472 <- 217.10.79.23:5060
RTP
192.168.2.10 : 16000 <- 218.116.146.6:54920
RTP
192.168.2.10 : 16000 -> 218.116.146.6:54920
RTP
61.199.255.PCC:16000 -> 218.116.146.6:54920
BYE Request
61.199.255.PCC:35060 -> 217.10.79.23:5060
BYE Request
192.168.2.9 : 35060 -> 217.10.79.23:5060
LAN
side
WAN
side Global IP : 61.199.255.PCC
Port forward
SIP : 35060
RTP : ~16063 (Max)
NAT Table (NAPT Enable)Inside local Inside global Outside global Timeout
192.168.2.9:35060 61.199.255.PCC:35060 any or Server IP ----------
192.168.2.10:16000 61.199.255.PCC:16000 any ----------
192.168.2.9:35060 61.199.255.PCC:33472 217.10.79.23:5060 300s
NAPT
Port Forward by Router
Port Forward by Router
NAPT
SIP Server
SNOM phone
217.10.79.23 218.116.146.6
INVITE Request
192.168.2.9 : 35060 <- 217.10.79.23:5060
INVITE Request
61.199.255.PCC:35060 <- 217.10.79.23:5060
180 Ringing Response
192.168.2.9 : 35060 -> 217.10.79.23:5060
180 Ringing Response
61.199.255.PCC:35060 -> 217.10.79.23:5060
RTP
61.199.255.PCC:16000 -> 218.116.146.6:55134
TDESIP
Server
MPR : 192.168.2.9DSP : 192.168.2.10
200 OK Response
192.168.2.9 : 35060 -> 217.10.79.23:5060
200 OK Response
61.199.255.PCC:35060 -> 217.10.79.23:5060
RTP
192.168.2.10 : 16000 -> 218.116.146.6:55134
RTP
192.168.2.10 : 16000 -> 218.116.146.6:55134
RTP
61.199.255.PCC:16000 -> 218.116.146.6:55134
BYE Request
61.199.255.PCC:35060 -> 217.10.79.23:5060
SNOM phone
BYE Request
192.168.2.9 : 35060 -> 217.10.79.23:5060
NAT Table (NAPT Enable)
Inside local Inside global Outside global Timeout
192.168.2.9:35060 61.199.255.PCC:35060 any ----------
192.168.2.10:16000 61.199.255.PCC:16000 any ----------
Global IP : 61.199.255.PCC 217.10.79.23
Port forward
SIP : 35060
RTP : ~16063 (Max)
Port Forward by Router
Port Forward by Router
Port Forward by Router
NAT Router
LAN
side
WAN
side 218.116.146.6
STUN method: incoming call