Finnish Profile For SIP Tariff Interworking Annex 1 .

2y ago
24 Views
2 Downloads
249.94 KB
7 Pages
Last View : 2m ago
Last Download : 2m ago
Upload by : Shaun Edmunds
Transcription

Suositus1 (7)217/2016 S30.9.2016Finnish profile for SIP tariff interworkingAnnex 1 - applying the SIP tariffViestintäviraston suosituksia217/2016 SViestintävirastoKommunikationsverketFinnish CommunicationsRegulatory AuthorityItämerenkatu 3 APL 31300181 HelsinkiPuhelin 0295 390 100www.viestintävirasto.fiÖstersjögatan 3APB 313, FI-00181Helsingfors, FinlandTelefon 358 295 390 100www.kommunikationsverket.fiItämerenkatu 3AP.O. Box 313, FI-00181Helsinki, FinlandTelephone 358 295 390 100www.ficora.fi

Suositus2 (7)217/2016 S30.9.2016Contents1Terminology and definitions . 32References . 43About this document. 44General information . 45Conversion between SIP tariff and ISUP MPM . 55.1Guidelines for CDP . 55.2Guidelines for CGP . 55.3Conversion from ISUP MPM to SIP tariff . 66CDR considerations . 77Intermediate parties and SIP tariff . 7ViestintävirastoKommunikationsverketFinnish CommunicationsRegulatory AuthorityItämerenkatu 3 APL 31300181 HelsinkiPuhelin 0295 390 100www.viestintävirasto.fiÖstersjögatan 3APB 313, FI-00181Helsingfors, FinlandTelefon 358 295 390 100www.kommunikationsverket.fiItämerenkatu 3AP.O. Box 313, FI-00181Helsinki, FinlandTelephone 358 295 390 100www.ficora.fi

Suositus3 (7)217/2016 S30.9.20161Terminology and definitionsThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and "OPTIONAL" in this document are to be interpretedas described in RFC 2119 [RFC 2119].ViestintävirastoKommunikationsverketFinnish CommunicationsRegulatory AuthoritySIPSession Initiation ProtocolXMLeXtensible Markup LanguageCDPCharge Determination PointCGPCharge Generation PointSIPSession Initiation ProtocolISUPISDN User PartCRGTChaRGe Tariff informationAOCRGAdd-On ChaRGe informationCRGISUP ChaRGe messageMPMISUP Metering Pulse MessageCDRCall Data RecordItämerenkatu 3 APL 31300181 HelsinkiPuhelin 0295 390 100www.viestintävirasto.fiÖstersjögatan 3APB 313, FI-00181Helsingfors, FinlandTelefon 358 295 390 100www.kommunikationsverket.fiItämerenkatu 3AP.O. Box 313, FI-00181Helsinki, FinlandTelephone 358 295 390 100www.ficora.fi

Suositus4 (7)217/2016 S30.9.20162References[RFC 2119] Key words for use in RFCs to Indicate RequirementLevels, https://datatracker.ietf.org/doc/rfc2119/[RFC 3261] SIP: Session Initiation [RFC 4028] Session Timers in the Session Initiation Protocol(SIP), https://datatracker.ietf.org/doc/rfc4028/[RFC 6086] Session Initiation Protocol (SIP) INFO Method andPackage Framework, https://datatracker.ietf.org/doc/rfc6086/[RFC 3023] XML Media PP TS 29.658 V12.0.0] SIP Transfer of IP MultimediaService Tariff Information; Protocol specification (Release ation 31] Regulation 31 on technical aspects of chargingin communications nicationsnetworks.html3About this documentThis document describes some aspect of applying the SIP tariffinformation described in Recommendation 217/2016 S Finnishprofile for SIP tariff interworking.Aspects not covered in this document or given reference to canbe agreed based on bilateral operator agreement.Every MUST in this document is a strict requirement.4General informationOperators MUST fulfill requirements of Regulation 31.It can be bilaterally agreed how to handle error situationswhere for example the SIP tariff information sent by CDP is notaccepted by CGP.The CGP can include SIP Warning header as defined in RFC3261 to the 200 OK response of SIP INFO tariff message. Alloperators MUST accept the Warning header in 200 OK sh CommunicationsRegulatory AuthorityItämerenkatu 3 APL 31300181 HelsinkiPuhelin 0295 390 100www.viestintävirasto.fiÖstersjögatan 3APB 313, FI-00181Helsingfors, FinlandTelefon 358 295 390 100www.kommunikationsverket.fiItämerenkatu 3AP.O. Box 313, FI-00181Helsinki, FinlandTelephone 358 295 390 100www.ficora.fi

