®
5ESS
Switch
Session Initiation Protocol (SIP) - OA&M
Manual
5E16.2 and Later Software Releases
235-200-118
Issue 3.02B
March 2007
Copyright © 2007 Lucent Technologies. All Rights Reserved.
This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any
fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or
licensing, without the express written consent of Lucent Technologies and the business management owner of the material.
Notice
Every effort was made to ensure that the information in this information product was complete and accurate at the time of publishing; However,
information is subject to change.
Mandatory customer information
Lucent Technologies 5ESS®switch equipment meets the applicable Network Equipment Building System (NEBS) Requirements as defined by
Telcordia Technologies, Inc.
Trademarks
5ESS is a registered trademark of Lucent Technologies, Inc. in the United States and other countries.
Ordering information
This information product is distributed by the Lucent Technologies Learning Organization in Indianapolis, Indiana. To order, call:
1 888 LUCENT8 (1 888 582-3688) or fax to 1 800 566-9568 (from inside the continental United States)
1 317 322-6416 or fax to 1 317 322-6699 (from outside the continental United States).
Support
Information product support
To report errors or ask nontechnical questions about this or other information products produced by Lucent Technologies, contact the Lucent
Technologies Learning Organization by sending email to comments@lucent.com.
Please include with your comments the title, ordering number, issue number, and issue date of the information product, your complete mailing
address, and your telephone number.
Technical support
For technical assistance, call Lucent Technologies Technical Support Services:
1 866 LUCENT8 (1 866 582-3688) (from inside the continental United States)
1 630 224-4672 (from outside the continental United States)
Technical Support Services is staffed 24 hours a day, 7 days a week.
Lucent Technologies
Contents
BOOKMARK1::Aboutthisinformation productAbout this information product
BOOKMARK2::PurposePurpose xvii
BOOKMARK3::ReasonforreissueReason for reissue xviii
BOOKMARK4::SafetylabelsSafety labels xviii
BOOKMARK5::IntendedaudienceIntended audience xviii
BOOKMARK6::Howtouse thisinformationproductHow to use this information product xix
BOOKMARK7::ConventionsusedConventions used xix
BOOKMARK8::SystemssupportedSystems supported xix
BOOKMARK9::RelateddocumentationRelated documentation xx
BOOKMARK10::HowtocommentHow to comment xx
BOOKMARK11::HowtoorderHow to order xx
.....................................................................................................................................................................................................................................
1 BOOKMARK12::1OverviewOverview
BOOKMARK13::OverviewOverview 1-1
BOOKMARK14::SIPforPacket TrunkingSIP for Packet Trunking 1-2
.....................................................................................................................................................................................................................................
2 BOOKMARK15::2ArchitectureArchitecture
BOOKMARK16::OverviewOverview 2-1
BOOKMARK17::NetworkViewNetwork View 2-3
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
CONTENTS
iii
BOOKMARK18::SystemViewSystem View 2-9
BOOKMARK19::SignalingViewSignaling View 2-17
BOOKMARK20::HardwareViewHardware View 2-24
BOOKMARK21::SecurityViewSecurity View 2-35
.....................................................................................................................................................................................................................................
3 BOOKMARK22::3CallFlowCall Flow
BOOKMARK23::OverviewOverview 3-1
BOOKMARK24::CallFlowOverviewCall Flow Overview 3-2
BOOKMARK25::NetworkArchitectureNetwork Architecture 3-3
BOOKMARK26::High-LevelCallFlowHigh-Level Call Flow 3-9
BOOKMARK27::MessageFlowsMessage Flows 3-15
BOOKMARK28::DetailedCallScenarios -SIPBaseDetailed Call Scenarios - SIP Base 3-26
BOOKMARK29::SIPMessage ExamplesSIP Message Examples 3-40
BOOKMARK30::SIPwithoutEncapsulated ISUP-MessageFlowSIP without Encapsulated ISUP - Message Flow 3-49
BOOKMARK31::SIPwithoutEncapsulated ISUP-DetailedCall ScenarioSIP without Encapsulated ISUP - Detailed Call Scenario 3-50
BOOKMARK32::SIPwithoutEncapsulated ISUP- SIPMessage ExamplesSIP without Encapsulated ISUP - SIP Message Examples 3-65
.....................................................................................................................................................................................................................................
4 BOOKMARK33::4EngineeringConsiderationsEngineering Considerations
BOOKMARK34::OverviewOverview 4-1
BOOKMARK35::SwitchConsiderationsSwitch Considerations 4-2
BOOKMARK36::GlobalSwitchingModule (GSM)ConsiderationsGlobal Switching Module (GSM) Considerations 4-4
BOOKMARK37::PacketSwitchUnit Model2 (PSU2)ConsiderationsPacket Switch Unit Model 2 (PSU2) Considerations 4-6
BOOKMARK38::SessionInitiationProtocol -Protocol Handler(SIP PH)ConsiderationsSession Initiation Protocol - Protocol Handler (SIP PH) Considerations 4-9
BOOKMARK39::GeneralQLPSProtocol Handler(GQPH) ConsiderationsGeneral QLPS Protocol Handler (GQPH) Considerations 4-11
BOOKMARK40::PacketGroupConsiderationsPacket Group Considerations 4-13
BOOKMARK41::AssociationSetConsiderationsAssociation Set Considerations 4-14
....................................................................................................................................................................................................................................
CONTENTS
iv
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
BOOKMARK42::StreamControlTransmission Protocol(SCTP) EndPoint ConsiderationsStream Control Transmission Protocol (SCTP) End Point
Considerations 4-16
BOOKMARK43::UserDatagramProtocol (UDP)Path ConsiderationsUser Datagram Protocol (UDP) Path Considerations 4-17
BOOKMARK44::IPAddressingSchemesIP Addressing Schemes 4-18
BOOKMARK45::MultihomingMultihoming 4-19
BOOKMARK46::MeasurementsMeasurements 4-20
BOOKMARK47::NetworkManagementNetwork Management 4-22
BOOKMARK48::OperationalSupportSystemsOperational Support Systems 4-23
.....................................................................................................................................................................................................................................
5 BOOKMARK49::5ProvisioningProvisioning
BOOKMARK50::OverviewOverview 5-1
BOOKMARK51::ProvisioningSequencesProvisioning Sequences 5-2
BOOKMARK52::SelectandPrepare TerminalSelect and Prepare Terminal 5-11
BOOKMARK53::FeatureActivation(RC/V 8.22)Feature Activation (RC/V 8.22) 5-13
BOOKMARK54::InsertSIPGlobal SM(RC/V 5.80)Insert SIP Global SM (RC/V 5.80) 5-16
BOOKMARK55::DefineProtocolHandler (RC/V22.4)Define Protocol Handler (RC/V 22.4) 5-18
BOOKMARK56::PHChannelGroup Assignment(RC/V 22.16)PH Channel Group Assignment (RC/V 22.16) 5-19
BOOKMARK57::AssignQPH Pipe(RC/V 17.24)Assign QPH Pipe (RC/V 17.24) 5-23
BOOKMARK58::AssignMHPipe (RC/V17.20)Assign MH Pipe (RC/V 17.20) 5-26
BOOKMARK59::UpdateGSM- Non-GSMCommunication (RC/V17.27)Update GSM - Non-GSM Communication (RC/V 17.27) 5-28
BOOKMARK60::InsertCallProcessing SM(RC/V 5.81)Insert Call Processing SM (RC/V 5.81) 5-31
BOOKMARK61::AssignPHChannel Groupas IPProcessor (RC/V33.1)Assign PH Channel Group as IP Processor (RC/V 33.1) 5-34
BOOKMARK62::InsertProcessorGroup (RC/V33.16)Insert Processor Group (RC/V 33.16) 5-38
BOOKMARK63::InsertEthernet- IPInterface (RC/V33.4)Insert Ethernet - IP Interface (RC/V 33.4) 5-41
BOOKMARK64::InsertIPRouting (RC/V33.3)Insert IP Routing (RC/V 33.3) 5-44
BOOKMARK65::InsertRouterPinging (RC/V33.17)Insert Router Pinging (RC/V 33.17) 5-47
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
CONTENTS
v
BOOKMARK66::InsertUDPPath (RC/V33.24)Insert UDP Path (RC/V 33.24) 5-50
BOOKMARK67::InsertSCTPEndpoint Timersand ProtocolParameters (RC/V33.18)Insert SCTP Endpoint Timers and Protocol Parameters (RC/V 33.18) 5-53
BOOKMARK68::InsertSCTPNear Endpoints(RC/V 33.19)Insert SCTP Near Endpoints (RC/V 33.19) 5-56
BOOKMARK69::InsertSCTPFar Endpoints(RC/V 33.21)Insert SCTP Far Endpoints (RC/V 33.21) 5-59
BOOKMARK70::InsertSCTPAssociation-related ProtocolParameters (RC/V33.20)Insert SCTP Association-related Protocol Parameters (RC/V 33.20) 5-62
BOOKMARK71::InsertSCTP Association(RC/V 33.22)Insert SCTP Association (RC/V 33.22) 5-65
BOOKMARK72::InsertSCTP AssociationSet (RC/V33.23)Insert SCTP Association Set (RC/V 33.23) 5-68
BOOKMARK73::UpdateCCSOffice Parameters(RC/V 8.15)Update CCS Office Parameters (RC/V 8.15) 5-71
BOOKMARK74::InsertSIPPSTN InterworkingParameter Set(RC/V 5.83)Insert SIP PSTN Interworking Parameter Set (RC/V 5.83) 5-74
BOOKMARK75::InsertSIPParameters (RC/V5.82)Insert SIP Parameters (RC/V 5.82) 5-79
BOOKMARK76::InsertPacketGroup (RC/V5.71)Insert Packet Group (RC/V 5.71) 5-82
BOOKMARK77::AssignTrunkGroup (RC/V5.1)Assign Trunk Group (RC/V 5.1) 5-85
BOOKMARK78::EnableINVITERequests (RC/V5.81)Enable INVITE Requests (RC/V 5.81) 5-88
BOOKMARK79::AssignRouteIndex (RC/V10.2)Assign Route Index (RC/V 10.2) 5-91
BOOKMARK80::Add/ChangeSIPElements withinan ExistingSIP NetworkAdd/Change SIP Elements within an Existing SIP Network 5-93
BOOKMARK81::AddNewSIPT PHE2IP ProcessorGroup onan ExistingSIP GSMAdd New SIPT PHE2 IP Processor Group on an Existing SIP GSM 5-95
BOOKMARK82::AddNewSCTP NearEndpointAdd New SCTP Near Endpoint 5-99
BOOKMARK83::AddNewSCTP Associationto Connectto aSCTP FarEndpointAdd New SCTP Association to Connect to a SCTP Far Endpoint 5-102
BOOKMARK84::AddNewAssociation Setto AnotherOfficeAdd New Association Set to Another Office 5-105
BOOKMARK85::AddSCTPAssociations toExisting AssociationSetAdd SCTP Associations to Existing Association Set 5-107
BOOKMARK86::AddUDPTransport forSIP Signalingto AnotherOfficeAdd UDP Transport for SIP Signaling to Another Office 5-109
BOOKMARK87::AddNewSIP PacketTrunking toAnother OfficeAdd New SIP Packet Trunking to Another Office 5-112
BOOKMARK88::AddNewSIP Call-ProcessingSMsAdd New SIP Call-Processing SMs 5-116
BOOKMARK89::AddaSIP PHE2to ExistingSimplex SIPIP ProcessorGroupAdd a SIP PHE2 to Existing Simplex SIP IP Processor Group 5-118
BOOKMARK90::ChangeIP/SCTPTransport Addressfor SCTPNear EndpointChange IP/SCTP Transport Address for SCTP Near Endpoint 5-121
....................................................................................................................................................................................................................................
CONTENTS
vi
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
BOOKMARK91::ChangeIP/SCTPTransport Addressfor SCTPFar EndpointChange IP/SCTP Transport Address for SCTP Far Endpoint 5-126
BOOKMARK92::ChangeFarIP TransportAddress forUDP PathChange Far IP Transport Address for UDP Path 5-129
BOOKMARK93::ChangeIPAddress forAdjacent IPRouterChange IP Address for Adjacent IP Router 5-132
BOOKMARK94::ChangeIPParameters fora SIPprocessor groupChange IP Parameters for a SIP processor group 5-136
BOOKMARK95::ChangeSCTPEndpoint ParametersChange SCTP Endpoint Parameters 5-142
BOOKMARK96::ChangeSCTPAssociation ParametersChange SCTP Association Parameters 5-144
BOOKMARK97::ChangeSIPParametersChange SIP Parameters 5-147
BOOKMARK98::ProvisionAlarmLevel forIP FragmentedPackets BeyondPM ThresholdProvision Alarm Level for IP Fragmented Packets Beyond PM
Threshold 5-150
BOOKMARK99::ProvisionAlarmLevel forICMP EchoRequests BeyondPM ThresholdProvision Alarm Level for ICMP Echo Requests Beyond PM Threshold 5-153
BOOKMARK100::ChangeSIPPSTN InterworkingParameter SetChange SIP PSTN Interworking Parameter Set 5-156
.....................................................................................................................................................................................................................................
6 BOOKMARK101::6DeprovisioningDeprovisioning
BOOKMARK102::OverviewOverview 6-1
BOOKMARK103::DeprovisioningSequenceDeprovisioning Sequence 6-3
BOOKMARK104::DisableINVITERequests (RC/V5.81)Disable INVITE Requests (RC/V 5.81) 6-8
BOOKMARK105::DisableAllSCTP Transportfor SIPPacket TrunkingDisable All SCTP Transport for SIP Packet Trunking 6-11
BOOKMARK106::RemoveAllSIP TrunkGroups FromRoute Lists(RC/V 10.2)Remove All SIP Trunk Groups From Route Lists (RC/V 10.2) 6-14
BOOKMARK107::RemoveAllSIP TrunkGroups FromRoute Lists(RC/V 10.4)Remove All SIP Trunk Groups From Route Lists (RC/V 10.4) 6-17
BOOKMARK108::DeleteAllSIP PacketTrunk Groups(RC/V 5.1)Delete All SIP Packet Trunk Groups (RC/V 5.1) 6-20
BOOKMARK109::DeleteAllSIP PacketGroups (RC/V5.71)Delete All SIP Packet Groups (RC/V 5.71) 6-23
BOOKMARK110::DisableAllUDP Transportfor SIPPacket TrunkingDisable All UDP Transport for SIP Packet Trunking 6-26
BOOKMARK111::DeleteAllSIP CallProcessing SMs(RC/V 5.81)Delete All SIP Call Processing SMs (RC/V 5.81) 6-29
BOOKMARK112::DeleteAll SCTPAssociation Sets(RC/V 33.23)Delete All SCTP Association Sets (RC/V 33.23) 6-32
BOOKMARK113::DeleteAll SCTPAssociations (RC/V33.22)Delete All SCTP Associations (RC/V 33.22) 6-35
BOOKMARK114::DeleteAllSCTP FarEndpoints (RC/V33.21)Delete All SCTP Far Endpoints (RC/V 33.21) 6-38
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
CONTENTS
vii
BOOKMARK115::DeleteAllSCTP NearEndpoints (RC/V33.19)Delete All SCTP Near Endpoints (RC/V 33.19) 6-41
BOOKMARK116::DeleteAllSCTP AssociationProtocol ParameterSets (RC/V33.20)Delete All SCTP Association Protocol Parameter Sets (RC/V 33.20) 6-44
BOOKMARK117::DeleteAllSCTP EndpointTimers andProtocol Parameters(RC/V 33.18)Delete All SCTP Endpoint Timers and Protocol Parameters (RC/V
33.18) 6-47
BOOKMARK118::DeleteAllRouter Pinging(RC/V 33.17)Delete All Router Pinging (RC/V 33.17) 6-50
BOOKMARK119::DeleteAllSIP UDPPaths (RC/V33.24)Delete All SIP UDP Paths (RC/V 33.24) 6-53
BOOKMARK120::DeleteAllIP Routingfor SIPUDP Paths(RC/V 33.3)Delete All IP Routing for SIP UDP Paths (RC/V 33.3) 6-55
BOOKMARK121::DeleteAllIP Routingfor SCTPAssociations (RC/V33.3)Delete All IP Routing for SCTP Associations (RC/V 33.3) 6-59
BOOKMARK122::DeleteAllSIP ProcessorGroups (RC/V33.16)Delete All SIP Processor Groups (RC/V 33.16) 6-63
BOOKMARK123::DeleteIPProcessor Assignmentto PH(RC/V 33.1)Delete IP Processor Assignment to PH (RC/V 33.1) 6-66
BOOKMARK124::UpdateAllSIP GSM- Non-GSMCommunication (RC/V17.27)Update All SIP GSM - Non-GSM Communication (RC/V 17.27) 6-69
BOOKMARK125::DeleteAll SIPGQPH Pipes(RC/V 17.24)Delete All SIP GQPH Pipes (RC/V 17.24) 6-72
BOOKMARK126::UpdateAllPHE2 &PH33 ChannelGroup Assignments(RC/V 22.16)Update All PHE2 & PH33 Channel Group Assignments (RC/V 22.16) 6-75
BOOKMARK127::DeleteAllSIP ParameterSets (RC/V5.82)Delete All SIP Parameter Sets (RC/V 5.82) 6-78
BOOKMARK128::DeleteAllSIP PSTNInterworking ParameterSets (RC/V5.83)Delete All SIP PSTN Interworking Parameter Sets (RC/V 5.83) 6-81
BOOKMARK129::DeleteAllSIP GlobalSMs (RC/V5.80)Delete All SIP Global SMs (RC/V 5.80) 6-84
BOOKMARK130::DeleteProtocolHandler (RC/V22.4)Delete Protocol Handler (RC/V 22.4) 6-87
BOOKMARK131::DeleteSIPSignaling froman ExistingSIP NetworkDelete SIP Signaling from an Existing SIP Network 6-88
BOOKMARK132::DeleteSIPPHE2 fromExisting DuplexSIP IPProcessor GroupDelete SIP PHE2 from Existing Duplex SIP IP Processor Group 6-89
BOOKMARK133::DeleteanExisting SIPCall-Processing SMDelete an Existing SIP Call-Processing SM 6-92
BOOKMARK134::DeletePacketTrunking toAnother OfficeDelete Packet Trunking to Another Office 6-94
BOOKMARK135::DeleteAssociationSet toAnother OfficeDelete Association Set to Another Office 6-97
BOOKMARK136::DeleteSCTPAssociations fromExisting AssociationSetDelete SCTP Associations from Existing Association Set 6-99
BOOKMARK137::DeleteExistingSCTP Associationto SCTPFar EndpointDelete Existing SCTP Association to SCTP Far Endpoint 6-101
BOOKMARK138::DeleteSCTPNear EndpointDelete SCTP Near Endpoint 6-107
....................................................................................................................................................................................................................................
CONTENTS
viii
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
BOOKMARK139::DeleteExistingSIP PHE2IP ProcessorGroupDelete Existing SIP PHE2 IP Processor Group 6-109
.....................................................................................................................................................................................................................................
7 BOOKMARK140::7MaintenanceConsiderationsMaintenance Considerations
BOOKMARK141::OverviewOverview 7-1
BOOKMARK142::RoutineMaintenanceRoutine Maintenance 7-3
BOOKMARK143::CollectDatafrom OfficeRecordsCollect Data from Office Records 7-4
BOOKMARK144::RequestSCTPNear EndpointStatusRequest SCTP Near Endpoint Status 7-8
BOOKMARK145::RequestSCTPAssociation StatusRequest SCTP Association Status 7-11
BOOKMARK146::RequestSCTPAssociation SetStatusRequest SCTP Association Set Status 7-14
BOOKMARK147::ReportServiceSelection, Pingand EthernetLink StatusReport Service Selection, Ping and Ethernet Link Status 7-16
BOOKMARK148::InitiateSCTPHeartbeatInitiate SCTP Heartbeat 7-18
BOOKMARK149::Initiate105Test CallInitiate 105 Test Call 7-22
BOOKMARK150::InitiateDelayTest CallInitiate Delay Test Call 7-24
BOOKMARK151::RequestUtilityCall TraceRequest Utility Call Trace 7-26
BOOKMARK152::RequestInternetProtocol (IP)Configuration DataRequest Internet Protocol (IP) Configuration Data 7-28
BOOKMARK153::CorrectiveMaintenanceCorrective Maintenance 7-31
BOOKMARK154::ResolveProtocolHandler ProblemsResolve Protocol Handler Problems 7-34
BOOKMARK155::ResolveLLE2Paddleboard ProblemsResolve LLE2 Paddleboard Problems 7-40
BOOKMARK156::ResolveGQPHQPipe ProblemsResolve GQPH QPipe Problems 7-43
BOOKMARK157::AnalyzeGeneralMessage Transport(GMT) ErrorReportsAnalyze General Message Transport (GMT) Error Reports 7-59
BOOKMARK158::ResolveSCTPAssociation ProblemsResolve SCTP Association Problems 7-64
BOOKMARK159::RemoveSCTPAssociationRemove SCTP Association 7-66
BOOKMARK160::RestoreSCTPAssociationRestore SCTP Association 7-68
BOOKMARK161::ResolveSCTPNear endpointProblemsResolve SCTP Near endpoint Problems 7-70
BOOKMARK162::RemoveSCTPNear EndpointRemove SCTP Near Endpoint 7-75
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
CONTENTS
ix
BOOKMARK163::RestoreSCTPNear EndpointRestore SCTP Near Endpoint 7-77
BOOKMARK164::AnalyzeSCTPNear EndpointChange ReportAnalyze SCTP Near Endpoint Change Report 7-79
BOOKMARK165::AnalyzeSCTPAssociation ChangeReportAnalyze SCTP Association Change Report 7-81
BOOKMARK166::RequestManualService SelectionSwitchRequest Manual Service Selection Switch 7-83
BOOKMARK167::AnalyzeServiceSelection ChangeReportAnalyze Service Selection Change Report 7-85
BOOKMARK168::DumpIPRouting TableDump IP Routing Table 7-87
BOOKMARK169::DumpAddressResolution Protocol(ARP) TableDump Address Resolution Protocol (ARP) Table 7-89
BOOKMARK170::PerformanceMonitoringon SIPPHPerformance Monitoring on SIP PH 7-91
.....................................................................................................................................................................................................................................
GL BOOKMARK171::GlossaryGlossary GL-1
.....................................................................................................................................................................................................................................
IN BOOKMARK172::IndexIndex IN-1
....................................................................................................................................................................................................................................
CONTENTS
x
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
List of Figures
2 Architecture
2-1 IP Backbone 2-3
2-2 SIP Signaling Network, Hardware Perspective 2-4
2-3 SIP Signaling Network, Provisioning Perspective 2-5
2-4 Bearer Network 2-6
2-5 Packet Trunking 2-7
2-6 PSTN Gateway 2-8
2-7 SIP Architecture 2-9
2-8 SIP on DRM Architecture 2-11
2-9 Sample Configurations 2-15
2-10 SIP Protocol Stack 2-17
2-11 SCTP Endpoints 2-19
2-12 Multiple SCTP Associations 2-21
2-13 Paths Between Endpoints 2-22
2-14 Pack Faceplates 2-26
2-15 PSU2 Shelf Arrangement 2-27
2-16 Connecting circuits 2-29
2-17 SIP PH Functionality 2-31
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
FIGURES
xi
2-18 Cookie Mechanism 2-36
.....................................................................................................................................................................................................................................
3 Call Flow
3-1 Packet Trunking 3-3
3-2 PSTN Gateway 3-4
3-3 Network Elements 3-6
3-4 Network Connections 3-8
3-5 Successful Call Completion Message Flow 3-15
3-6 5ESS®Switch OPS - 5ESS®Switch TPS Message Flow 3-17
3-7 5ESS®Switch PSTN Gateway TPS and TAS OPS Message
Flow 3-21
3-8 SIP INVITE 3-40
3-9 SIP 183 SESSION PROGRESS 3-43
3-10 SIP UPDATE 3-44
3-11 SIP 200 OK (UPDATE) 3-45
3-12 SIP 180 RINGING 3-46
3-13 SIP 200 OK (INVITE) 3-47
3-14 SIP BYE 3-47
3-15 SIP 200 OK (BYE) 3-48
3-16 SIP without Encapsulated ISUP Successful Call 3-49
3-17 High-level Call Flow (without Encapsulated ISUP) 3-50
3-18 Call Setup at OPS - Steps 1-9 3-51
3-19 Call Setup at OPS - Steps 10-17 3-53
3-20 Call Setup at OPS - Steps 18-21 3-54
3-21 Call Setup at OPS - Steps 22-25 3-55
3-22 Call Setup at TPS - Steps 1-6 3-56
....................................................................................................................................................................................................................................
FIGURES
xii
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
3-23 Call Setup at TPS - Steps 7-12 3-58
3-24 Call Setup at TPS - Steps 13-18 3-59
3-25 Call Setup at TPS - Steps 19-23 3-60
3-26 Call Tear Down at OPS 3-61
3-27 Call Tear Down at TPS 3-63
3-28 SIP INVITE {SDP} 3-65
3-29 SIP 183 SESSION PROGRESS {SDP} 3-66
3-30 SIP UPDATE {SDP} 3-67
3-31 SIP 200 OK (UPDATE) {SDP} 3-68
3-32 SIP 180 RINGING 3-69
3-33 200 OK (INVITE) 3-70
3-34 SIP ACK 3-70
3-35 SIP BYE 3-70
3-36 200 OK (BYE) 3-71
.....................................................................................................................................................................................................................................
4 Engineering Considerations
4-1 Two shelf PSU2 4-7
4-2 Engineering Association Sets 4-15
.....................................................................................................................................................................................................................................
5 Provisioning
5-1 SM Connectivity Provisioning Flowchart 5-3
5-2 Signaling Provisioning Flowchart for SIP with SCTP Transport 5-5
5-3 Signaling Provisioning Flowchart for SIP with UDP Transport 5-7
.....................................................................................................................................................................................................................................
6 Deprovisioning
6-1 Deprovisioning Flowchart 6-4
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
FIGURES
xiii
.....................................................................................................................................................................................................................................
7 Maintenance Considerations
7-1 “Autonomous Reports Flowchart” 7-32
7-2 “Resolve Protocol Handler Problems Flowchart” 7-35
7-3 “Resolve GQPH QPipe Problems Flowchart” 7-44
7-4 “Resolve SCTP Near Endpoint Problems Flowchart” 7-71
....................................................................................................................................................................................................................................
FIGURES
xiv
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
List of Tables
2 Architecture
2-1 TCP/UDP/SCTP Comparison 2-17
2-2 SIP PH Characteristics 2-24
2-3 GQPH Characteristics 2-24
2-4 PSU2 shelf power terminations 2-27
2-5 Service Selection State 2-33
2-6 Service Selection State Combinations 2-34
.....................................................................................................................................................................................................................................
4 Engineering Considerations
4-1 IOST model BHC capacities 4-4
4-2 IOSE model BHC capacities 4-4
4-3 PSTNGW-LT model BHC capacities 4-4
4-4 PH equipage - one shelf 4-7
4-5 PH equipage - two shelves 4-8
4-6 SIP PH Configuration 4-9
4-7 SIP PH Equipage 4-10
4-8 GQPH Configuration 4-11
4-9 Control - messaging timeslots 4-12
4-10 GQPH Equipage 4-12
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
TABLES
xv
.....................................................................................................................................................................................................................................
5 Provisioning
5-1 SIP to PSTN Mapping Reference 5-77
5-2 PSTN to SIP Mapping Reference 5-78
....................................................................................................................................................................................................................................
TABLES
xvi
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
About this information product
...............................................................................................................................................................................................................................................................
Purpose
The 5ESS®Switch Session Initiation Protocol (SIP) - OA&M Manual,
5E16.2 and Later, 235-200-118, information product enables users,
planners, maintenance personnel, engineers, installers, administrators,
and provisioners to perform the necessary tasks required to support
configuration, installation, monitoring, and repair of SIP signaling for
packet trunking (including packet groups, SIP, SCTP, UDP, IP, QLPS
connectivity, processor groups, and signaling-related hardware).
OA&M procedures related to the OIU-IP bearer for SIP-signaled calls
are covered in Optical Interface Unit - Internet Protocol (OIU-IP)
Interface Specification [5E16.2 and Later Software Releases],
235-900-316.
This information product should be used as the source of complete
details on this protocol to clarify the implementation on the switch
and the interpretation of technical reference (TR) requirements. These
®
details describe the 5ESS
switch offerings in terms of the support of
Session Initiation Protocol (SIP). SIP is an evolving platform in which
new features will be introduced continuously for new revenue
opportunities, for improved operational efficiencies, and for support of
specific applications. Beginning with the 5E16.2 software release, the
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
,
Lucent Technologies
xvii
5E16.2 and Later Software Releases
5ESS®switch supports the protocols and services defined by Telcordia
Technologies, Inc.
This information product is expected to change as requirements and
standards evolve. Therefore, Lucent Technologies reserves the right to
change or delete any portion of the document, or to add information
in future issues.
Reason for reissue
This information product is being reissued to support feature
99-5E-8645, “DRM IP Trunking”
About this information product
®
Safety labels
Typical safety labels are contained in this information product. The
safety labels include warnings, cautions, and dangers and are
accompanied by icons that indicate the type and level of safety hazard
involved.
CAUTION
Caution indicates the presence of a hazard that can or will
cause minor injury or property damage.
WARNING
Warning indicates the presence of a hazard that can cause
death or severe injury.
DANGER
Danger indicates the presence of a hazard that will cause
death or severe injury.
Intended audience
....................................................................................................................................................................................................................................
xviii
The 5ESS®Switch Session Initiation Protocol for Packet Trunking OA&M Manual describes the architecture, engineering, provisioning,
®
and maintenance of SIP on the 5ESS
switch. It is published as a
guide for the users, planners, maintenance personnel, engineers,
installers, administrators, and provisioners to perform their SIP-related
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
,
5E16.2 and Later Software Releases
tasks. Responsible personnel should have a working knowledge of
telephony, switching, routing, and networking technologies.
About this information product
How to use this
information product
Each chapter in this information product groups related information
about the SIP application.
Chapter Content
1. Overview Overview of SIP from an industry perspective
and Lucent Technologies’ perspective.
2. Architecture Overview of the SIP architecture, starting at
the Network view, then narrowing down to the
System view, and finally, focusing on the
hardware view.
3. Call Flow Overview of SIP call flows through the
network (office-to-office), and through the
®
5ESS
4. Engineering
Considerations
Things to keep in mind when engineering SIP
into your switch and network (for example,
capacity, configuration, constraints, IP
addressing schemes, network management,
performance monitoring, and OS impact).
5. Provisioning Procedures required for provisioning all
aspects of the SIP platform on your switch and
in your network.
switch hardware.
6. Deprovisioning Procedures required to remove the SIP
®
switch.
7. Maintenance
Considerations
application from the 5ESS
Overview of troubleshooting and maintenance
specific to SIP.
8. Glossary List of acronyms used within this IP and their
expansions.
9. Index Index of subjects covered within this IP.
Conventions used
No special or unusual conventions are used in this information
product.
Systems supported
This information product supports software releases 5E16.2, Feature
Release 3, and later.
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
,
Lucent Technologies
xix
5E16.2 and Later Software Releases
About this information product
Related documentation
Other customer documentation that will be useful in understanding the
®
5ESS
switch SIP platform are the following:
• OIU-IP feature description, Feature Descriptions, 235-190-400
• OIU-IP Interface Specification, 235-900-316
• Session Initiation Protocol (SIP) - Interface Specification,
235-900-344
Specific procedural and descriptive information from the following
information products are referred to:
• Administration and Engineering Guidelines, 235-070-100
• Translation Guide (TG-5), 235-080-100
• Hardware Description, 235-100-200
• System Maintenance Requirements and Tools, 235-105-110
• Routine Operations and Maintenance Procedures, 235-105-210
• Corrective Maintenance Procedures, 235-105-220
• Hardware Change - Growth Procedures, 235-105-231
• System Recovery, 235-105-250
How to comment
How to order
• Hardware Change - Degrowth Procedures, 235-105-331
• Recent Change Reference 5E16.2 Software Release, 235-118-258
• Translations Data Reference, 235-600-126
• Translations & Dynamic Data Reference, 235-600-228
• Dynamic Data Reference, 235-600-237
• Translations & Dynamic Data Domain Description, 235-600-248
• Audits Manual, 235-600-400
• Asserts Manual, 235-600-500
• Input Messages Manuals, 235-600-700
• Output Messages Manuals, 235-600-750
To comment on this information product, go to the Online Comment
Form (http://www.lucent-info.com/comments/enus/) or email your
comments to the Comments Hotline (comments@lucent.com).
The Lucent Technologies Learning Organization in Indianapolis,
Indiana, distributes this information product. It can be ordered by
phone, fax, mail, or on line. Specific ordering information is listed
below. When ordering, refer to information product number
....................................................................................................................................................................................................................................
xx
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
,
5E16.2 and Later Software Releases
235-200-118, 5ESS®Switch Session Initiation Protocol (SIP) - OA&M
Manual, 5E16.2 and Later. Proper billing information must be
provided.
To order this information product by phone, call:
To order this information product online, logon to http://www.
lucentdocs.com.
To order this information product by mail, write to the following
address:
Lucent Technologies Learning Organization
2855 N. Franklin Road
About this information product
1 888 LUCENT8 (1 888 582-3688) or fax to 1 800 566-9568
(from inside the continental United States)
1 317 322-6416 or fax to 1 317 322-6699 (from outside the
continental United States).
Indianapolis, IN 46219
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
,
Lucent Technologies
xxi
1 Overview
Overview
....................................................................................................................................................................................................................................
Purpose
The purpose of this chapter is to provide an overview of the following
Session Initiation Protocol (SIP) features on the 5E-XC and 5E DRM:
• “SIP for Packet Trunking” (1-2) (99-5E-8382),
• “UDP Transport Layer for SIP” (1-3) (99-5E-8581),
• “Support for SIP without Preconditions” (1-3) (99-5E-8582),
• “SIP Support for Line to Packet Trunk Calls” (1-3) (99-5E-8583),
• “SIP without Encapsulated ISUP” (1-3) (99-5E-8587), and
• “SIP Enhancements to Support PSTN Gateway Phase 1” (1-3)
(99-5E-8658).
• “DRM IP Trunking” (1-4) (99-5E-8645),
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
1-1
Overview
SIP for Packet Trunking
....................................................................................................................................................................................................................................
Platform definition
Feature descriptions
Session Initiation Protocol (SIP) is a method of establishing,
maintaining, and terminating internet sessions. These sessions
interactively exchange real-time multimedia data (voice, text, and
video) between multiple participants. SIP is based on a client-server
model with intelligent end-points. End servers respond to session
initiation requests and locate the called parties. SIP is an application
layer protocol that can run on top of different transport protocols.
The SIP for Packet Trunking - NAR (99-5E-8382) feature adds a SIP
®
packet trunking interface to the 5ESS
®
5ESS
switch to operate as a gateway for interworking between the
switch. This feature allows the
time division multiplexing (TDM)-based public switched telephone
network (PSTN) trunks and the next-generation internet protocol (IP)
network virtual trunks. It interworks current circuit signaling
protocols, such as Signaling System 7 (SS7) integrated services user
part (ISUP), multifrequency (MF), or dual tone multifrequency
(DTMF), with SIP trunk signaling over IP networks.
The SIP signaling protocol for telephony is the packet signaling
protocol used to establish calls using the Optical Interface Unit Internet Protocol (OIU-IP).
The SIP for Packet Trunking feature contains:
• two new PSU2 protocol handlers (SIP-PH and the GQPH) for
setting up the SIP signaling connection,
• a new lower layer transport protocol, Stream Control
Transmission Protocol (SCTP), and
• integrated operations, administration, maintenance and
®
provisioning (OAM&P) using the conventional 5ESS
switch
interfaces.
Automatic ACM Timer - is a modification to the 99-5E-8382 feature
being implemented in software release 5E16.2 FR6. The Automatic
address complete message (ACM) timer is a new field on RC/V 5.82.
The timer value ranges from 4-14 seconds, with 14 seconds as the
default. This timer is started at the originating packet switch (OPS) by
the SIP terminal process when an INVITE message is sent to a
terminating packet switch (TPS). If the timer expires, the SIP
Terminal Process generates a default ISUP ACM that is sent to the
....................................................................................................................................................................................................................................
1-2
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
SIP for Packet Trunking
Overview
ISUP originating terminal process (OTP). The ISUP OTP will send an
ACM message out to the ISUP network. This prevents the call from
being terminated by the ISUP office because the TPS response was
too slow.
The features that follow enhance the capabilities provided by the SIP
for Packet Trunking feature (99-5E-8382). Feature descriptions for
these features can be found in the Feature Descriptions, 235-190-400
document.
UDP Transport Layer for SIP
The UDP Transport Layer for SIP (99-5E-8581) feature allows the
™
5E-XC
allowing the 5E-XC
to support SIP with a UDP transport layer instead of SCTP,
™
to connect to SIP network elements that do not
support SCTP.
Support for SIP without Preconditions
The Support for SIP without Preconditions (99-5E-8582) feature
allows SIP calls to be established without the precondition procedures
that were initially required by the SIP for Packet Trunking feature. For
additional information about SIP signaling procedures, with or without
preconditions, see the Session Initiation Protocol (SIP) - Interface
Specification, 235-900-344 document.
SIP Support for Line to Packet Trunk Calls
The SIP Support for Line to Packet Trunk Calls (99-5E-8583) feature
allows analog and ISDN line originations and terminations to be
routed to and from SIP packet groups, in addition to the circuit trunk
originations and terminations initially supported by the SIP for Packet
Trunking feature.
SIP without Encapsulated ISUP
The SIP without Encapsulated ISUP (99-5E-8587) feature allows the
™
5E-XC
to interwork with elements that do not generate and process
ISUP messages and to generate appropriate interworking messages to
™
pass through the network. The 5E-XC
supports SIP without
Encapsulated ISUP on a per packet group basis.
SIP Enhancements to Support PSTN Gateway Phase 1
The SIP Enhancements to Support PSTN Gateway Phase 1
(99-5E-8658) feature provides a series of enhancements that allow
phone calls to be setup between PSTN subscribers and IP subscribers
that terminate to a Telephone Application Server (TAS). The PSTN
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
1-3
SIP for Packet Trunking
Overview
Gateway sits between the IP network (using SIP signaling) and PSTN
network (using ISUP signaling). The PSTN Gateway performs the
interworking between SIP and ISUP protocols.
DRM IP Trunking
The DRM IP Trunking (99-5E-8645) feature extends SIP-T signaling
and OIU-IP packet trunking to the DRM.
Feature descriptions for the features listed above can be found in the
Feature Descriptions, 235-190-400 document.
Benefits
SIP is an emerging IP-based protocol that is critical for deploying
converged and next generation real-time voice, data and video
communication services. SIP for Packet Trunking gives the 5ESS
®
switch direct access to more efficient IP transport networks. It allows
for the utilization of more cost-effective revenue-generating services.
It also can be used to expand trunking capacity or to replace existing
circuit trunks.
SIP for Packet Trunking:
• reuses the embedded network equipment to migrate to an all IP
multimedia network,
• provides high quality service with 99.999% hardware and
software reliability,
®
• reuses existing integrated 5ESS
switch OAM&P interfaces,
• supports inter-operability with other vendors equipment through
development based on industry standards,
• reuses existing switch hardware and software infrastructure,
• interfaces with the TDM-based PSTN trunks or next generation
IP network virtual trunks, and
• can use SCTP to provide additional network security.
Differences
The existing TDM network contains dedicated circuits between two
end-points. IP calls have no fixed connections. Calls are dynamically
routed through the packet network based on available bandwidth. The
connection information is exchanged using SIP signaling.
The migration from an expansive SS7-based signaling transfer point
(STP) network to an IP-based signaling network will be ongoing. As
SIP evolves, more capabilities will be defined and added.
....................................................................................................................................................................................................................................
1-4
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
SIP for Packet Trunking
Overview
Secured features
Availability
The features that follow are secured features listed with the associated
secured feature IDs (SFIDs). Recent Change view 8.22 is used to
activate these features. Refer to “Feature Activation (RC/V 8.22)”
(5-13) for the procedure.
• SIP for Packet Trunking (SFID 684)
• SIP without Encapsulated ISUP (SFID 769)
The following list provides the availability for SIP related features:
• SIP for Packet Trunking (feature 99-5E-8382) is available with
the 5E16.2 FR3 software release or later.
• UDP Transport Layer for SIP (feature 99-5E-8581) and Support
for SIP without Preconditions (feature 99-5E-8582) are available
with 5E16.2 FR5 software release or later.
• SIP without Encapsulated ISUP (feature 99-5E-8587) and SIP
Enhancements to Support PSTN Gateway Phase 1 (feature
99-5E-8658) are available with the 5E16.2 FR6 software release
or later.
Deployment
Background knowledge
• The DRM IP Trunking (99-5E-8645) feature is available with the
5E16.2 FR 9 software release or later.
This platform is provided on a per office basis.
When SIP is used in media gateway controllers for call establishment,
there are many cases where it must bridge the PSTN network with IP
networks. To do this, SIP must be extended to transport all of the
PSTN signaling information transparently. By extending SIP
messaging and adding PSTN signaling encapsulation functionality, the
SIP protocol can be used for media gateway to media gateway
communication.
Interfacing with a IP network requires an understanding of the
following IP concepts and equipment:
• routers and Layer 2 (L2) switches,
• Ethernet,
• internet protocol and internet control message protocol (ICMP),
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
1-5
SIP for Packet Trunking
Overview
• transport protocols like SCTP and user datagram protocol (UDP),
and
• SIP standards and protocols.
Hardware Dependencies
Software Dependencies
The Optical Interface Unit - Internet Protocol (OIU-IP) hardware
(feature 99-5E-8308) needs to be installed and active.
Other hardware required to support this feature includes two types of
protocol handlers (PHs); the PHE2 to support the SIP PH
functionality, and the PH33 to support the General Quad-link Package
Switch (QLPS) PH (GQPH), as well as the following:
• SM2000 switching modules,
• QLPS,
• Packet Switch Unit - Model 2 (PSU2), and
• Data Fanout - Model 2 (DF2).
Note: This QLPS and PH33 are not required on the DRM/VCDX.
Refer to Chapter 4, “Engineering Considerations” for a list of the
required hardware.
The following software components are needed:
• new SIP signaling software supported by SCTP or UDP for
transport,
• software to support the optical facility interface (OFI) circuit
pack hardware delivered with the Optical Interface Unit for NAR
Market feature (99-5E-7140),
• software to support the optical facility interface internet protocol
(OFI-IP) circuit pack hardware delivered with the Optical
Interface Unit - Internet Protocol feature (99-5E-8308), and
• operational support system (OSS) enhancements.
Incompatibilities
Feature Interactions
There are no incompatibilities with other features.
SIP for Packet trunking defines the signaling protocol to control the
bearer transport delivered with the Optical Interface Unit - Internet
Protocol (OIU-IP) feature (99-5E-8308).
SIP for Packet Trunking that uses UDP Transport Layer for SIP
(99-5E-8581) requires Support for SIP without Preconditions
....................................................................................................................................................................................................................................
1-6
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
SIP for Packet Trunking
Overview
(99-5E-8582). Both features are dependent on the base SIP feature
(99-5E-8382).
The SIP without Encapsulated ISUP feature (99-5E-8587) is
dependent on the base SIP feature (99-5E-8382). The SIP without
Encapsulated ISUP feature is transport independent.
The SIP Enhancements to Support PSTN Gateway Phase 1
(99-5E-8658) is dependent on the base SIP feature (99-5E-8382).
The DRM IP Trunking (99-5E-8645) is dependent on the base SIP
feature (99-5E-8382).
Inter-operability
One of the main objectives of SIP is to provide call signaling and call
control independent of the IP network technology.
Inter-operability with IP equipment
The IP router or Layer 2 (L2) switch to which the 5ESS®switch
protocol handlers (PHs) interface can be from any vendor, provided
that it meets the requirements of the Session Initiation Protocol (SIP)
- Interface Specification, 235-900-344 document.
®
The IP network components and the 5ESS
switch can be configured
many different ways. The different configurations are described in “IP
Router & Layer 2 Switch Interoperability” (2-15).
Inter-operability with other Switching Systems
SIP for Packet Trunking is based on standards for the protocol layers
including SIP, SCTP, and/or UDP, IP, and ICMP, and the software is
intended to operate with other vendors. However, this feature works
®
best when used with other 5ESS
switches. If another vendor’s switch
adheres to the standards in the same way, the products should be
compatible. No assumptions are made about inter-operability with
other vendor’s equipment.
The Session Initiation Protocol (SIP) - Interface Specification,
235-900-344 document explains the interface implementation in
greater detail.
Customer Security
It is the customer’s responsibility to ensure the security of the IP
backbone network. It is assumed that the IP layer security is
®
performed by the edge router and that the 5ESS
switch is in a trusted
network.
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
1-7
SIP for Packet Trunking
Overview
Industry standards
SIP for Packet Trunking is based on standards by the Internet
™
Engineering Task Force (IETF) and Telecordia
Technologies.
SIP standards continue to be defined and extended. Some standards
are in draft form and, in some cases, incomplete or not well defined.
In some instances, standards could not be followed simply because no
standard exists.
IETF RFC Title
RFC 3261 SIP: Session Initiation Protocol
RFC 2960 Stream Control Transmission Protocol
RFC 768 User Datagram Protocol
RFC 791 Internet Protocol
RFC 792 Internet Control Message Protocol
RFC 1122 Requirements for Internet Hosts -- Communication
Layers
RFC 1332 The PPP Internet Protocol Control Protocol (IPCP)
RFC 1661 The Point-to-Point Protocol (PPP)
RFC 1662 PPP in HDLC-like Framing
RFC 2474 Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers
RFC 2615 PPP over SONET/SDH
RFC 1878 Variable Length Subnet Table for IPv4
RFC 1918 Address Allocation for Private Internets
RFC 917 Internet Subnets
RFC 1519 Classless Inter-Domain Routing (CIDR): an Address
Assignment and Aggregation Strategy
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
RFC 2665 Definitions of Managed Objects for the Ethernet-like
Interface Types
RFC 2011 SNMPv2 Management Information Base for the Internet
Protocol using SMIv2
RFC 2013 SNMPv2 Management Information Base for the User
Datagram Protocol using SMIv2
RFC 3372 Session Initiation Protocol for Telephones (SIP-T):
Context and Architectures
....................................................................................................................................................................................................................................
1-8
Lucent Technologies 235-200-118
Issue 3.02B, March 2007
Loading...