VF-Italy Network Requirements and Technical Limitations Overview

Slide Note
Embed
Share

The document outlines the network requirements and technical constraints for VF-Italy's D-SIP, focusing on IMS network constraints, supported voice codecs, signaling protocols, and SIP access interfaces. It details the INVITE format for calls, codec requirements, DTMF support, signaling options, failover mechanisms for DNS queries, and rerouting processes in case of primary SBC unavailability. The document emphasizes the importance of codec support, signaling protocols, and failover strategies in maintaining communication services.

amarc
amarc Follow

Uploaded on Sep 10, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript

  1. Corporates D-SIP: Network Requirements and technical limitations. C-SBC: SIP ACCESS INTERFACE .

  2. Summary D-SIP requirements: VF-Italy: IMS network constraints VF-Italy: INVITE format for Originated Calls INVITE examples: INVITE Standard for Originated calls INVITE Standard for Terminated calls 2

  3. VF-Italy: IMS network constraints 3

  4. VF-Italy: interface description 1/2 Supported Voice Codecs G729 and G711: Both codecs must be supported and simultaneously included in the SDP for the originating call, G729 must be inserted as a first priority. If the above requirement is not fulfilled: G729-only - Fax and/or POS transmissions; NOT supported. - Calls towards with G711-only end-points; NOT supported. G711-only - Calls to/from G729-only end-points; NOT supported. - Calls to Hunting Group Call Queue Number of another Company (or your own). Such feature is configured in order to reach agents with G729-only, thus would not allow communication with G711- only endpoints; NOT supported. - Calls to SIP Phone, which makes a Call Transfer towards any target; NOT supported. DTMF RFC 4733: supported. VF-Italy supports but does not suggest In-band Tone. Preferred choice is Out-of-band Tone. SIP Info: NOT supported Fax Pass-through or T.38 Codec T38: T38 Supported only with a fallback to G711. Otherwise Fax to/from G711-only endpoints would not be possible. Codec G711: supported. Signaling: SDP Early Offer Early Offer: supported. Delayed Offer: NOT supported. 4

  5. VF-Italy: interface description 2/2 PROTOCOLS Signaling: SIP over UDP. Media: RTP over UDP. PORTS SIP: UDP port 5060. RTP: UDP port range from 10000 to 21999 (SBC Type I) UDP port range from 10002 to 59999 (SBC Type II) OPTION REQUEST SIP method OPTIONS: VF-Italy does not send SIP OPTIONS request messages. GNR VF will provide GNR that has to be configured on client s PBX during the certification process. SIP Access Interface SBC Type I has a single IP address at access side managing SIP, DNS and media traffic (RTP). SBC Type II has specific IP addresses dedicated to each access interface protocol; i.e. one IP for SIP Traffic, one for DNS and one or more for media (RTP). 5

  6. VF-Italy Failover DNS query & Rerouting SBC Primary 1. DNS query every T seconds towards SBC-Pri (DNS server for ims.vodafone.it domain resolution) CORE NETWORK Rerouting to SBC-Sec whenever DNS query reply is received from such a node instead of SBC-Pri PBX configured with a single Trunk (host = ims.vodafone.it) IP-PBX SBC Secondary DNS query every T seconds towards SBC-Sec (alternate DNS server for ims.vodafone.it domain resolution) As a recommended mechanism, IP-PBX sends, every T seconds (*), DNS query (type A) towards SBC-Pri IP address & SBC-Sec IP address (alternate) in order to resolve ims.vodafone.it domain. Normal condition: DNS queries are resolved via SBC-Pri. All outgoing calls are routed through SBC-Pri. Whenever SBC-Pri becomes unavailable: SBC-Pri cannot reply and DNS queries are resolved via SBC-Sec. According to the Failover mechanism all outgoing calls are re- routed through SBC-Sec. As soon as SBC-Pri becomes available again: DNS queries are resolved again via SBC-Pri as normal condition. All outgoing calls are then routed towards SBC-Pri again. (*) Configured on IP-PBX Every T 120 s (DNS, UDP port 53) 6

  7. VF-Italy Failover SIP OPTION message & Rerouting SBC Primary SIP OPTION message CORE NETWORK IP-PBX SBC Secondary SIP OPTION message As a recommended mechanism, IP-PBX sends, every T seconds (*), a SIP OPTION message towards SBC-Pri IP address & SBC-Sec IP address in order check the availability of the two interface Normal condition: Primary SBC answer with 200OK to the SIP Option All outgoing calls are routed through SBC-Pri. Whenever SBC-Pri becomes unavailable: SBC-Pri cannot reply to the SIP OPTION. According to the Failover mechanism IP-PBX sends outgoing calls to SBC-Sec. When SBC-Pri becomes available again: Primary SBC answer to the SIP Option. All outgoing calls are then routed towards SBC-Pri again. (*) Configured on IP-PBX Every T 120 s SIP OPTION 7

  8. VF-Italy Failover Rerouting for Timeout SBC Primary SIP INVITE message CORE NETWORK IP-PBX SBC Secondary SIP INVITE message , IP-PBX sends INVITE message towards SBC-Pri IP address Normal condition: Primary SBC answer with a SIP message All outgoing calls are routed through SBC-Pri. Whenever SBC-Pri becomes unavailable after a period to be defined configured on IP-PBX: SBC-Pri cannot reply to the SIP INVITE. After a period to be defined configured on IP-PBX,according to the Failover mechanism, IP-PBX sends outgoing calls to SBC-Sec. ASBC-Pri becomes available again: Primary SBC answer to the SIP INVITE. All outgoing calls are then routed towards SBC-Pri again. 8

  9. INVITE format Originated calls 9

  10. VF-Italy 1/2 Header SIP in INVITE Domain ims.vodafone.it Invite must include the domain ims.vodafone.it in the Request-URI. The escape code 0 must be present in the uri-user part in order to permit the outgoing call. Example: INVITE sip:03489000082@ims.vodafone.it:5060 SIP/2.0" FROM Header The FROM header field indicates the logical identity of the initiator of the request, it contains a URI and optionally a display name. This is the format: From:..<sip:+39...@domainName>;tag. Example: From: <sip:+390716400002@ims.vodafone.it>;tag=0ab... FROM must always be populated, it cannot be Anonymous Identity in the FROM is E164 of the calling Party. In case call is resulting from an incoming diversion, FROM will include the identity of the PBX entity generating the diversion. In case of GNR, FROM must be consistent with GNR prefix. FROM must be an existing extension in VF VPN. +39 prefix shall always be present. TO Header The TO header specifies the desired "logical" recipient of the request. The format must be the following: TO: ... <sip:...@domainName >. The escape code 0 must be present in the uri-user part in order to permit the outgoing call. Example: To: sip:03489000082@ims.vodafone.it Port will not be declared in TO header. CONTACT Header The CONTACT header field provides a SIP or SIPS URI that can be used to contact that specific instance of the UA for subsequent requests. The format must be the following: Contact: ... <sip:+39...@ip source:port;trasport protocol>;. Example: Contact :<sip:+390716400002@192.168.1.4:5060;transport=udp> 10

  11. VF-Italy 2/2 Header SIP in INVITE VIA Header The VIA header field indicates the transport used for the transaction and identifies the location where the response is to be sent. The format must be the following: Via:<SIP/2.0/UDP ip source:port;branch>. Example: VIA: SIP/2.0/UDP 192.168.10.39:5060;branch=z9hG4bK185d7be7" CALL-ID Header The CALL-ID header field acts as a unique identifier to group together a series of messages. It MUST be the same for all requests and responses sent by either UA in a dialog. Example: Call-ID: f81d4fae-7dec-11d0-a765-00a0c CSEQ Header The CSEQ header field serves to order transactions within a dialog, to provide a means to uniquely identify transactions, and to differentiate between new requests and request retransmissions. Two CSEQ header fields are considered equal if the sequence number and the request method are identical. Example: CSeq: 4711 INVITE Diversion Header / History Info Not supported (only direct calls can be sent to VF Network). 11

  12. VF-Italy Body SDP in INVITE Media Description The m-line has four parameters: Type of Media=audio. Port: contains the port where the media can be received. Transport: the transport protocol to use (RTP/AVP). Format-list contains payload types. Example: m:"audio 21400 RTP/AVP 18 0 8 Connection Info The c-line has three parameters: Network type: the only defined network type is the Internet IN. Address type: IP4 Network address: this parameter identifies the IP address where media is received (in this case PBX s IP address). Example: c: IN IP4 192.168.1.21 Media Attribute: List of codec supported The rtpmap attribute consists of four parameters: Payload type: carries the payload-type number as indicated in the m-line. Encoding name: the codec name. Clock rate: bits per second. Encoding parameters: media-specific parameters. Example: Media attribute: "rtpmap:18 G729/8000 Media attribute: "rtpmap:0 PCMU/8000 . Media attribute: "rtpmap:8 PCMA/8000 . P Time Packetization time must be configured to 20msec. 12

  13. Example of INVITE Standard Originated calls 13

  14. VF-Italy 1/2 INVITE Standard Originated calls Request-Line: INVITE sip:033xxxxxxxx@ims.vodafone.it SIP/2.0 Method: INVITE Request-URI: sip:033xxxxxxxx@ims.vodafone.it Request-URI User Part: 033xxxxxxxx Request-URI Host Part: ims.vodafone.it Message Header Via: SIP/2.0/UDP 1. x.x.x:5060;branch=z9hG4bK271522 Transport: UDP Sent-by Address: 1.x.x.x Sent-by port: 5060 Branch: z9hG4bK271522 Max-Forwards: 70 From: "08xxxxxxxxx" <sip:+3908xxxxxxxxx@ims.vodafone.it>;tag=as2734b9f2 SIP Display info: "08xxxxxxxxx" SIP from address: sip:+3908xxxxxxxx@ims.vodafone.it SIP from tag: as2734b9f2 To: <sip:033xxxxxxxx@ims.vodafone.it> SIP to address: sip:033xxxxxxxx@ims.vodafone.it Contact: <sip:+3908xxxxxxxxx@1.x.x.x:5060> Call-ID: 08baf9f0498f2e470008a73f6e82f6d8@ims.vodafone.it CSeq: 102 INVITE User-Agent: FPBX-2.11.0(1.8.12.0) Date: Mon, 27 Apr 2015 14:54:01 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Type: application/sdp Content-Length: 281 14

  15. VF-Italy 2/2 INVITE Standard Originated calls Message Body Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): 0000 105613363 105613363 IN IP4 192.x.x.x Session Name (s): Asterisk PBX 1.8.12.0 Connection Information (c): IN IP4 1.x.x.x Time Description, active time (t): 0 0 Media Description, name and address (m): audio 11674 RTP/AVP 18 8 101 Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): fmtp:101 0-16 Media Attribute (a): ptime:20 Media Attribute (a): sendrecv 15

  16. Examples of INVITE Standard Terminated calls 16

  17. VF-Italy 1/2 INVITE Standard Terminated calls (from PSTN) Request-Line: INVITE sip:+3908xxxxxxxxx;trunk- context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@3908xxxxxxxxx.corporate.vodafone.it SIP/2.0 Method: INVITE Request-URI: sip:+3908xxxxxxxxx;trunk- context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@3908xxxxxxxxx.corporate.vodafone.it Request-URI User Part: +3908xxxxxxxxx;trunk-context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx Request-URI Host Part: 3908xxxxxxxxx.corporate.vodafone.it Message Header Via: SIP/2.0/UDP 83.x.x.x:5060;branch=z9hG4bK0ctcpbp8610ln6ps47g6c7o6m7 Content-Length: 229 From: <sip:+3902xxxxxxxx@ims.vodafone.it;user=phone>;tag=SD0csf701-D__4D2047bccB22j SIP from address: sip:+3902xxxxxxxx@ims.vodafone.it;user=phone SIP from tag: SD0csf701-D__4D2047bccB22j To: <sip:+3908xxxxxxxxx@scscf.xxxxxx.cfx.ims.vodafone.it;user=phone> SIP to address: sip:+3908xxxxxxxxx@scscf.xxxxxxx.cfx.ims.vodafone.it;user=phone Call-ID: SD0csf701-dbb8f4bb07ff499e4d0f9500beee0d26-a8g9b23 CSeq: 1 INVITE Max-Forwards: 27 Request-Disposition: no-fork P-Asserted-Identity: <sip:+3902xxxxxxxx@ims.vodafone.it;user=phone;cpc=ordinary> P-Asserted-Identity: <tel:+3902xxxxxxxxx;cpc=ordinary> Contact: <sip:+3902xxxxxxxx@83.x.x.x:5060;transport=udp> Supported: 100rel,norefersub Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE P-Charging-Vector: icid-value=k0MpABCUsWyNmwABUnpYzAVdQugY;icid-generated-at=10.189.96.34 Content-Type: application/sdp Content-Disposition: session;handling=required RURI: <sip:+3908xxxxxxxxxx@ruriuser.uri:5060;transport=udp> Route: <sip:+3908xxxxxxxxx;trunk-context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@D- xxxxxxCPE1.ims.vodafone.it:5060;lr> 17

  18. VF-Italy 2/2 INVITE Standard Terminated calls (from PSTN) Message Body Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - 0 0 IN IP4 83.x.x.x Connection Information (c): IN IP4 83.x.x.x Time Description, active time (t): 0 0 Media Description, name and address (m): audio 12964 RTP/AVP 18 8 96 Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:96 telephone-event/8000 Media Attribute (a): ptime:20 Media Attribute (a): maxptime:20 18

  19. VF-Italy 1/2 INVITE Standard Terminated calls (from Mobile) Request-Line: INVITE sip:+3908xxxxxxxxx;trunk- context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@3908xxxxxxxxx.corporate.vodafone.it SIP/2.0 Method: INVITE Request-URI: sip:+3908xxxxxxxxx;trunk- context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@3908xxxxxxxxx.corporate.vodafone.it Request-URI User Part: +3908xxxxxxxxx;trunk-context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx Request-URI Host Part: 3908xxxxxxxxx.corporate.vodafone.it Message Header Via: SIP/2.0/UDP 83.x.x.x:5060;branch=z9hG4bKe9tn3bsu0ksf706f6pd143qe35 To: <sip:008xxxxxxxxx@ims.vodafone.it> SIP to address: sip:008xxxxxxxxxx@ims.vodafone.it From: +3902xxxxxxxx <sip:+3902xxxxxxxx@ims.vodafone.it>;tag=SD6s93c01-n7sr9np-21498- 1430382415830785477653 SIP Display info: +3902xxxxxxxxx SIP from address: sip:+3902xxxxxxxx@ims.vodafone.it SIP from tag: SD6s93c01-n7sr9np-21498-1430382415830785477653 Call-ID: SD6s93c01-9ec1d00a1b8e44b0e51d1ef7c7d0cae1-a8g9b23 CSeq: 1 INVITE Allow: ACK,BYE,CANCEL,INFO,INVITE Contact: <sip:@83.x.x.x:5060;transport=udp> Contact URI: sip:@83.x.x.x:5060;transport=udp Max-Forwards: 64 Accept: application/sdp P-Asserted-Identity: <tel:+3902xxxxxxxx> P-Charging-Vector: icid-value=08b957e6b3f621f24029719bc6f8cc4a P-Charging-Function-Addresses: ccf="aaa://cg.ims.vodafone.it";ccf="aaa://cg.ims.vodafone.it User-Agent: Lucent-SIPTRANS v2.2 Content-Length: 428 Content-Type: application/sdp RURI: <sip:+3908xxxxxxxxx@ruriuser.uri:5060;transport=udp Route: <sip:+3908xxxxxxxxx;trunk-context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@D- xxxxxCPE1.ims.vodafone.it:5060;lr> 19

  20. VF-Italy 2/2 INVITE Standard Terminated calls (from Mobile) Message Body Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): 0000 xxxxxxxxxx xxxxxxxxxxxx IN IP4 83.x.x.x Session Name (s): - Connection Information (c): IN IP4 83.x.x.x Time Description, active time (t): 0 0 Media Description, name and address (m): audio 21154 RTP/AVP 18 0 2 8 9 96 97 98 101 Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:2 G726-32/8000 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:9 G722/8000 Media Attribute (a): rtpmap:96 G726-40/8000 Media Attribute (a): rtpmap:97 G726-24/8000 Media Attribute (a): rtpmap:98 G726-16/8000 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 Media Attribute (a): ptime:20 Media Attribute (a): sendrecv 20

  21. VF-Italy INVITE Standard Terminated calls (from VF corporate)1/5 INVITE, in terminated call from VF corporate, can have two different format of FROM HEADER depending on the origin of the call. The two different format of from header are the following: From: +3902xxxxxxxx <tel:+390249459860>;tag=SDkkt4b01-n7sr9np-21499-143023049891352799304 From: +3906XXXXXXXX <sip:+3906XXXXXXXX@ims.vodafone.it>;tag=n7sr9np-5114-1520330081346879311591 Customer PBX has to be able to manage the two different format of FROM HEADER. 21

  22. VF-Italy 2/5 INVITE Standard Terminated calls (from VF corporate) From: <tel:....> Request-Line: INVITE sip:+3908xxxxxxxxx;trunk- context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@3908xxxxxxxxx.corporate.vodafone.it SIP/2.0 Method: INVITE Request-URI: sip:+3908xxxxxxxxx;trunk- context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@3908xxxxxxxxx.corporate.vodafone.it Request-URI User Part: +3908xxxxxxxxx;trunk-context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx Request-URI Host Part: 3908xxxxxxxxx.corporate.vodafone.it Message Header Via: SIP/2.0/UDP 83.x.x.x:5060;branch=z9hG4bKigrdhib279tpm56h4spfmkbat4 To: <sip:008xxxxxxxxx@ims.vodafone.it> SIP to address: sip:008xxxxxxxxxx@ims.vodafone.it From: +3902xxxxxxxx <tel:+390249459860>;tag=SDkkt4b01-n7sr9np-21499-143023049891352799304 SIP from tag: SDkkt4b01-n7sr9np-21499-143023049891352799304 Call-ID: SDkkt4b01-54da6a697d8759810992d308ab9c04cd-a8g9b23 CSeq: 1 INVITE Allow: ACK,BYE,CANCEL,INFO,INVITE Contact: <sip:@83.x.x.x:5060;transport=udp> Contact URI: sip:@83.x.x.x:5060;transport=udp Max-Forwards: 64 Accept: application/sdp P-Asserted-Identity: <tel:+3902xxxxxxxx> P-Charging-Vector: icid-value=49110ef321089297d8016a661096e524 P-Charging-Function-Addresses: ccf="aaa://cg.ims.vodafone.it";ccf="aaa://cg.ims.vodafone.it User-Agent: Lucent-SIPTRANS v2.2 Content-Length: 426 Content-Type: application/sdp RURI: <sip:+3908xxxxxxxxx@ruriuser.uri:5060;transport=udp> Route: <sip:+3908xxxxxxxxx;trunk-context=3908xxxxxxxxx.ims.vf.it;tgrp=tg3908xxxxxxxxx@D- xxxxxCPE1.ims.vodafone.it:5060;lr> 22

  23. VF-Italy 3/5 INVITE Standard Terminated calls (from VF corporate) Message Body Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): 0000 xxxxxxxxxx xxxxxxxxxxxx IN IP4 83.x.x.x Session Name (s): - Connection Information (c): IN IP4 83.x.x.x Time Description, active time (t): 0 0 Media Description, name and address (m): audio 16508 RTP/AVP 18 0 2 8 9 96 97 98 101 Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:2 G726-32/8000 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:9 G722/8000 Media Attribute (a): rtpmap:96 G726-40/8000 Media Attribute (a): rtpmap:97 G726-24/8000 Media Attribute (a): rtpmap:98 G726-16/8000 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 Media Attribute (a): ptime:20 Media Attribute (a): sendrecv 23

  24. VF-Italy 4/5 INVITE Standard Terminated calls (from VF corporate) From: <sip:....> Request-Line: INVITE sip:+3907xxxxxxxxx;trunk- context=3907xxxxxxx.ims.vf.it;tgrp=tg3907xxxxxxx@3907xxxxxxx.corporate.vodafone.it SIP/2.0 Method: INVITE Request-URI: sip:+3907xxxxxxxxx;trunk- context=3907xxxxxxx.ims.vf.it;tgrp=tg3907xxxxxxx@3907xxxxxxx.corporate.vodafone.it Request-URI User Part: +3907xxxxxxxxx;trunk-context=3907xxxxxxx.ims.vf.it;tgrp=tg3907xxxxxxx E.164 number (MSISDN): 3907xxxxxxxxx;trunk-context=3907xxxxxxx.ims.vf.it;tgrp=tg3907xxxxxxx Request-URI Host Part: 3907xxxxxxx.corporate.vodafone.it Message Header Via: SIP/2.0/UDP 83.xxx.xxx.xx:5060;branch=z9hG4bKi6by5rhopr058hy0bbyyhhori;Role=3;Hpt=8e68_16 Record-Route: <sip:83.xxx.xxx.xx:5060;transport=udp;lr;Hpt=8e68_16;CxtId=4;TRC=ffffffff-ffffffff;X- HwB2bUaCookie=13405> Call-ID: isbcMCAS-SIPSCH%002/1018+24664-311591@RMSCPc23-0-0 From: +3906xxxxxxxx <sip:+3906xxxxxxxx@ims.vodafone.it>;tag=n7sr9np-5114-1520330081346879311591 SIP Display info: +3906xxxxxxxx SIP from address: sip:+3906xxxxxxxx@ims.vodafone.it SIP from tag: n7sr9np-5114-1520330081346879311591 To: <sip:007xxxxxxxxx@ims.vodafone.it> SIP to address: sip:007xxxxxxxxx@ims.vodafone.it CSeq: 1 INVITE Accept: application/sdp Allow: ACK,BYE,CANCEL,INFO,INVITE,REFER Contact: <sip:83.xxx.xxx.xx:5060;transport=udp;Hpt=8e68_16;CxtId=4;TRC=ffffffff-ffffffff> Contact URI: sip:83.xxx.xxx.xx:5060;transport=udp;Hpt=8e68_16;CxtId=4;TRC=ffffffff-ffffffff Max-Forwards: 64 User-Agent: Nokia-SIPTRANS v2.2 P-Charging-Vector: icid-value="5e4489074441ceda8622aeb66d3ee00a.3729318881.286757258.110";orig- ioi=scscf.BOICP22.icp.ims.vodafone.it P-Asserted-Identity: <sip:+3906xxxxxxxx@83.xxx.xxx.xx> 24

  25. VF-Italy 5/5 INVITE Standard Terminated calls (from VF corporate) Content-Length: 282 Content-Type: application/sdp Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - xxxxxxxxx xxxxxxxxx IN IP4 83.xxx.xxx.xxx Session Name (s): SBC call Time Description, active time (t): 0 0 Media Description, name and address (m): audio 11462 RTP/AVP 18 0 8 101 Connection Information (c): IN IP4 83.xxx.xxx.xxx Media Attribute (a): rtpmap:18 G729/8000 Media Attribute (a): fmtp:18 annexb=no Media Attribute (a): rtpmap:0 PCMU/8000 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 Media Attribute (a): sendrecv 25