Suositus5 (7)217/2016 S30.9.2016Warning code 399 and warning text clearly indicating the causeand/or result of the warning can be used.Information on fault situations can be logged according toguidelines regulating the logging on traffic data.5Conversion between SIP tariff and ISUP MPMIntroduction of SIP tariff based charging in telephony networksdoes not affect the current specifications or conventionsconcerning the ISUP MPM based charging. However, as long asboth ISUP MPM based charging and SIP tariff based chargingcoexist in telephony networks, the conversion between SIPtariff information and ISUP MPM information is required.If the need arises to change or specify in greater detail themethods concerning ISUP MPM handling due to introduction ofSIP tariff, such changes should primarily be handled withinISUP specifications and documents related to ISUP MPMhandling.5.1Guidelines for CDPThe charge indicated by ISUP MPM messages is always themultiple of the price of a metering pulse (0,0673 , 0% VAT).Even though the call prices are a commercial decision thatevery operator and/or service provider can make, as long asboth SIP and ISUP based charging can be used in the same call,it is RECOMMENDED that the charges indicated by SIP tariffmessage are defined so that the rounding error to the chargeindicated by MPM messages is as small as possible.The information about the used VAT percentage can't beindicated in SIP tariff message. Because of this the chargeindicated by SIP tariff MUST be with 0% VAT.The 3GPP specification on SIP tariff handling gives a possibilityto apply very high prices on calls, and therefore operators MAYapply filters that limit the maximum price that is applied. Pricelimits for individual can be defined on bilateral trafficagreements between operators.5.2Guidelines for CGPWhen converting the SIP tariff information to ISUP MPMmessages, the price of a metering pulse needs to be set in CGP.When doing the backwards calculation of the charge indicatedby currencyFactor and currencyScale to generate ISUP MPMViestintävirastoKommunikationsverketFinnish CommunicationsRegulatory AuthorityItämerenkatu 3 APL 31300181 HelsinkiPuhelin 0295 390 100www.viestintävirasto.fiÖstersjögatan 3APB 313, FI-00181Helsingfors, FinlandTelefon 358 295 390 100www.kommunikationsverket.fiItämerenkatu 3AP.O. Box 313, FI-00181Helsinki, FinlandTelephone 358 295 390 100www.ficora.fi

Suositus6 (7)217/2016 S30.9.2016messages, the CGP MUST ensure that the price applied is neverhigher than the price indicated in SIP tariff message. Whenconverting the received tariff information to ISUP MPs (CRGmessages), this means the following: In time based charging, the CGP MUST round thecalculated time interval betweenconsecutive ISUPCRG messages up. In time based charging per starting time unit, call setupcharge or additional charge, the CGP MUST round thecalculated number of MPs down.Pricing errors between SIP tariff and ISUP MPM may causeinaccuracy in clearing between operators. How to handle thisinaccuracy can be agreed bilaterally between operators whentaking the 3GPP tariff in use.5.3Conversion from ISUP MPM to SIP tariffThere is a schematic difference in the method how the charginginformation is indicated with SIP tariff and how it is indicatedwith ISUP MPM. The SIP tariff information for call setup chargeand time based charging can be given in a single SIP tariffmessage for the whole duration of the call. On ISUP the chargeinformation is based on the cumulated number of MPMmessages during call and the price of a call can be reliablycalculated only after the call has ended.Because of this, the conversion from ISUP MPM to SIP tariff canbe reliably done only by using aocrg messages, where eachISUP MPM message should immediately result in acorresponding aocrg message on SIP side. The price indicatedin aocrg message MUST be the price of a metering pulsemultiplied with the number of metering pulses in ISUP MPMmessage.Here it also needs to be noticed that according to 3GPP SIPtariff specification no aocrg message be can be sent during callunless at least one crgt message has been sent. This meansthat the first MPM message MUST be converted to crgt messagewith Call Setup Charge indicating the MPM price. SubsequentMPM messages MUST be converted to aocrg messages.Another possible method to transfer call pricing information inSIP networks is to use MPM messages over SIP-I. The decisionon using either 3GPP tariff or SIP-I can be done bilaterallybetween nish CommunicationsRegulatory AuthorityItämerenkatu 3 APL 31300181 HelsinkiPuhelin 0295 390 100www.viestintävirasto.fiÖstersjögatan 3APB 313, FI-00181Helsingfors, FinlandTelefon 358 295 390 100www.kommunikationsverket.fiItämerenkatu 3AP.O. Box 313, FI-00181Helsinki, FinlandTelephone 358 295 390 100www.ficora.fi

