Technical Communication 1201 Norphonic emergency rugged telephone on Alcatel-Lucent OmniPCX Enterprise
|
|
|
- Rudolf Booth
- 10 years ago
- Views:
Transcription
1 Technical Communication 1201 Norphonic emergency rugged telephone on Alcatel-Lucent OmniPCX Enterprise This document describes configuration procedure for your Alcatel-Lucent OmniPCX Enterprise PBX in order to operate with the Norphonic Emergency phones. Detailed description is provided to assist engineers in configuring Alcatel-Lucent OmniPCX Enterprise and the Norphonic Emergency Telephones. The configuration is done and tested in lab, using OmniPCX Enterprise R10, j c and the Norphonic Emergency Rugged Telephone V8. The procedure requires a minimum knowledge to SIP basics, linux, ftp, and wireshark usage. This document includes SIP traces with successful communications for engineers to compare with on-site traces. The on-site network must provide the Norphonic Phones with IP address and TFTP server providing configuration files. Learn more about our innovations at At Norphonic, we produce Heavy Duty VoIP Telephones for emergency and industrial areas. Our vision is based on a unified and consistent approach to delivering products that can interface with other communication systems, thereby reducing costs and eliminating inefficiencies of using proprietary and non-reusable solutions. Norphonic AS Fabrikkgaten 10 N-5059 BERGEN Contact: [email protected] Office: Document: tc1201
2 This publication is a guide for reference only. Reference to local codes and standards for compliance of system design should always be sought. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Norphonic. Please contact Norphonic for further information. The manufacturer reserves the right to change designs or specifications without obligation and without further notice. This document is owned by Norphonic and you agree not to copy, communicate to the public, adapt, distribute, transfer, sell, modify or publish any content of this document without express prior written consent from the owner. Norphonic is a registered company registration number NO Norphonic AS Fabrikkgaten 10 N-5059 Bergen Contact: [email protected] Office:
3 Contents Setting up Alcatel SIP system... 1 Know your environment... 1 Important prerequisites... 1 RTP Direct... 1 GF Diversion on joining must be disabled to ensure correct forwarding of calls Start Configuration... 1 Make sure your SIP Network Number is defined as ABC_F... 1 Create Your SIP Trunk Group. Some options may appear after first validation Configure the virtual access on the trunk... 2 Select Compression Type... 2 Create your SIP gateway... 2 Set your Proxy parameters... 3 Command to restart the Alcatel SIP engine:... 3 Add your SIP user... 3 Setting up Norphonic phone... 3 Tracing sip on Alcatel-Lucent OXE... 4 Trace applications... 4 Using sipdump... 4 Using motortrace... 5 Using tcpdump... 6 Successful SIP registration... 6 Scenario... 6 Trace... 7 Norphonic phone trying register with too brief Expires time... 8 Scenario... 8 Trace... 9 Successful call from Alcatel-Lucent 4028 IP set to Norphonic Phone Scenario Trace Authentication fail due to missing Realm setting in SIP SIP Proxy Scenario Trace Incoming call with Session Timer Too Small Scenario Trace Questions and Answers Q: Norphonic phone is registered but calls are rejected. Call to Norphonic phone is fine Q: The Norphonic Phone registers with the proxy but cannot make calls. Alcatel ISSUES a 502 Bad Gateway message Norphonic AS Fabrikkgaten 10 N-5059 Bergen Contact: [email protected] Office:
4 Q: The Norphonic phone is challenged with a Status: 407 Proxy Authentication Required and call establishment from Norphonic phone is failing Words and abbreviations Disclaimer... Error! Bookmark not defined. Norphonic AS Fabrikkgaten 10 N-5059 Bergen Contact: [email protected] Office:
5 Setting up Alcatel SIP system Know your environment To ensure parameters are set up correctly, please note the following information: Definition Description Value in example $_SIPNetworkNumber Find an unused network number in Translator Network Routing Table $_SIPTrunkGroup A free Trunk Group ID 10 $_OXENodeNumber Locate your Node number in System Node Number $_OXEIPAddress Defined in netadmin installation $_OXEHostname Defined in netadmin installation demo 10 1 The values will be referenced as defined in the first column. Important prerequisites RTP Direct IP > IP Parameters: Direct RTP For H323 Terminals True GF Diversion on joining must be disabled to ensure correct forwarding of calls. System > Other System Param. > External Signaling Parameters: gf diversion on joining False Start Configuration Make sure your SIP Network Number is defined as ABC_F Translator > Network Routing Table: Review/modify [$_SIPNetworkNumber] Protocol Type ABC_F Page 1
6 Create Your SIP Trunk Group. Some options may appear after first validation. Trunk Groups: Create Trunk Group ID Trunk Group Type Remote Network Node Number Q931 Signal variant T2 Specification $_SIPTrunkGroup T2 $_SIPNetworkNumber $_OXENodeNumber ABC_F SIP Configure the virtual access on the trunk Trunk Groups > Trunk Group [$_SIPTrunkGroup] : Review/modify Virtual access for SIP Define an even number of accesses to define how many simultaneous calls needed. Each access provides 30 simultaneous calls. Select Compression Type The selection made here defines the OXE s codec offer to SIP UA. G711 will make OXE offer the uncpmpressed G711 codec on this specific Trunk. Selecting Default points to System Other System Param. - Compression Parameters - Compression Type Trunk groups Trunk Group[$_SIPTrunkGroup] : Review/Modify IP Compression Type Default The Compression Type selected in System Parameters control which codec is used when IP Domain requires use of compression. System > System Parameters > Other system param. > Compression Parameters: Review/Modify Compression Type G 729 Norphonic Phone support G729 compression Create your SIP gateway This defines where Alcatel-Lucent receives and handles SIP proxy functions. SIP SIP Gateway SIP Subnetwork $_SIPSubNetwork SIP Trunk Group $_SIPTrunkGroup IP Address Automatically updated Machine name Host Automatically updated SIP Port number 6060 SIP Proxy Port Number 5060 SIP Subscribe Min Duration 1800 Page 2
7 SIP Subscribe Max Duration SDP in 18x Set True to include Session Description Protocol information in 18x messages (RFC 3261) If your system needs to handle fully qualified domain names (FQDN), add the following information as well: DNS Local domainname SIP DNS1 IP Address SIP DNS2 IP Address Ex.: company_network.lan Address to primary dns Address to secondary dns Set your Proxy parameters SIP SIP Proxy Parameter Value Description Minimal authentication method SIP Digest RFC 2617 with auth qop Authentication realm Anything Norphonic phones will adapt to OXE s request. Field cannot be left empty. Only authenticated incoming calls False Do not require additional Authentication on incoming call TCP when long messages False No TCP at all Command to restart the Alcatel SIP engine: # dhs3_init -R SIPMOTOR Add your SIP user Users Create Directory number Ex.: 4458 Directory name Ex.: Norphonic 58 Set Type SIP URL username Username used for Proxy authentication Ex.: 1158 URL Domain Leave blank SIP Password SIP Proxy authentication password Ex.: secret58 Setting up Norphonic phone Your network must be set up to supply the phones with DHCP addresses and pointing TFTP towards a server supplying the configuration files. The name of the file must be either of [IP-address].cfg or [MAC-address].cfg. I.e.: cfg or 1045BE cfg. Page 3
8 Config file example content: sip_display_name=norphonic 1158 sip_user_name=4458 sip_proxy_server= :5060 proxy_user_name=1158 proxy_domain_name= default_if_name=br0 transport_tcp=0 sip_port=5060 audio_=/dev/dsp audio_frag_size=128 audio_frag_count=4 audio_aec_settings=0x54b0 0x2a82 0x0008 selftest_interval=3600 reregister_interval=1800 srv_auth=1 srv_auth_user_name=1158 srv_auth_realm= srv_auth_passwd=secret58 dial_enabled=1 dial_numbering_schema=:4; dial_domain= Tracing sip on Alcatel-Lucent OXE Trace applications Using sipdump This method print information to terminal window and additional information from OXE s SIP engine is added. Initiate two telnet sessions to the OXE, using your telnet client of choice. After logging in, disable the auto logout mechanism by command: (1)norphonic> timout 0 timout disabled. In the first telnet session, start sipdump: (1)norphonic> sipdump Wed May 9 10:45:11 CEST 2012 SIP Gateway resources menu 1 - Dump the gateway management datas 2 - Dump a call 3 - Display the number of calls 4 - Display the calls-neqt mapping 5 - Display the calls list 6 - Display the detailed calls list 7 - Release a call 8 - Display subscription list Page 4
9 9 - Display calls through a gateway 10 - Display calls in a trunk group 11 - SIP traces filters 12 - Display registred users 13 - Display CPU-SSM connections 0 - Exit Choice [0-13] : In the second telnet session, change to a directory in a partition with more space. (1)norphonic> cd /usr4/backup/immed/ (1)norphonic> Start traced: (1)norphonic> traced In your first telnet session, type 1 in the menu and check for trace information display in the second telnet session: Wed May 9 11:39: [ipc_thread] IPC Thread : TCL thread signaled. Wed May 9 11:39: [exec_ipc] in Wed May 9 11:39: [display_ipc_in] Begin Wed May 9 11:39: neqt : -1 Id : -1 Wed May 9 11:39: RELATIVE REQUEST : SIP_MOTOR_DUMP_REQUEST Wed May 9 11:39: [display_ipc_in] End Wed May 9 11:39: [CMotorCallManager::onIncomingEvent] an event arrived on the eqt Wed May 9 11:39: [onincomingevent] SIP_MOTOR_DUMP_REQUEST arrived. Wed May 9 11:39: [exec_ipc] in end Wed May 9 11:39: Wed May 9 11:39: Gateway Management Datas Wed May 9 11:39: Wed May 9 11:39: Wed May 9 11:39: Use of licences : Yes Wed May 9 11:39: Number of initial licenses : 2 Wed May 9 11:39: Number of available licences : 2 Wed May 9 11:39: Number of initial Tls licenses : 0 Wed May 9 11:39: Number of available Tls licences : 0 Wed May 9 11:39: Wed May 9 11:39: Main server : Yes Wed May 9 11:39: Degraded mode : Yes Wed May 9 11:39: Degraded mode : No Wed May 9 11:39: Trace information will appear in this window. Using motortrace This procedure make sipmotor engine create descriptive logs directly to traced. Initiate a telnet sessions to the OXE, using your telnet client of choice. After logging in, disable the auto logout mechanism by command: (1)norphonic> timout 0 timout disabled. Set sipmotor trace level to 3: (1)norphonic> motortrace 3 motortrace (v5.2.0) verbosity = 0037b524 sipmotor trace-level set 3 (All traces). (1)norphonic> traced ** UNIX-trace-daemon started... (static user group No 1) ** traced started... You may also pipe the output to a file: traced > siptrace01.txt Page 5
10 The traced application is stopped with a common break signal, Ctrl-C. Sipdump may be used in along with motortrace. Using tcpdump This method copies data traffic on the network for the purpose of analyzing with an external application. Initiate a telnet sessions to the OXE, using your telnet client of choice. After logging in, disable the auto logout mechanism by command: (1)norphonic> timout 0 timout disabled. In the telnet session, switch to user root and enter the root password. (default: letacla) (1)norphonic> su - Password: [root@norphonic root]# Again, disable the auto logout mechanism and change to a directory in a partition with more space. [root@norphonic root]# timout 0 timout disabled. [root@norphonic root]# cd /usr4/backup/immed/ [root@norphonic IMMED]# Start a dump of network traffic to and from the IP assigned your Norphonic Emergency phone and save the result to a file. The information is written binary to the.cap file and must be analyzed with wireshark. The wireshark tool is not described here. Refer to for additional information. Description of switches: -s 0 set snaplength to infinite and make tcpdump save the entire content of each tcp package, -w trace01.cap write the captured data to the file trace01.cap, -I eth0 ensure tcpdump capture data on Ethernet interface eth0 and host limit the capture to traffic to and from [root@norphonic IMMED]# tcpdump -s 0 -w trace01.cap -i eth0 host tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size bytes There will be no output in terminal during capture. Break the ongoing capture with a Ctrl-C when capture is considered done. The terminal will answer with statistics of the finished tcpdump job. 11 packets captured 11 packets received by filter 0 packets dropped by kernel [root@norphonic IMMED]# Retrieve the.cap file from /usr4/backup/immed by ftp and open for analyzing with Wireshark. Successful SIP registration Scenario Norphonic Phone at tries to register with Alcatel Lucent OmniPCX Enterprise at in Frame 1. OXE replies a 401 Unauthorized in frame 2 with a request for WWW Digest Auth and qop= auth Norphonic Phone run a new REGISTER message according to RFC 2617 with WWW- Authenticate:Digest and qop= auth. OXE grants the REGISTER with a 200 OK in frame 4. Page 6
11 Trace SIP 509 Request: REGISTER sip: :5060 Frame 1: 509 bytes on wire (4072 bits), 509 bytes captured (4072 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: REGISTER sip: :5060 SIP/ :5060;rport;branch=z9hG4bK1q6b6efb49933a From: <sip:1158@ >;tag= SIP tag: To: <sip:1158@ > Call-ID: 6b6efb49933a6c40@ CSeq: 1 REGISTER Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:1158@ :5060> Contact-URI: sip:1158@ :5060 Max-Forwards: 15 Supported: replaces, timer Expires: SIP 441 Status: 401 Unauthorized (0 bindings) Frame 2: 441 bytes on wire (3528 bits), 441 bytes captured (3528 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Unauthorized WWW-Authenticate: Digest qop="auth",nonce="94f8f57f853b a6b3295c1afe",realm="anything" Authentication Scheme: Digest qop="auth" nonce="94f8f57f853b a6b3295c1afe" realm="anything" To: <sip:1158@ >;tag=882fc470f6408ee8334b64222d9e6e9b SIP tag: 882fc470f6408ee8334b64222d9e6e9b From: <sip:1158@ >;tag= SIP tag: Call-ID: 6b6efb49933a6c40@ CSeq: 1 REGISTER :5060;received= ;rport=5060;branch=z9hG4bK1q6b6efb49933a SIP 736 Request: REGISTER sip: :5060 Frame 3: 736 bytes on wire (5888 bits), 736 bytes captured (5888 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Page 7
12 Request-Line: REGISTER sip: :5060 SIP/ :5060;rport;branch=z9hG4bK2q6b6efb49933a From: SIP tag: To: Call-ID: CSeq: 2 REGISTER Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:1158@ :5060> Contact-URI: sip:1158@ :5060 Authorization: Digest realm="anything", nonce="94f8f57f853b a6b3295c1afe", username="1158", uri="sip: :5060", response="1f4c0ba00b cc4c2bda14", nc= , cnonce=" ", qop=auth, algorithm=md5 Authentication Scheme: Digest realm="anything" nonce="94f8f57f853b a6b3295c1afe" username="1158" uri="sip: :5060" response="1f4c0ba00b cc4c2bda14" nc= cnonce=" " qop=auth algorithm=md5 Max-Forwards: 15 Supported: replaces, timer Expires: SIP 387 Status: 200 OK (1 bindings) Frame 4: 387 bytes on wire (3096 bits), 387 bytes captured (3096 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ OK Contact: <sip:1158@ :5060>;expires=1800 Contact-URI: sip:1158@ :5060 Contact parameter: expires=1800 To: <sip:1158@ >;tag=9ba8b7f306bd4f ac53cb1b SIP tag: 9ba8b7f306bd4f ac53cb1b From: <sip:1158@ >;tag= SIP tag: Call-ID: 6b6efb49933a6c40@ CSeq: 2 REGISTER :5060;received= ;rport=5060;branch=z9hG4bK2q6b6efb49933a Norphonic phone trying register with too brief Expires time Scenario Page 8
13 Norphonic Phone issues a REGISTER request in frame 1 and get challenged with authentication in frame 2. The Phone REGISTER with Authentication in frame 3 and is informed with Status: 423 Registration Too Brief with information on Min-Expires Norphonic Phone adapts to the requested Expires time and issue a new REGISTER. The OXE grant the registration. Trace SIP 508 Request: REGISTER sip: :5060 Frame 1: 508 bytes on wire (4064 bits), 508 bytes captured (4064 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: REGISTER sip: :5060 SIP/ :5060;rport;branch=z9hG4bK1q292adec5c73f From: <sip:1158@ >;tag= SIP tag: To: <sip:1158@ > Call-ID: 292adec5c73f723b@ CSeq: 1 REGISTER Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:1158@ :5060> Contact-URI: sip:1158@ :5060 Max-Forwards: 15 Supported: replaces, timer Expires: SIP 441 Status: 401 Unauthorized (0 bindings) Frame 2: 441 bytes on wire (3528 bits), 441 bytes captured (3528 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Unauthorized WWW-Authenticate: Digest qop="auth",nonce="94f8f57f853b a6b3295c1afe",realm="anything" Authentication Scheme: Digest qop="auth" nonce="94f8f57f853b a6b3295c1afe" realm="anything" To: <sip:1158@ >;tag=3e5740a69ea d cbcdd3 SIP tag: 3e5740a69ea d cbcdd3 From: <sip:1158@ >;tag= SIP tag: Call-ID: 292adec5c73f723b@ CSeq: 1 REGISTER :5060;received= ;rport=5060;branch=z9hG4bK1q292adec5c73f Page 9
14 SIP 735 Request: REGISTER sip: :5060 Frame 3: 735 bytes on wire (5880 bits), 735 bytes captured (5880 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: REGISTER sip: :5060 SIP/ :5060;rport;branch=z9hG4bK2q292adec5c73f From: SIP tag: To: Call-ID: CSeq: 2 REGISTER Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:1158@ :5060> Contact-URI: sip:1158@ :5060 Authorization: Digest realm="anything", nonce="94f8f57f853b a6b3295c1afe", username="1158", uri="sip: :5060", response="7b cbf0e5b39f707869ea29f58", nc= , cnonce=" ", qop=auth, algorithm=md5 Authentication Scheme: Digest realm="anything" nonce="94f8f57f853b a6b3295c1afe" username="1158" uri="sip: :5060" response="7b cbf0e5b39f707869ea29f58" nc= cnonce=" " qop=auth algorithm=md5 Max-Forwards: 15 Supported: replaces, timer Expires: SIP 375 Status: 423 Registration Too Brief (0 bindings) Frame 4: 375 bytes on wire (3000 bits), 375 bytes captured (3000 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Registration Too Brief Min-Expires: 1800 To: <sip:1158@ >;tag=1ee22a867aa7d60ed765680ced32f3fa SIP tag: 1ee22a867aa7d60ed765680ced32f3fa From: <sip:1158@ >;tag= SIP tag: Call-ID: 292adec5c73f723b@ CSeq: 2 REGISTER :5060;received= ;rport=5060;branch=z9hG4bK2q292adec5c73f SIP 736 Request: REGISTER sip: :5060 Frame 5: 736 bytes on wire (5888 bits), 736 bytes captured (5888 bits) Page 10
15 Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: REGISTER sip: :5060 SIP/ :5060;rport;branch=z9hG4bK3q292adec5c73f From: SIP tag: To: Call-ID: CSeq: 3 REGISTER Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:1158@ :5060> Contact-URI: sip:1158@ :5060 Authorization: Digest realm="anything", nonce="94f8f57f853b a6b3295c1afe", username="1158", uri="sip: :5060", response="7b cbf0e5b39f707869ea29f58", nc= , cnonce=" ", qop=auth, algorithm=md5 Authentication Scheme: Digest realm="anything" nonce="94f8f57f853b a6b3295c1afe" username="1158" uri="sip: :5060" response="7b cbf0e5b39f707869ea29f58" nc= cnonce=" " qop=auth algorithm=md5 Max-Forwards: 15 Supported: replaces, timer Expires: SIP 387 Status: 200 OK (1 bindings) Frame 6: 387 bytes on wire (3096 bits), 387 bytes captured (3096 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ OK Contact: <sip:1158@ :5060>;expires=1800 Contact-URI: sip:1158@ :5060 Contact parameter: expires=1800 To: <sip:1158@ >;tag=c5610ebf523976ff d6761bc0a SIP tag: c5610ebf523976ff d6761bc0a From: <sip:1158@ >;tag= SIP tag: Call-ID: 292adec5c73f723b@ CSeq: 3 REGISTER :5060;received= ;rport=5060;branch=z9hG4bK3q292adec5c73f Page 11
16 Successful call from Alcatel-Lucent 4028 IP set to Norphonic Phone Scenario IP Touch 4028 Invite Norphonic phone for session and offer PCMA/8000 codec in frame 1. This is equivalent to G711 alaw The Norphonic Phone issue a 100 Trying, a 180 Ringing and a 200 Call accepted in frames 2, 3 and 4. IP Touch 4028 replies with a ACK as the communication is set up in frame 5. The call is ended with a Request: BYE from the IP Touch 4028 and a 200 OK from the Norphonic Phone. Trace SIP/SDP 905 Request: INVITE sip:1158@ :5060, with session description Frame 1: 905 bytes on wire (7240 bits), 905 bytes captured (7240 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Request-Line: INVITE sip:1158@ :5060 SIP/2.0 Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO Supported: histinfo,replaces,timer,path User-Agent: OmniPCX Enterprise R10.0 j Session-Expires: 1800;refresher=uac Min-SE: 900 Content-Type: application/sdp To: <sip:1158@demo;user=phone> From: "Test" <sip:4411@ ;user=phone>;tag=7c3a332f52ceca113222e284f03ffc23 Contact: <sip:4411@ ;transport=udp> Call-ID: defc62d15c8dfe2aea97473e7a888ac6@ CSeq: INVITE ;branch=z9hG4bK46784bbd8eb0148fc10691d9766de172 Max-Forwards: 70 Content-Length: 209 Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): OXE IN IP Session Name (s): abs Connection Information (c): IN IP Time Description, active time (t): 0 0 Media Description, name and address (m): audio RTP/AVP 8 97 Media Attribute (a): sendrecv Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): ptime:20 Media Attribute (a): maxptime:30 Media Attribute (a): rtpmap:97 telephone-event/ SIP 439 Status: 100 Trying... Frame 2: 439 bytes on wire (3512 bits), 439 bytes captured (3512 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Page 12
17 Status-Line: SIP/ Trying :5060;received= ;branch=z9hG4bK46784bbd8eb0148fc10691d9766de172 From: "Test" To: Call-ID: CSeq: INVITE Contact: SIP 453 Status: 180 Ringing... Frame 3: 453 bytes on wire (3624 bits), 453 bytes captured (3624 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Status-Line: SIP/ Ringing :5060;received= ;branch=z9hG4bK46784bbd8eb0148fc10691d9766de172 From: "Test" To: Call-ID: CSeq: INVITE Contact: SIP/SDP 798 Status: 200 Call accepted, with session description Frame 4: 798 bytes on wire (6384 bits), 798 bytes captured (6384 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Status-Line: SIP/ Call accepted :5060;received= ;branch=z9hG4bK46784bbd8eb0148fc10691d9766de172 From: "Test" To: Call-ID: CSeq: INVITE Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: Require: timer Supported: replaces, timer Session-Expires: 900;refresher=uac Content-Type: application/sdp Content-Length: 137 Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): VOCAL IN IP Session Name (s): - Connection Information (c): IN IP Time Description, active time (t): 0 0 Media Description, name and address (m): audio 1260 RTP/AVP 8 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): ptime:184 Page 13
18 SIP 474 Request: ACK Frame 5: 474 bytes on wire (3792 bits), 474 bytes captured (3792 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Request-Line: ACK SIP/2.0 Contact: User-Agent: OmniPCX Enterprise R10.0 j To: From: "Test" Call-ID: CSeq: ACK ;branch=z9hG4bKce6afae5ead76f0b488865f10e1240cd Max-Forwards: SIP 477 Request: BYE sip:1158@ :5060 Frame 6: 477 bytes on wire (3816 bits), 477 bytes captured (3816 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Request-Line: BYE sip:1158@ :5060 SIP/2.0 Supported: replaces,timer,path,100rel User-Agent: OmniPCX Enterprise R10.0 j To: <sip:1158@demo;user=phone>;tag= From: <sip:4411@ ;user=phone>;tag=7c3a332f52ceca113222e284f03ffc23 Call-ID: defc62d15c8dfe2aea97473e7a888ac6@ CSeq: BYE ;branch=z9hG4bKc9da223106eb c2ec36d967f78 Max-Forwards: SIP 435 Status: 200 OK Frame 7: 435 bytes on wire (3480 bits), 435 bytes captured (3480 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Status-Line: SIP/ OK :5060;received= ;branch=z9hG4bKc9da223106eb c2ec36d967f78 From: <sip:4411@ ;user=phone>;tag=7c3a332f52ceca113222e284f03ffc23 To: <sip:1158@demo;user=phone>;tag= Call-ID: defc62d15c8dfe2aea97473e7a888ac6@ CSeq: BYE Contact: <sip:1158@ :5060> Page 14
19 Authentication fail due to missing Realm setting in SIP SIP Proxy Scenario Norphonic Phone at tries to register with Alcatel Lucent OmniPCX Enterprise at in Frame 1. OXE replies a 401 Unauthorized in frame 2 with a request for WWW Digest Auth and qop= auth Norphonic Phone run a new REGISTER message, but uses OXE s IP as realm causing the MD5 hash response to be rendered different than expected by OXE. OXE denies the REGISTER with a new 401 Unauthorized in frame 4 as the password hash do not match. Trace SIP 509 Request: REGISTER sip: :5060 Frame 1: 509 bytes on wire (4072 bits), 509 bytes captured (4072 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: REGISTER sip: :5060 SIP/2.0 Method: REGISTER Request-URI: sip: :5060 [Resent Packet: False] :5060;rport;branch=z9hG4bK1qc19fefe6b2d2 From: <sip:1158@ >;tag= SIP tag: To: <sip:1158@ > Call-ID: c19fefe6b2d2c562@ CSeq: 1 REGISTER Sequence Number: 1 Method: REGISTER Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:1158@ :5060> Contact-URI: sip:1158@ :5060 Max-Forwards: 15 Supported: replaces, timer Expires: SIP 433 Status: 401 Unauthorized (0 bindings) Frame 2: 433 bytes on wire (3464 bits), 433 bytes captured (3464 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Unauthorized Status-Code: 401 [Resent Packet: False] [Request Frame: 1] [Response Time (ms): 30] Page 15
20 WWW-Authenticate: Digest qop="auth",nonce="94f8f57f853b a6b3295c1afe",realm="" Authentication Scheme: Digest qop="auth" nonce="94f8f57f853b a6b3295c1afe" realm="" To: SIP tag: 9b34cc a5501fcc5fb40d9fd16 From: SIP tag: Call-ID: CSeq: 1 REGISTER Sequence Number: 1 Method: REGISTER :5060;received= ;rport=5060;branch=z9hG4bK1qc19fefe6b2d SIP 737 Request: REGISTER sip: :5060 Frame 3: 737 bytes on wire (5896 bits), 737 bytes captured (5896 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: REGISTER sip: :5060 SIP/2.0 Method: REGISTER Request-URI: sip: :5060 [Resent Packet: False] :5060;rport;branch=z9hG4bK2qc19fefe6b2d2 From: <sip:1158@ >;tag= SIP tag: To: <sip:1158@ > Call-ID: c19fefe6b2d2c562@ CSeq: 2 REGISTER Sequence Number: 2 Method: REGISTER Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:1158@ :5060> Contact-URI: sip:1158@ :5060 Authorization: Digest realm=" ", nonce="94f8f57f853b a6b3295c1afe", username="1158", uri="sip: :5060", response="b53ba4d023460f9e1b13f e3", nc= , cnonce=" ", qop=auth, algorithm=md5 Authentication Scheme: Digest realm=" " nonce="94f8f57f853b a6b3295c1afe" username="1158" uri="sip: :5060" response="b53ba4d023460f9e1b13f e3" nc= cnonce=" " qop=auth algorithm=md5 Max-Forwards: 15 Supported: replaces, timer Expires: SIP 433 Status: 401 Unauthorized (0 bindings) Frame 4: 433 bytes on wire (3464 bits), 433 bytes captured (3464 bits) Page 16
21 Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Unauthorized Status-Code: 401 [Resent Packet: False] [Request Frame: 3] [Response Time (ms): 30] WWW-Authenticate: Digest qop="auth",nonce="94f8f57f853b a6b3295c1afe",realm="" Authentication Scheme: Digest qop="auth" nonce="94f8f57f853b a6b3295c1afe" realm="" To: SIP tag: a645feb43522f3e40d98a4b625a32033 From: SIP tag: Call-ID: CSeq: 2 REGISTER Sequence Number: 2 Method: REGISTER :5060;received= ;rport=5060;branch=z9hG4bK2qc19fefe6b2d2 Incoming call with Session Timer Too Small Scenario Norphonic Phone INVITE in frame 1 IP Touch 4028 to a call and the IP Touch 4028 replies with 100 Trying, and a Status: 422 Session Timer Too Small. In frame 2 and 3. Norphonic Phone acknowledges the request in frame 4 and sends a new INVITE with adjusted Session- Expires adjusted to OXE s request in frame 5. The IP Touch 4028 replies with 100 trying, 180 Ringing and a 200 OK in frame 6, 7 and 8. The Norphonic phone send an ACK and communication is up in frame 9. The call is ended by a Request: BYE from IP Touch 4028 and a 200 OK in frame 10 and 11. Trace SIP/SDP 788 Request: INVITE sip:4411@ :5060;user=phone, with session description Frame 1: 788 bytes on wire (6304 bits), 788 bytes captured (6304 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: INVITE sip:4411@ :5060;user=phone SIP/ :5060;rport;branch=z9hG4bK1qc241830a232d From: 4458 <sip:4458@ >;tag= To: <sip:4411@ > Call-ID: c241830a232d8885@ CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:4458@ :5060> Page 17
22 Max-Forwards: 15 Supported: replaces, timer Session-Expires: 900 Min-SE: 90 Content-Type: application/sdp Content-Length: 208 Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): VOCAL IN IP Session Name (s): - Connection Information (c): IN IP Time Description, active time (t): 0 0 Media Description, name and address (m): audio 1274 RTP/AVP Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): ptime: SIP 308 Status: 100 Trying Frame 2: 308 bytes on wire (2464 bits), 308 bytes captured (2464 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Trying To: <sip:4411@ > From: 4458 <sip:4458@ >;tag= Call-ID: c241830a232d8885@ CSeq: 1 INVITE :5060;received= ;rport=5060;branch=z9hG4bK1qc241830a232d SIP 507 Status: 422 Session Timer Too Small Frame 3: 507 bytes on wire (4056 bits), 507 bytes captured (4056 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Session Timer Too Small Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE User-Agent: OmniPCX Enterprise R10.0 j Min-SE: 1900 To: <sip:4411@ >;tag=692fe55ef8529a5f390bafc2fb061cf3 From: 4458 <sip:4458@ >;tag= Call-ID: c241830a232d8885@ CSeq: 1 INVITE :5060;received= ;rport=5060;branch=z9hG4bK1qc241830a232d SIP 424 Request: ACK sip:4411@ :5060;user=phone Frame 4: 424 bytes on wire (3392 bits), 424 bytes captured (3392 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Page 18
23 Request-Line: ACK SIP/ :5060;rport;branch=z9hG4bK1qc241830a232d From: 4458 To: Call-ID: CSeq: 1 ACK Contact: <sip:4458@ :5060> Max-Forwards: SIP/SDP 828 Request: INVITE sip:4411@ :5060;user=phone, in-dialog, with session description Frame 5: 828 bytes on wire (6624 bits), 828 bytes captured (6624 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: INVITE sip:4411@ :5060;user=phone SIP/ :5060;rport;branch=z9hG4bK2qc241830a232d From: 4458 <sip:4458@ >;tag= To: <sip:4411@ >;tag=692fe55ef8529a5f390bafc2fb061cf3 Call-ID: c241830a232d8885@ CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE Contact: <sip:4458@ :5060> Max-Forwards: 15 Supported: replaces, timer Session-Expires: 1900 Min-SE: 1900 Content-Type: application/sdp Content-Length: 208 Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): VOCAL IN IP Session Name (s): - Connection Information (c): IN IP Time Description, active time (t): 0 0 Media Description, name and address (m): audio 1274 RTP/AVP Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): ptime: SIP 345 Status: 100 Trying Frame 6: 345 bytes on wire (2760 bits), 345 bytes captured (2760 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Trying To: <sip:4411@ >;tag=692fe55ef8529a5f390bafc2fb061cf3 From: 4458 <sip:4458@ >;tag= Call-ID: c241830a232d8885@ CSeq: 2 INVITE :5060;received= ;rport=5060;branch=z9hG4bK2qc241830a232d Page 19
24 SIP 501 Status: 180 Ringing Frame 7: 501 bytes on wire (4008 bits), 501 bytes captured (4008 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ Ringing Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE Contact: sip: User-Agent: OmniPCX Enterprise R10.0 j To: From: 4458 Call-ID: CSeq: 2 INVITE :5060;received= ;rport=5060;branch=z9hG4bK2qc241830a232d SIP/SDP 861 Status: 200 OK, with session description Frame 8: 861 bytes on wire (6888 bits), 861 bytes captured (6888 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Status-Line: SIP/ OK Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE Contact: sip: Supported: replaces,timer,path,100rel User-Agent: OmniPCX Enterprise R10.0 j Session-Expires: 1900;refresher=uas P-Asserted-Identity: "Test" <sip:4411@ ;user=phone> Content-Type: application/sdp To: <sip:4411@ >;tag=692fe55ef8529a5f390bafc2fb061cf3 From: 4458 <sip:4458@ >;tag= Call-ID: c241830a232d8885@ CSeq: 2 INVITE :5060;received= ;rport=5060;branch=z9hG4bK2qc241830a232d Content-Length: 195 Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): OXE IN IP Session Name (s): abs Connection Information (c): IN IP Time Description, active time (t): 0 0 Media Description, name and address (m): audio RTP/AVP 18 Media Attribute (a): sendrecv Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): ptime:20 Media Attribute (a): maxptime: SIP 405 Request: ACK sip: Frame 9: 405 bytes on wire (3240 bits), 405 bytes captured (3240 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Request-Line: ACK sip: SIP/2.0 Page 20
25 :5060;rport;branch=z9hG4bK2q2qc241830a232d From: 4458 To: Call-ID: CSeq: 2 ACK Contact: <sip:4458@ :5060> Max-Forwards: SIP 444 Request: BYE sip:4458@ :5060 Frame 10: 444 bytes on wire (3552 bits), 444 bytes captured (3552 bits) Ethernet II, Src: AlcatelB_34:45:d2, Dst: JuniperN_7a:ab:82 Request-Line: BYE sip:4458@ :5060 SIP/2.0 Supported: replaces,timer,path,100rel User-Agent: OmniPCX Enterprise R10.0 j To: sip:4458@ ;tag= From: sip:4411@ ;tag=692fe55ef8529a5f390bafc2fb061cf3 Call-ID: c241830a232d8885@ CSeq: BYE ;branch=z9hG4bKd0ab0c2ddb2dbc16bda5ede284fae56b Max-Forwards: SIP 411 Status: 200 OK Frame 11: 411 bytes on wire (3288 bits), 411 bytes captured (3288 bits) Ethernet II, Src: JuniperN_7a:ab:82, Dst: AlcatelB_34:45:d2 Status-Line: SIP/ OK :5060;received= ;branch=z9hG4bKd0ab0c2ddb2dbc16bda5ede284fae56b From: <sip:4411@ >;tag=692fe55ef8529a5f390bafc2fb061cf3 To: 4458 <sip:4458@ >;tag= Call-ID: c241830a232d8885@ CSeq: BYE Contact: <sip:4458@ :5060> Page 21
26 Questions and Answers Q: Norphonic phone is registered but calls are rejected. Call to Norphonic phone is fine. A: The Alcatel is set up to authenticate all incoming calls. Change SIP SIP Proxy - Only authenticated incoming calls to False. Q: The Norphonic Phone registers with the proxy but cannot make calls. Alcatel ISSUES a 502 Bad Gateway message A: The phone offers both G711 as well as G729 codec choice to OXE. If OXE is set to require Compression for this call due to IP Domain settings and Compression Type is set to G723 in System Parameters, the call is rejected with a 502 Bad Gateway message. Q: The Norphonic phone is challenged with a Status: 407 Proxy Authentication Required and call establishment from Norphonic phone is failing. A: Make sure SIP SIP Proxy parameter Only authenticated incoming calls is set to False. Restart Alcatel SIP Motor engine to ensure proper parameter adaptation. Page 22
27 Words and abbreviations Abbreviation used Explained alaw G711 a-law. Also known as PCMA OXE OmniPCX Enterprise. PBX by Alcatel-Lucent PCMA This is equivalent to G711 a-law PCMU This is equivalent to G711 u-law QOP Quality Of Protection. Ref.: RFC 2617 SIP ulaw G711 u-law. Also known as PCMU Page 23
Application Notes for Configuring SIP Trunking between McLeodUSA SIP Trunking Solution and an Avaya IP Office Telephony Solution 1.
Avaya Solution & Interoperability Test Lab Application Notes for Configuring SIP Trunking between McLeodUSA SIP Trunking Solution and an Avaya IP Office Telephony Solution 1.0 Abstract These Application
SIP Basics. CSG VoIP Workshop. Dennis Baron January 5, 2005. Dennis Baron, January 5, 2005 Page 1. np119
SIP Basics CSG VoIP Workshop Dennis Baron January 5, 2005 Page 1 Outline What is SIP SIP system components SIP messages and responses SIP call flows SDP basics/codecs SIP standards Questions and answers
TECHNICAL SUPPORT NOTE. 3-Way Call Conferencing with Broadsoft - TA900 Series
Page 1 of 6 TECHNICAL SUPPORT NOTE 3-Way Call Conferencing with Broadsoft - TA900 Series Introduction Three way calls are defined as having one active call and having the ability to add a third party into
AGILE SIP TRUNK IP-PBX Connection Manual (Asterisk)
AGILE SIP TRUNK IP-PBX Connection Manual (Asterisk) 1. Login to CID (Customer ID) Login https://manager.agile.ne.jp/login.php USERNAME Password 2. Go to SIP List of SIP TRUNK SIP SIP List Buy SIP Trunk
SIP: Protocol Overview
SIP: Protocol Overview NOTICE 2001 RADVISION Ltd. All intellectual property rights in this publication are owned by RADVISION Ltd. and are protected by United States copyright laws, other applicable copyright
Three-Way Calling using the Conferencing-URI
Three-Way Calling using the Conferencing-URI Introduction With the deployment of VoIP users expect to have the same functionality and features that are available with a landline phone service. This document
Enabling Security Features in Firmware DGW v2.0 June 22, 2011
Enabling Security Features in Firmware DGW v2.0 June 22, 2011 Proprietary 2011 Media5 Corporation Table of Contents Scope... 3 Acronyms and Definitions... 3 Setup Description... 3 Basics of Security Exchanges...
CyberData VoIP V2 Speaker with VoIP Clock Kit Configuration Guide for OmniPCX Enterprise
CyberData VoIP V2 Speaker with VoIP Clock Kit Configuration Guide for OmniPCX Enterprise CyberData Corporation 2555 Garden Road Monterey, CA 93940 T:831-373-2601 F: 831-373-4193 www.cyberdata.net 2 Introduction
Asterisk with Twilio Elastic SIP Trunking Interconnection Guide using Secure Trunking (SRTP/TLS)
Asterisk with Twilio Elastic SIP Trunking Interconnection Guide using Secure Trunking (SRTP/TLS) With the Introduction of Twilio Elastic SIP trunking this guide provides the configuration steps required
SIP Trunking & Peering Operation Guide
SIP Trunking & Peering Operation Guide For Samsung OfficeServ May 07, 2008 doc v2.1.0 Sungwoo Lee Senior Engineer [email protected] OfficeServ Network Lab. Telecommunication Systems Division
SIP: Session Initiation Protocol. Copyright 2005 2008 by Elliot Eichen. All rights reserved.
SIP: Session Initiation Protocol Signaling Protocol Review H323: ITU peer:peer protocol. ISDN (Q.931) signaling stuffed into packets. Can be TCP or UDP. H225: Q931 for call control, RAS to resolve endpoints
Session Initiation Protocol (SIP) 陳 懷 恩 博 士 助 理 教 授 兼 計 算 機 中 心 資 訊 網 路 組 組 長 國 立 宜 蘭 大 學 資 工 系 Email: [email protected] TEL: 03-9357400 # 340
Session Initiation Protocol (SIP) 陳 懷 恩 博 士 助 理 教 授 兼 計 算 機 中 心 資 訊 網 路 組 組 長 國 立 宜 蘭 大 學 資 工 系 Email: [email protected] TEL: 03-9357400 # 340 Outline Session Initiation Protocol SIP Extensions SIP Operation
Session Initiation Protocol and Services
Session Initiation Protocol and Services Harish Gokul Govindaraju School of Electrical Engineering, KTH Royal Institute of Technology, Haninge, Stockholm, Sweden Abstract This paper discusses about the
Mediatrix 4404 Step by Step Configuration Guide June 22, 2011
Mediatrix 4404 Step by Step Configuration Guide June 22, 2011 Proprietary 2011 Media5 Corporation Table of Contents First Steps... 3 Identifying your MAC Address... 3 Identifying your Dynamic IP Address...
Avaya IP Office 4.0 Customer Configuration Guide SIP Trunking Configuration For Use with Cbeyond s BeyondVoice with SIPconnect Service
Avaya IP Office 4.0 Customer Configuration Guide SIP Trunking Configuration For Use with Cbeyond s BeyondVoice with SIPconnect Service Issue 2.2 06/25/2007 Page 1 of 41 Table of contents 1 Introduction...8
SIP ALG - Session Initiated Protocol Applications- Level Gateway
SIP ALG is a parameter that is generally enabled on most commercial router because it helps to resolve NAT related problems. However, this parameter can be very harmful and can actually stop SIP Trunks
SIP Essentials Training
SIP Essentials Training 5 Day Course Lecture & Labs COURSE DESCRIPTION Learn Session Initiation Protocol and important protocols related to SIP implementations. Thoroughly study the SIP protocol through
Grandstream Networks, Inc. GXP2130/2140/2160 Auto-configuration Plug and Play
Grandstream Networks, Inc. GXP2130/2140/2160 Auto-configuration Plug and Play Introduction: This is a technical guide targeted to PBX developers that want to learn the different mechanisms that GXP2130/2140/2160
AV@ANZA Formación en Tecnologías Avanzadas
SISTEMAS DE SEÑALIZACION SIP I & II (@-SIP1&2) Contenido 1. Why SIP? Gain an understanding of why SIP is a valuable protocol despite competing technologies like ISDN, SS7, H.323, MEGACO, SGCP, MGCP, and
Session Initiation Protocol
TECHNICAL OVERVIEW Session Initiation Protocol Author: James Wright, MSc This paper is a technical overview of the Session Initiation Protocol and is designed for IT professionals, managers, and architects
Technical Configuration Notes
MITEL SIPCoE Technical Configuration Notes Configure Inn-Phone SIP Phone for use with MCD SIP CoE NOTICE The information contained in this document is believed to be accurate in all respects but is not
Basic Xten Pro Configuration
Basic Xten Pro Configuration 1. Download and install Xten Lite. 2. Launch the Xten Lite client; click the Menu option just above the number 3 digit on the Xten keypad. 3. Double click on the System Settings
Request for Comments: 4579. August 2006
Network Working Group Request for Comments: 4579 BCP: 119 Category: Best Current Practice A. Johnston Avaya O. Levin Microsoft Corporation August 2006 Status of This Memo Session Initiation Protocol (SIP)
AGILE SIP TRUNK IP- PBX Connection Manual (Asterisk, Trixbox)
AGILE SIP TRUNK IP- PBX Connection Manual (Asterisk, Trixbox) 1. SIP TRUNK SETTINGS 1.1. Login to CID (Customer ID): https://manager.agile.ne.jp/login.php USERNAME Password 1.2. On the left most column
IP Touch 4088 EE/4018 EE SIP Phone installation manual
IP Touch 4088 EE/4018 EE SIP Phone installation manual 8AL90824AAAAed01 October, 2009 Alcatel-Lucent All Rights Reserved Alcatel-Lucent 2009 1. Overview... 3 2. SIP Stand-Alone Mode... 3 2.1. Initializing
Interoperability between IPv4 and IPv6 SIP User Agents
Interoperability between IPv4 and IPv6 SIP User Agents Armin Brunner Head Communication Services Swiss Federal Institute of Technology Zürich [email protected] Sabbatical-Project December 2003,
SIP Trunking Quick Reference Document
SIP Trunking Quick Reference Document Publication Information SAMSUNG TELECOMMUNICATIONS AMERICA reserves the right without prior notice to revise information in this publication for any reason. SAMSUNG
SIP Trunking. Service Guide. www.megapath.com. Learn More: Call us at 877.634.2728.
Service Guide Learn More: Call us at 877.634.2728. www.megapath.com What is MegaPath SIP Trunking? SIP Trunking enables your business to reduce costs and simplify IT management by combining voice and Internet
Integrating a Hitachi IP5000 Wireless IP Phone
November, 2007 Avaya Quick Edition Integrating a Hitachi IP5000 Wireless IP Phone This application note explains how to configure the Hitachi IP5000 wireless IP telephone to connect with Avaya Quick Edition
NTP VoIP Platform: A SIP VoIP Platform and Its Services
NTP VoIP Platform: A SIP VoIP Platform and Its Services Speaker: Dr. Chai-Hien Gan National Chiao Tung University, Taiwan Email: [email protected] Date: 2006/05/02 1 Outline Introduction NTP VoIP
Voice over IP Fundamentals
Voice over IP Fundamentals Duration: 5 Days Course Code: GK3277 Overview: The aim of this course is for delegates to gain essential data networking and Voice over IP (VoIP) knowledge in a single, week-long
Part II. Prof. Ai-Chun Pang Graduate Institute of Networking and Multimedia, Dept. of Comp. Sci. and Info. Engr., National Taiwan University
Session Initiation Protocol oco (SIP) Part II Prof. Ai-Chun Pang Graduate Institute of Networking and Multimedia, Dept. of Comp. Sci. and Info. Engr., National Taiwan University Email: [email protected]
SIP Trunking Manual 05.15. Technical Support Web Site: http://ws1.necii.com (registration is required)
SIP Trunking Manual 05.15 Technical Support Web Site: http://ws1.necii.com (registration is required) This manual has been developed by NEC Unified Solutions, Inc. It is intended for the use of its customers
BroadSoft Partner Configuration Guide
BroadSoft Partner Configuration Guide Grandstream GXW-400X FXS Analog Gateway & HandyTone HT-50X Analog Telephone Adapter April 2007 Document Version 1.1 BroadWorks Guide Copyright Notice Copyright 2007
How To Understand The Purpose Of A Sip Aware Firewall/Alg (Sip) With An Alg (Sip) And An Algen (S Ip) (Alg) (Siph) (Network) (Ip) (Lib
NetVanta Unified Communications Technical Note The Purpose of a SIP-Aware Firewall/ALG Introduction This technical note will explore the purpose of a Session Initiation Protocol (SIP)-aware firewall/application
3.1 SESSION INITIATION PROTOCOL (SIP) OVERVIEW
3.1 SESSION INITIATION PROTOCOL (SIP) OVERVIEW SIP is an application layer protocol that is used for establishing, modifying and terminating multimedia sessions in an Internet Protocol (IP) network. SIP
Avaya Aura SIP Trunking Training
Avaya Aura SIP Trunking Training 5 Day Course Lecture & Demo WHO NEEDS TO ATTEND This class is suited to those who are new to administering Avaya systems and would like to know more about the SIP protocol.
EE4607 Session Initiation Protocol
EE4607 Session Initiation Protocol Michael Barry [email protected] [email protected] Outline of Lecture IP Telephony the need for SIP Session Initiation Protocol Addressing SIP Methods/Responses Functional
Application Notes for IDT Net2Phone SIP Trunking Service with Avaya IP Office 8.1 - Issue 1.0
Avaya Solution & Interoperability Test Lab Application Notes for IDT Net2Phone SIP Trunking Service with Avaya IP Office 8.1 - Issue 1.0 Abstract These Application Notes describe the procedures for configuring
Configuring Alcatel OmniPCX Enterprise with Avaya Meeting Exchange TM Enterprise Edition 5.2 Issue 1.0
Avaya Solution & Interoperability Test Lab Configuring Alcatel OmniPCX Enterprise with Avaya Meeting Exchange TM Enterprise Edition 5.2 Issue 1.0 Abstract These Application Notes present a sample configuration
SIP Trunk 2 IP-PBX User Guide Asterisk. Ver1.0.0 2015/08/01 Ver1.0.3 2015/09/17 Ver1.0.4 2015/10/07 Ver1.0.5 2015/10/15 Ver1.0.
SIP Trunk 2 IP-PBX User Guide Asterisk Ver1.0.0 2015/08/01 Ver1.0.3 2015/09/17 Ver1.0.4 2015/10/07 Ver1.0.5 2015/10/15 Ver1.0.6 2015/10/23 Index 1. SIP Trunk 2 Overview 3 2. Purchase/Settings in Web Portal
NAT TCP SIP ALG Support
The feature allows embedded messages of the Session Initiation Protocol (SIP) passing through a device that is configured with Network Address Translation (NAT) to be translated and encoded back to the
SIP : Session Initiation Protocol
: Session Initiation Protocol EFORT http://www.efort.com (Session Initiation Protocol) as defined in IETF RFC 3261 is a multimedia signaling protocol used for multimedia session establishment, modification
Hacking Trust Relationships of SIP Gateways
Hacking Trust Relationships of SIP Gateways Author : Fatih Özavcı Homepage : gamasec.net/fozavci SIP Project Page : github.com/fozavci/gamasec-sipmodules Version : 0.9 Hacking Trust Relationship Between
Installation and setup guide V 1.0
V o I P G S M G A T E BlueGate SIP 1 Installation and setup guide V 1.0 1. General description 1.1 Technical parametres Dimensions 100 x 130 x 37 mm Weight 850 g Operating position various Operating condition
MITEL SIP CoE. Technical. Configuration Notes. Configure MCD 6.X for use with babytel SIP trunks. SIP CoE 13-4940-00266
MITEL SIP CoE Technical Configuration Notes Configure MCD 6.X for use with babytel SIP trunks SIP CoE 13-4940-00266 NOTICE The information contained in this document is believed to be accurate in all respects
Ecessa Proxy VoIP Manual
Ecessa Proxy VoIP Manual Table of Contents Introduction...1 Configuration Overview...2 VoIP failover requirements...2 Import VoIP Authentication...3 Add a user manually...3 Setup...3 Hosted setup...3 Example
IP Office 4.2 SIP Trunking Configuration Guide AT&T Flexible Reach and AT&T Flexible Reach with Business in a Box (SM)
IP Office 4.2 SIP Trunking Configuration Guide AT&T Flexible Reach and AT&T Flexible Reach with Business in a Box (SM) Issue 1.0 (8 th October 2008) 2008 Avaya Inc. All Rights Reserved. Notice While reasonable
VoIP Fundamentals. SIP In Depth
VoIP Fundamentals SIP In Depth 9 Rationale SIP dominant intercarrier and carrier-to-customer protocol Good understanding of its basic operation can help rapidly resolve problems. 10 VoIP Call Control &
Voice over IP & Other Multimedia Protocols. SIP: Session Initiation Protocol. IETF service vision. Advanced Networking
Advanced Networking Voice over IP & Other Multimedia Protocols Renato Lo Cigno SIP: Session Initiation Protocol Defined by IETF RFC 2543 (first release march 1999) many other RFCs... see IETF site and
For internal circulation of BSNL only
E1-E2 E2 CFA Session Initiation Protocol AGENDA Introduction to SIP Functions of SIP Components of SIP SIP Protocol Operation Basic SIP Operation Introduction to SIP SIP (Session Initiation Protocol) is
White paper. SIP An introduction
White paper An introduction Table of contents 1 Introducing 3 2 How does it work? 3 3 Inside a normal call 4 4 DTMF sending commands in sip calls 6 5 Complex environments and higher security 6 6 Summary
Configuring the Cisco SPA8800 IP Telephony Gateway in an Asterisk Environment
Application Note Revised June 10 th 2009 Configuring the Cisco SPA8800 IP Telephony Gateway in an Asterisk Environment 2009 Cisco Systems, Inc. All rights reserved. Page 1 of 69 Table of Contents Introduction
nexvortex Setup Template
nexvortex Setup Template ZULTYS, INC. April 2013 5 1 0 S P R I N G S T R E E T H E R N D O N V A 2 0 1 7 0 + 1 8 5 5. 6 3 9. 8 8 8 8 Introduction This document is intended only for nexvortex customers
DPH-140S SIP Phone Quick User Guide
DPH-140S SIP Phone Quick User Guide Version 1.0 TABLE OF CONTENTS 1.0 INTRODUCTION... 1 2.0 PACKAGE CONTENT... 1 3.0 LIST OF FIGURES... 2 4.0 SUMMARY OF KEY FUNCTIONS... 3 5.0 CONNECTING THE IP PHONE...
IP Touch 4008/4018 Extended Edition
IP Touch 4008/4018 Extended Edition SIP Phone Installation Guide 8AL90824AAAA ed02 August, 2010 Alcatel-Lucent All Rights Reserved Alcatel-Lucent 2010 1. Overview...3 2. Connecting the Alcatel-Lucent IP
Configuring for Integra Telecom SIP Solutions
February 2013 Configuring for Integra Telecom SIP Solutions Section Title Page Background 1 Table 1 Software & Firmware Versions Tested 1 Figure 1 Generic IP PBX Test Configuration (with Transparent SIP
Time Warner ITSP Setup Guide
October 14 Time Warner ITSP Setup Guide Author: Zultys Technical Support This configuration guide was created to assist knowledgeable vendors with configuring the Zultys MX Phone System with Time Warner
Storming SIP Security Captions
Storming SIP Security Captions Listing 1. Running svwar with default options on the target Asterisk PBX./svwar.py 192.168.1.107 Extension Authentication ------------------------------ 502 reqauth 503 reqauth
Media Gateway Controller RTP
1 Softswitch Architecture Interdomain protocols Application Server Media Gateway Controller SIP, Parlay, Jain Application specific Application Server Media Gateway Controller Signaling Gateway Sigtran
Configuration Guide for connecting the Eircom Advantage 4800/1500/1200 PBXs to the Eircom SIP Voice platform.
Configuration Guide for connecting the Eircom Advantage 4800/1500/1200 PBXs to the Eircom SIP Voice platform. 1 Contents Introduction.... 3 Installing the Applications Module... 4 Ordering a Licence for
Application Notes for Level 3 Enterprise IP Trunking Service with an Avaya IP Telephony Network - Issue 1.0
Avaya Solution & Interoperability Test Lab Application Notes for Level 3 Enterprise IP Trunking Service with an Avaya IP Telephony Network - Issue 1.0 Abstract These Application Notes describe the steps
SIP Trunking using Optimum Business SIP Trunk Adaptor and the Cisco Call Manager Express Version 8.5
CISCO SIP Trunking using Optimum Business SIP Trunk Adaptor and the Cisco Call Manager Express Version 8.5 Goal The purpose of this configuration guide is to describe the steps needed to configure the
Troubleshooting Procedures for Cisco TelePresence Video Communication Server
Troubleshooting Procedures for Cisco TelePresence Video Communication Server Reference Guide Cisco VCS X7.2 D14889.01 September 2011 Contents Contents Introduction... 3 Alarms... 3 VCS logs... 4 Event
Technical Configuration Notes
MITEL SIP CoE Technical Configuration Notes Configure MCD for use with OpenIP SIP Trunking service SIP CoE 11-4940-00186 NOTICE The information contained in this document is believed to be accurate in
BROADWORKS SIP ACCESS SIDE EXTENSIONS INTERFACE SPECIFICATIONS RELEASE 13.0. Version 1
BROADWORKS SIP ACCESS SIDE EXTENSIONS INTERFACE SPECIFICATIONS RELEASE 13.0 Version 1 BroadWorks Guide Copyright Notice Trademarks Copyright 2005 BroadSoft, Inc. All rights reserved. Any technical documentation
How To Send A Connection From A Proxy To A User Agent Server On A Web Browser On A Pc Or Mac Or Ipad (For A Mac) On A Network With A Webmail Web Browser (For Ipad) On An Ipad Or
About this Tutorial SIP is a signalling protocol designed to create, modify, and terminate a multimedia session over the Internet Protocol. It is an application layer protocol that incorporates many elements
MITEL SIP CoE. Technical. Configuration Notes. Configure the Mitel 3300 MCD 4.1 for use with Paetec Broadworks Softswitch. SIP CoE 08-4940-00035
MITEL SIP CoE Technical Configuration Notes Configure the Mitel 3300 MCD 4.1 for use with Broadworks Softswitch SIP CoE 08-4940-00035 NOTICE The information contained in this document is believed to be
Background 1 Table 1 Software & Firmware Versions Tested 1 Figure 1 Integra s Universal Access (UA) IP PBX Test Configuration 1
1 Background 1 Table 1 Software & Firmware Versions Tested 1 Figure 1 Integra s Universal Access (UA) IP PBX Test Configuration 1 Configuration Data 2 Section 1: Initial IPitomy IP PBX Connection & Login
Transbox. User Manual
Transbox User Manual Content 1. INTRODUCTION... 1 2. FUNCTIONS... 1 3. THE CONTENTS IN PACKAGE... 2 4. DIMENSION AND PANEL DESCRIPTION... 3 5. ACCESSORY ATTACHMENT... 3 6. SETTING AND MANAGING VIA WEB
P160S SIP Phone Quick User Guide
P160S SIP Phone Quick User Guide Version 2.2 TABLE OF CONTENTS 1.0 INTRODUCTION... 1 2.0 PACKAGE CONTENT... 1 3.0 LIST OF FIGURES... 2 4.0 SUMMARY OF KEY FUNCTIONS... 3 5.0 CONNECTING THE IP PHONE... 4
Alcatel Polycom Video Telephony: IP Touch Instant Video Solution Deployment Guide Phase 1
Alcatel Polycom Video Telephony: IP Touch Instant Video Solution Deployment Guide Phase 1 Copyright 2006 Polycom, Inc. All Rights Reserved Catalog No. DOC2332A Version 1.0 Proprietary and Confidential
nexvortex Setup Guide
nexvortex Setup Guide CUDATEL COMMUNICATION SERVER September 2012 510 S P R I N G S T R E E T H E R N D O N V A 2 0 1 7 0 + 1 8 5 5. 6 3 9. 8 8 8 8 Introduction This document is intended only for nexvortex
Technical Configuration Notes
MITEL SIPCoE Technical Configuration Notes Configure the MCD 6.0 for use with the Commend SIP Doorphone SIP CoE 13-4940-00251 NOTICE The information contained in this document is believed to be accurate
SIP - QUICK GUIDE SESSION INITIATION PROTOCOL - INTRODUCTION
SIP - QUICK GUIDE http://www.tutorialspoint.com/session_initiation_protocol/session_initiation_protocol_quick_guide.htm SESSION INITIATION PROTOCOL - INTRODUCTION Copyright tutorialspoint.com Session Initiation
Troubleshooting Tools to Diagnose or Report a Problem February 23, 2012
Troubleshooting Tools to Diagnose or Report a Problem February 23, 2012 Proprietary 2012 Media5 Corporation Scope of this Document This Technical Bulletin aims to inform the reader on the troubleshooting
Session Initiation Protocol (SIP) Vulnerabilities. Mark D. Collier Chief Technology Officer SecureLogix Corporation
Session Initiation Protocol (SIP) Vulnerabilities Mark D. Collier Chief Technology Officer SecureLogix Corporation What Will Be Covered Introduction to SIP General SIP security SIP vulnerabilities and
Avaya Aura SIP Trunking Training
Avaya Aura SIP Trunking Training 5 Day Course Lecture & Demo WHO NEEDS TO ATTEND This class is suited to those who are new to administering Avaya systems, need to know how to send calls through an Avaya
THINKTEL COMMUNICATIONS DIGIUM G100/G200 PRI OVER IP SIP TRUNKING
THINKTEL COMMUNICATIONS DIGIUM G100/G200 PRI OVER IP SIP TRUNKING TA B L E O F C O N T E N T S 1.1 NETWORK DIAGRAM... 3 1.2 COLLABORATION OF MONARQUE TELECOM... 3 1.3 CONNECTING TO THE DIGIUM G100... 4
IP Office Technical Tip
IP Office Technical Tip Tip no: 200 Release Date: January 23, 2008 Region: GLOBAL IP Office Session Initiation Protocol (SIP) Configuration Primer There are many Internet Telephony Service Providers (ITSP)
Technical Configuration Notes
MITEL SIPCoE Technical Configuration Notes Configure Mitel UC360 SIP Phone and Mitel MCD for use with VidyoWay SIP CoE 13-4940-00228 NOTICE The information contained in this document is believed to be
MITEL SIP CoE. Technical. Configuration Notes. Configure MCD 4.1 for use with SKYPE SIP Trunking. SIP CoE 10-4940-00120
MITEL SIP CoE Technical Configuration Notes Configure MCD 4.1 for use with SKYPE SIP Trunking SIP CoE 10-4940-00120 NOTICE The information contained in this document is believed to be accurate in all respects
SIP Trunking using Optimum Business Sip Trunk Adaptor and the Zultys MX250 IP PBX
SIP Trunking using Optimum Business Sip Trunk Adaptor and the Zultys MX250 IP PBX Table of Contents Goal 3 Prerequisites 3 Zultys MX250 Configuration 4 Network Settings 4 Phone Registration and Assignment
Session Initiation Protocol (SIP) The Emerging System in IP Telephony
Session Initiation Protocol (SIP) The Emerging System in IP Telephony Introduction Session Initiation Protocol (SIP) is an application layer control protocol that can establish, modify and terminate multimedia
MyIC setup and configuration (with sample configuration for Alcatel Lucent test environment)
MyIC setup and configuration (with sample configuration for Alcatel Lucent test environment) N.B. Goto MyIC Preferences in the System Toolbar. Description: this may be any appropriate description of the
Session Initiation Protocol Gateway Call Flows and Compliance Information
Session Initiation Protocol Gateway Call Flows and Compliance Information Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000
Alcatel-Lucent OmniPCX Enterprise Free Desktop. Free Desktop version 3.0.1 Linux Installation Guide
Alcatel-Lucent OmniPCX Enterprise Free Desktop Free Desktop version 3.0.1 Linux Installation Guide Alcatel-Lucent Services for Enterprise All Rights Reserved Alcatel-Lucent 2008 Legal notice Alcatel, Lucent,
TALKSWITCH VOIP NETWORK TROUBLESHOOTING GUIDE
TALKSWITCH DOCUMENTATION TALKSWITCH VOIP NETWORK TROUBLESHOOTING GUIDE RELEASE 3.24 CT.TS005.008001 ANSWERS WITH INTELLIGENCE COPYRIGHT INFORMATION TalkSwitch. Copyright 2006. All Rights Reserved. Reproduction,
SIP Trunking Application Notes V1.3
SIP Trunking Application Notes V1.3 Publication Information SAMSUNG TELECOMMUNICATIONS AMERICA reserves the right without prior notice to revise information in this publication for any reason. SAMSUNG
MITEL SIP CoE. Technical. Configuration Note. Configure MCD for use with Intelepeer Service provider SIP Trunking. SIP CoE 14-4940-00313
MITEL SIP CoE Technical Configuration Note Configure MCD for use with Intelepeer Service provider SIP Trunking SIP CoE 14-4940-00313 NOTICE The information contained in this document is believed to be
LifeSize Video Communications Systems Administrator Guide
LifeSize Video Communications Systems Administrator Guide November 2009 Copyright Notice 2005-2009 LifeSize Communications Inc, and its licensors. All rights reserved. LifeSize Communications has made
V101 SIP VoIP Telephone Adaptor User Manual V1.1m
V101 SIP VoIP Telephone Adaptor User Manual V1.1m Quick Guide Step 1: Broadband (ADSL/Cable Modem) Connections for V101 A. Connect V101 LAN port to ADSL NAT Router as the following connection. B. Connect
Application Note Configuring the Synapse SB67070 SIP Gateway for Broadvox GO! SIP Trunking
Configuring the Synapse SB67070 SIP Gateway for Broadvox GO! SIP Trunking 2012 Advanced American Telephones. All Rights Reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property licensed
Avaya IP Office 8.1 Configuration Guide
Avaya IP Office 8.1 Configuration Guide Performed By tekvizion PVS, Inc. Contact: 214-242-5900 www.tekvizion.com Revision: 1.1 Date: 10/14/2013 Copyright 2013 by tekvizion PVS, Inc. All Rights Reserved.
Configuring SIP Registration Proxy on Cisco UBE
The Support for SIP Registration Proxy on Cisco UBE feature provides support for sending outbound registrations from Cisco Unified Border Element (UBE) based on incoming registrations. This feature enables
Manual. ABTO Software
Manual July, 2011 Flash SIP SDK Manual ABTO Software TABLE OF CONTENTS INTRODUCTION... 3 TECHNICAL BACKGROUND... 6 QUICK START GUIDE... 7 FEATURES OF FLASH SIP SDK... 10 2 INTRODUCTION Trends indicate
Session Initiation Protocol (SIP)
SIP: Session Initiation Protocol Corso di Applicazioni Telematiche A.A. 2006-07 Lezione n.7 Ing. Salvatore D Antonio Università degli Studi di Napoli Federico II Facoltà di Ingegneria Session Initiation
IP-Telephony SIP & MEGACO
IP-Telephony SIP & MEGACO Bernard Hammer Siemens AG, Munich Siemens AG 2001 1 Presentation Outline Session Initiation Protocol Introduction Examples Media Gateway Decomposition Protocol 2 IETF Standard
nexvortex Setup Guide
nexvortex Setup Guide CISCO UC500 March 2012 Introduction This document is intended only for nexvortex customers and resellers as an aid to setting up the Cisco PBX software to connect to the nexvortex