Related


Sustainable Waste Management Initiatives in Italy

Sustainable Waste Management Initiatives in Italy

khgs736
Integrating Adriatic Energy Markets: Italy's Regulatory Perspective

Integrating Adriatic Energy Markets: Italy's Regulatory Perspective

dshah
Technical Integration Meeting: DUNE Requirements Overview

Technical Integration Meeting: DUNE Requirements Overview

haye_ora
Comprehensive Technical Writing Workshop by John Cole at The University of Texas at Dallas

Comprehensive Technical Writing Workshop by John Cole at The University of Texas at Dallas

arre644
Network Slicing with OAI 5G CN Workshop Overview

Network Slicing with OAI 5G CN Workshop Overview

justice
Insights on Long-Term Care Policies in Italy: National Reforms to Local Changes

Insights on Long-Term Care Policies in Italy: National Reforms to Local Changes

azami
Enhancing Network Stability with Network Monitoring Systems

Enhancing Network Stability with Network Monitoring Systems

rosa_735
NHS Community Pharmacy Blood Pressure Check Service Technical Toolkit Overview

NHS Community Pharmacy Blood Pressure Check Service Technical Toolkit Overview

wilsey_f
Monumental Trees of Italy - A Natural Legacy of Grandeur and Cultural Significance

Monumental Trees of Italy - A Natural Legacy of Grandeur and Cultural Significance