Suositus7 (7)217/2016 S30.9.20166CDR considerationsBelow are listed the new 3GPP tariff and SIP parameters thatcan have influence on the call pricing and on how the tariff isapplied. Operators can collect and apply this information asthey see necessary.Time of SIP tariff indication (when the SIP INFOmessage is sent or received). If several INFOmessages are sent during the same call, each INFOmessage should be noted separatelyCall-id header value of the SIP tariff messageNetwork identificationTime based charge indicated bycommunicationChargeSequenceCurrency, includingthe possible cyclic and subtariffs.Tariff durationCall Setup ChargeAdd On ChargeDelay Until StartContents of Warning header from 200 OK reply toSIP tariff INFO message7Intermediate parties and SIP tariffIf the tariff information if transferred via several operators, SIPtariff messages can be terminated and recreated by anyoperator included. This gives the transit operators thepossibility to modify the tariff information and for exampleinclude their own additional fees.If the tariff information is modified, the modifier MUST replacethe Network identification of the SIP tariff message with theirown identification innish CommunicationsRegulatory AuthorityItämerenkatu 3 APL 31300181 HelsinkiPuhelin 0295 390 100www.viestintävirasto.fiÖstersjögatan 3APB 313, FI-00181Helsingfors, FinlandTelefon 358 295 390 100www.kommunikationsverket.fiItämerenkatu 3AP.O. Box 313, FI-00181Helsinki, FinlandTelephone 358 295 390 100www.ficora.fi

P.O. Box 313, FI-00181 Helsinki, Finland Telephone 358 295 390 100 www.ficora.fi Finnish profile for SIP tariff interworking Annex 1 - applying the SIP tariff Viestintäviraston suosituksia 217/2016 S . Suositus 2 (7) 217/2016 S 30.9.2016 Viestintävirasto Kommunikationsverket Finnish Communications Regulatory Authority Itämerenkatu 3 A PL 313 00181 Helsinki Puhelin 0295 390 100 www .

Related Documents:

SIP SIP phones Blustar 8000i NA SIP SIP phones 9112i, 9133i, 480i Not Supported SIP SIP phones 673xi ( A673xi), 675xi ( A675xi) NA SIP SIP phones 6735i, 6737i ( A6735i, A6737i) NA SIP SIP phones 6739i NA SIP SIP phones 6863i, 6865i, 6867i NA SIP MiVoice Conference phone (UC360

C O N T E N T S Configuration of SIP Trunking for PSTN Access SIP-to-SIP 1 Finding Feature Information 1 Configuration of SIP Trunking for PSTN Access SIP-to-SIP Features 1 Configuring SIP Registration Proxy on Cisco UBE 3 Finding Feature Information 3 Registration Pass-Through Modes 4 End-to-End Mode 4 Peer-to-Peer Mode 5 Registration in Different Registrar Modes 7

How To Guide: SIP Trunking Configuration Using the SIP Trunk Page 6(19) 2.2 The SIP Trunk Page The SIP Trunk pages are found under SIP Trunks. Several SIP Trunk pages may be defined if you have several PBXs or Trunk Services. You need to purchase Additional Trunk Group licensees to get more than one SIP Trunk page. Details are found below. s d he n

To support SIP trunks through a SIP trunk service provider, the SIP Trunk Groups folder was added to the SIP Peers folder in DB Programming. To create a SIP Trunk Group for Fusion Connect Service Provider, navigate to System- Device and Feature Codes- SIP Peers- SIP Trunk Groups and right click in the right hand pane. Then select "Create SIP .

Call Flow Scenarios for Successful Calls This section describes call flows for the following scenarios, which illustrate successful calls: SIP Gateway-to-SIP Gateway—Call Setup and Disconnect, page 7-3 SIP Gateway-to-SIP Gateway—Call via SIP Redirect Server, page 7-6 SIP Gateway-to-SIP Gateway—Call via SIP Proxy Server, page 7-9

4. SIP, VVoIP and QoS 5. SIP and Media Security 6. STIR/SHAKEN and the 'identity' problem 7. Firewalls, NAT and Session Border Controllers 8. SIP Trunking 9. Testing, Troubleshooting and Interoperability 10. ENUM, Peering and Interconnect 11. SIP in the Cloud 12. SIP in Cellular networks 13. SIP and Fax over IP 14. SIP in UC, UCaaS and .

How to Guide: SIP Trunking Configuration using the SIP Trunks page 4 2.2 The SIP Trunk Page The SIP Trunk pages are found under SIP Trunks. Several SIP Trunk pages may be defined if you have several PBXs or Trunk Services. You need to purchase Additional Trunk Group licensees to get more than one SIP Trunk page. Details are found below. s d he Tru

In recent years, there has been an increasing amount of literature on . A large and growing body of literature has investigated . In recent years, several studies have focused on