michal
Rise of Mussolini in Italy and Weaknesses of the Liberal Monarchy

Rise of Mussolini in Italy and Weaknesses of the Liberal Monarchy

hemminger_e
Italy's Experience with Web Accessibility Directive Implementation

Italy's Experience with Web Accessibility Directive Implementation

marschall_a
Unification of Italy in the 19th Century: Risorgimento Movement

Unification of Italy in the 19th Century: Risorgimento Movement

ssuri
The Rise of Fascism in Italy: The Reign of Mussolini

The Rise of Fascism in Italy: The Reign of Mussolini

ann_lan
Discovering Italy: My Heritage Project by Carly Maree Saia

Discovering Italy: My Heritage Project by Carly Maree Saia

blanka
The Wine Industry in Italy: Trends and Acquisition Opportunities

The Wine Industry in Italy: Trends and Acquisition Opportunities

costales_a
Embracing Technician Commitment for Technical Excellence

Embracing Technician Commitment for Technical Excellence

livia
Women's Retirement Challenges in Italy: Insights from NDC and Pension Reforms

Women's Retirement Challenges in Italy: Insights from NDC and Pension Reforms

maxo_zac
Exploring Network Slicing in Future 5G Networks

Exploring Network Slicing in Future 5G Networks

lad_yah
Network Compression Techniques: Overview and Practical Issues

Network Compression Techniques: Overview and Practical Issues

heron
NAO Website Technical Discovery Summary

NAO Website Technical Discovery Summary

sophronia
Progress of Network Architecture Work in FG IMT-2020

Progress of Network Architecture Work in FG IMT-2020

lonan
Feasibility Study of Italy-France Cross-Border Intraday Trading

Feasibility Study of Italy-France Cross-Border Intraday Trading

amberros
Network Function Virtualization (NFV) Overview

Network Function Virtualization (NFV) Overview

brey983
Understanding NPDES Permits and Effluent Limitations

Understanding NPDES Permits and Effluent Limitations

kail_499

More Related Content