{"type":"doc","content":[{"type":"paragraph","content":[{"text":"Table of Contents","type":"text","marks":[{"type":"strong"}]}]},{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"toc","parameters":{"macroParams":{"minLevel":{"value":"1"},"maxLevel":{"value":"6"},"outline":{"value":"false"},"style":{"value":"default"},"type":{"value":"list"},"printable":{"value":"false"}},"macroMetadata":{"macroId":{"value":"818cac1d-a284-4b3e-8ccc-3503e2d69ef0"},"schemaVersion":{"value":"1"},"title":"Table of Contents"}},"localId":"6aa3dc43-fcb1-423b-8bc8-9a275cffef0f"}},{"type":"paragraph"},{"type":"paragraph","content":[{"text":"Tel URI (","type":"text"},{"text":"RFC 3966","type":"text","marks":[{"type":"link","attrs":{"href":"http://www.ietf.org/rfc/rfc3966.txt"}}]},{"text":") is a unique identifier that is expressed using either an Address-of-Record or a Dial String. Feature F-1291 adds tel URI support to the IMG 2020. With the inclusion of this feature, the IMG 2020 can receive the tel URI information in a SIP request of an incoming call and pass the same tel URI information to the outgoing SIP leg. The tel URI will be separated into two parts: the phone number and the optional parameters. This will allow the phone number to be used for routing in the same way as for SIP URI while the optional parameters can still be sent out as received. The tel URI functionality is by default enabled and cannot be disabled. Refer to the information below.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"tel URI Supported Headers","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"Below is a list of the headers that support the tel URI functionality with a brief description of each.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Request-URI, From: Header, To: Header","type":"text","marks":[{"type":"strong"}]}]},{"type":"table","attrs":{"layout":"align-start","width":1121.0,"localId":"5718aeea-e6c7-4dfd-8774-8c24f5bd4995"},"content":[{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"background":"#f4f5f7","rowspan":1,"colwidth":[168.0]},"content":[{"type":"paragraph","marks":[{"type":"alignment","attrs":{"align":"center"}}],"content":[{"text":"Supported Header","type":"text","marks":[{"type":"strong"}]}]}]},{"type":"tableCell","attrs":{"colspan":1,"background":"#f4f5f7","rowspan":1,"colwidth":[953.0]},"content":[{"type":"paragraph","marks":[{"type":"alignment","attrs":{"align":"center"}}],"content":[{"text":" ","type":"text","marks":[{"type":"strong"}]}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[168.0]},"content":[{"type":"paragraph","content":[{"text":"Request-URI","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[953.0]},"content":[{"type":"paragraph","content":[{"text":"When a tel-URI is received in the incoming Request URI message, the tel-URI along with any optional parameters will be passed to the outgoing leg. Refer to the Call Trace below.","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[168.0]},"content":[{"type":"paragraph","content":[{"text":"From: Header","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[953.0]},"content":[{"type":"paragraph","content":[{"text":"When a tel-URI is received in the From: Header, the tel-URI along with any optional parameters will be passed to the outgoing leg. Refer to the Call Trace below.","type":"text"}]}]}]},{"type":"tableRow","content":[{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[168.0]},"content":[{"type":"paragraph","content":[{"text":"To: Header","type":"text"}]}]},{"type":"tableCell","attrs":{"colspan":1,"rowspan":1,"colwidth":[953.0]},"content":[{"type":"paragraph","content":[{"text":"When a tel-URI is received in the To: Header, the tel-URI along with any optional parameters will be passed to the outgoing leg. Refer to the Call Trace below.","type":"text"}]}]}]}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"P-Preferred-ID / P-Asserted ID","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"As described in ","type":"text"},{"text":"RFC 3325","type":"text","marks":[{"type":"link","attrs":{"href":"http://www.ietf.org/rfc/rfc3325.txt"}}]},{"text":", these headers along with the SIP Privacy Header should only be sent to a trusted entity. When SIP Privacy is set to id, it means the sender requests the removal of the P-Asserted-Identity header fields before being transmitted to an untrusted network. The IMG 2020 supports interworking the new tel-URI in the P-Preferred-ID and P-Asserted-ID. All SIP Privacy rules still apply. Refer to the Call Trace below.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"tel URI in Referred-By Header","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"The Referred-By header information is present in the incoming REFER message. When a tel-URI is received in the incoming Referred-By message, the tel-URI along with any optional parameters will be passed to the outgoing leg. Refer to the Call Trace below.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"tel URI in Remote-Party-ID Header","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"If the Remote-Party-ID Header tel URI Header is received on the incoming side, the Remote-Party-ID tel URI information is passed to the outgoing side only when SIP Privacy allows it. In the example call trace below, the Remote-Party-ID tel URI is received on the incoming leg but not passed to the outgoing leg.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"tel URI Interworking Call Trace","type":"text","marks":[{"type":"strong"}]}]},{"type":"codeBlock","content":[{"text":"CALL> 13:43:20.284 CALL(SIP) (00:18719:00) RCVD INVITE W/SDP from 10.129.45.244:5060 udp CSeq:1\n13:43:20.284 CALL(SIP) (00:18719:00) with Via sent-by: 10.129.45.244\n13:43:20.284 CALL(SIP) (00:18719:00) Call-id: 1-20583@10.129.45.244\n13:43:20.284 CALL(SIP) (00:18719:00) and Msg Size: 797\n13:43:20.284 CALL(SIP) (00:18719:00)\n ---> [10.129.45.244, 5060]\n INVITE tel:+15082222;phone-context=10.129.45.244 SIP/2.0\\r\\n\n Via: SIP/2.0/UDP 10.129.45.244:5060;branch=z9hG4bK-20583-1-0\\r\\n\n From: ;tag=20583SIPpTag091\\r\\n\n To: \\r\\n\n Call-ID: 1-20583@10.129.45.244\\r\\n\n CSeq: 1 INVITE\\r\\n\n Contact: sip:sipp@10.129.45.244:5060\\r\\n\n P-Asserted-Identity: \"test\" \\r\\n\n P-Asserted-Identity: \"tel508\"\\r\\n\n Remote-Party-ID: \"eric\";privacy=off;screen=no\\r\\n\n Privacy: id\\r\\n\n Max-Forwards: 70\\r\\n\n Referred-By: \\r\\n\n Subject: Performance Test\\r\\n\n Content-Type: application/sdp\\r\\n\n Content-Length: 221\\r\\n\n \\r\\n\n v=0\\r\\n\n o=user1 53655765 2353687637 IN IP4 10.129.45.244\\r\\n\n s=-\\r\\n\n c=IN IP4 10.129.45.244\\r\\n\n t=0 0\\r\\n\n m=audio 30000 RTP/AVP 0 101\\r\\n\n a=rtpmap:0 PCMU/8000\\r\\n\n a=sendrecv\\r\\n\n a=rtpmap:101 telephone-event/8000\\r\\n\n a=fmtp:101 0-11,16\\r\\n\n a=sendrecv\\r\\n\n \n13:43:20.284 CALL(SIP) (00:18719:00) SENT 100 Trying to 10.129.45.244:5060\n13:43:20.284 CALL(SIP) (00:18719:00)\n <--- [10.129.45.244, 5060 <- 10.129.55.194, 5060]\n SIP/2.0 100 Trying\\r\\n\n Via: SIP/2.0/UDP 10.129.45.244:5060;branch=z9hG4bK-20583-1-0;received=10.129.45.244\\r\\n\n Call-ID: 1-20583@10.129.45.244\\r\\n\n From: ;tag=20583SIPpTag091\\r\\n\n To: \\r\\n\n CSeq: 1 INVITE\\r\\n\n Server: Dialogic-SIP/2.1.0.182 BDN_Stgo 0\\r\\n\n Content-Length: 0\\r\\n\n \\r\\n\n \n13:43:20.284 CALL(SIP) (00:18719:00) SENT Route Control to L4\n13:43:20.284 CALL(L4) (00:18719:00) RCVD Route Control from SIP\n13:43:20.284 CALL(L4) (00:18719:00) Accessing Route Table 2\n13:43:20.284 CALL(L4) (00:18719:00) Accessing Resource Table 1\n13:43:20.284 CALL(L4) (00:18719:00) Hunting Algorithm is Round Robin\n13:43:20.284 CALL(L4) (00:18719:00) SENT Route Control Ack to SIP\n13:43:20.284 CALL(SIP) (00:18719:00) RCVD Route Control Ack from L4\n13:43:20.284 CALL(SIP) (00:18719:00) Session Group Profile ID is 1\n13:43:20.284 CALL(SIP) (00:18719:00) SENT Route Control to L4\n13:43:20.284 CALL(L4) (00:18719:00) RCVD Route Control from SIP\n13:43:20.284 CALL(L4) (00:18719:00) Accessing IP Bearer Profiles\n13:43:20.284 CALL(L4) (00:18719:00) Profile Id 1 (RG 769)\n13:43:20.284 CALL(L4) (00:15891:00) SENT Route Control Ack to SIP\n13:43:20.284 CALL(SIP) (00:18719:00) RCVD Route Control Ack from L4\n13:43:20.284 CALL(SIP) (00:18719:00) m line (audio) codec list: 0 101\n13:43:20.284 CALL(SIP) (00:18719:00) RTP Type: 0, name: PCMU, clk: 8000\n13:43:20.284 CALL(SIP) (00:18719:00) RTP Type: 101, name: telephone-event, clk:8000\n13:43:20.284 CALL(SIP) (00:18719:00) CODEC Negotiation Priority LOCAL\n13:43:20.284 CALL(SIP) (00:18719:00) SRTP configuration Disabled\n13:43:20.284 CALL(SIP) (00:18719:00) SDP Audio Codec Overlap Success\n13:43:20.284 CALL(SIP) (00:18719:00) Local Media Capability is Audio Only\n13:43:20.284 CALL(SIP) (00:18719:00) SENT iL3-L3 Reserve Resource Request to VPPL\n13:43:20.284 CALL(VPP) (00:18719:00) RCVD Reserve Resource [its 427] from L3P\n13:43:20.284 CALL(VPP) (00:18719:00) SENT Reserve Resource Request to CM\n13:43:20.284 CALL(XCM) (00:18719:00) LTS:3883 Processing RESERVE request for xCM_PACKET_AUDIO_CHANNEL\n13:43:20.284 CALL(XCM) (00:18719:00) SENT MEDAUDIO_MODM_CHAN_RESERVE_REQ chanType 1 groupId 0x1\n13:43:20.284 CALL(AUD) (00:11913:00) RCVD RESERVE REQ [TransID 1571297072; LTS 3883; GrpID 1]\n13:43:20.284 CALL(AUD) (00:11913:00) SENT RESERVE RESP [ResID x10010B47; CID 2887; TransID 1571297072, SUCCESS]\n13:43:20.284 CALL(XCM) (00:18719:00) LTS:3883 RCV :0x2f01(MEDAUDIO_MODM_CHAN_RE\n SERVE_RESP) in state:xCM_CHANNEL_RESERVING\n13:43:20.284 CALL(XCM) (00:18719:00) Sending message:0x2b17(XCM_CHANNEL_RESERVE_RSP), result=0x0\n13:43:20.284 CALL(VPP) (00:18719:00) RCVD Reserve Resp from CM\n13:43:20.284 CALL(VPP) (00:18719:00) SENT Reserve ACK (toPvid: x66) to L3P\n13:43:20.284 CALL(SIP) (00:18719:00) RCVD Reserve Resource ACK from VPPL\n13:43:20.284 CALL(SIP) (00:18719:00) 2: CPC (Default)\n13:43:20.284 CALL(SIP) (00:18719:00) Leg 0 associated with hndl(9511), LTS(3883)(span 8205 chan 11)\n13:43:20.284 CALL(SIP) (00:18719:00) SENT Setup to L4\n13:43:20.284 CALL(L4) (00:18719:00) RCVD Setup Ind from SIP\n13:43:20.284 CALL(L4) (00:18719:00)\n13:43:20.284 CALL(L4) (00:18719:00)\n13:43:20.284 CALL(L4) (00:18719:00) SENT RFS to GCL\n13:43:20.284 CALL(GCL) (00:18719:00) RCVD RFS DN=[15082222] ANI=[1234567] GN=[0] from L4\n13:43:20.284 CALL(GCL) (00:18719:00) DN NOA=[3]\n13:43:20.284 CALL(GCL) (00:18719:00) ANI APRI=[0],SI=[0],Category=[10]\n13:43:20.284 CALL(GCL) (00:18719:00) GN APRI=[0],SI=[0], NQI=[6]\n13:43:20.284 CALL(GCL) (00:18719:00) Incoming Channel Group = 10 [SIP_HMP_244]\n13:43:20.284 CALL(GCL) (00:18719:00) SENT Make Call Request to GCL\n13:43:20.284 CALL(GCL) (00:18719:01) SENT Route Control to L4\n13:43:20.284 CALL(L4) (00:18719:00) RCVD RFS response from GCL\n13:43:20.284 CALL(L4) (00:18719:00) RCVD Route Control from GCL\n13:43:20.284 CALL(L4) (00:18719:00) Accessing Route Table 9\n13:43:20.284 CALL(GCL) (00:18719:01) RCVD Route Control Ack (Mid Stream Router)from L4\n13:43:20.284 CALL(GCL) (00:18719:01) Outgoing Channel Group = 11 [SIP_HMP_245]\n13:43:20.284 CALL(GCL) (00:18719:01) SENT Route Control to L4\n13:43:20.284 CALL(L4) (00:18719:01) RCVD Route Control from GCL\n13:43:20.284 CALL(L4) (00:18719:01) Accessing Resource Table 1\n13:43:20.284 CALL(L4) (00:18719:01) Resource Group ID is 2\n13:43:20.284 CALL(L4) (00:18719:01) Hunting Algorithm is Round Robin\n13:43:20.294 CALL(GCL) (00:18719:01) RCVD CPE of ADDRESS INFO from L4\n13:43:20.294 CALL(GCL) (00:18719:01) Leg 1 associated with LTS(5479)(span 8255 chan 7)\n13:43:20.294 CALL(L4) (00:18719:01)\n13:43:20.294 CALL(L4) (00:18719:01)\n13:43:20.294 CALL(L4) (00:18719:01) SIP From UserName Bypassed: Enabled\n13:43:20.294 CALL(L4) (00:18719:01) SIP From UserName Bypassed: Enabled\n13:43:20.294 CALL(L4) (00:18719:01) SENT Outseize Ctrl to SIP\n13:43:20.294 CALL(SIP) (00:18719:01) RCVD Outseize Ctrl from L4\n13:43:20.294 CALL(SIP) (00:18719:01) SENT Route Control to L4\n13:43:20.294 CALL(L4) (00:18719:01) RCVD Route Control from SIP\n13:43:20.294 CALL(L4) (00:18719:01) Accessing GatewayId to IP Tables\n13:43:20.294 CALL(L4) (00:18719:01) Gateway ID is 1031\n13:43:20.294 CALL(L4) (00:15984:00) SENT Route Control Ack to SIP\n13:43:20.294 CALL(SIP) (00:18719:01) RCVD Route Control Ack from L4\n13:43:20.294 CALL(SIP) (00:18719:01) Session Group Profile ID is 1\n13:43:20.294 CALL(SIP) (00:18719:01) SENT Route Control to L4\n13:43:20.294 CALL(L4) (00:18719:01) RCVD Route Control from SIP\n13:43:20.294 CALL(L4) (00:18719:01) Accessing IP Bearer Profiles\n13:43:20.294 CALL(L4) (00:18719:01) Profile Id 1 (RG 769)\n13:43:20.294 CALL(L4) (00:15984:00) SENT Route Control Ack to SIP\n13:43:20.294 CALL(SIP) (00:18719:01) RCVD Route Control Ack from L4\n13:43:20.294 CALL(SIP) (00:18719:01) Remote Media Capability is audio Only\n13:43:20.294 CALL(SIP) (00:18719:01) Local Media Capability is Audio Only\n13:43:20.294 CALL(SIP) (00:18719:01) SENT iL3-L3 Reserve Resource Request to VPPL\n13:43:20.294 CALL(VPP) (00:18719:01) RCVD Reserve Resource [its 2023] from L3P\n13:43:20.294 CALL(VPP) (00:18719:01) SENT Reserve Resource Request to CM\n13:43:20.294 CALL(XCM) (00:18719:01) LTS:5479 Processing RESERVE request for xCM_PACKET_AUDIO_CHANNEL\n13:43:20.294 CALL(XCM) (00:18719:01) SENT MEDAUDIO_MODM_CHAN_RESERVE_REQ chanType 1 groupId 0x1\n13:43:20.294 CALL(AUD) (00:11914:00) RCVD RESERVE REQ [TransID 1509923024; LTS 5479; GrpID 1]\n13:43:20.294 CALL(AUD) (00:11914:00) SENT RESERVE RESP [ResID x10010B71; CID 2929; TransID 1509923024, SUCCESS]\n13:43:20.294 CALL(XCM) (00:18719:01) LTS:5479 RCV :0x2f01(MEDAUDIO_MODM_CHAN_RESERVE_RESP)\n in state:xCM_CHANNEL_RESERVING\n13:43:20.294 CALL(XCM) (00:18719:01) Sending message:0x2b17(XCM_CHANNEL_RESERVE_RSP), result=0x0\n13:43:20.294 CALL(VPP) (00:18719:01) RCVD Reserve Resp from CM\n13:43:20.294 CALL(VPP) (00:18719:01) SENT Reserve ACK (toPvid: x66) to L3P\n13:43:20.294 CALL(SIP) (00:18719:01) RCVD Reserve Resource ACK from VPPL\n13:43:20.294 CALL(SIP) (00:18719:01) REM TP port=5060 transport:0\n13:43:20.294 CALL(SIP) (00:00000:00) Unsupported Header Relaying Disabled\n13:43:20.294 CALL(SIP) (00:18719:01) Remote media capabilities:Audio local media capabilities:Audio\n13:43:20.294 CALL(SIP) (00:18719:01) SENT INVITE W/SDP to 10.129.45.245:5060 Cseq:1\n13:43:20.294 CALL(SIP) (00:18719:01) and Call-id: 1f11-1567-932012134320-BDN_Stgo-0-10.129.47.204\n13:43:20.294 CALL(SIP) (00:18719:01)\n <--- [10.129.45.245, 5060 <- 10.129.47.204, 5060]\n INVITE tel:+15082222;phone-context=10.129.45.244 SIP/2.0\\r\\n\n Via: SIP/2.0/UDP 10.129.47.204:5060;rport;branch=z9hG4bK-9e3-1349271800-9510-467\\r\\n\n Call-ID: 1f11-1567-932012134320-BDN_Stgo-0-10.129.47.204\\r\\n\n CSeq: 1 INVITE\\r\\n\n Max-Forwards: 70\\r\\n\n To: \\r\\n\n From: ;tag=95ffcd055e0f78f7d5d397020e89288df3b7c24e\\r\\n\n User-Agent: Dialogic-SIP/2.1.0.182 BDN_Stgo 0\\r\\n\n Timestamp: 10032012134320\\r\\n\n P-Asserted-Identity: \"tel508\"\\r\\n\n Privacy: id\\r\\n\n Contact: \\r\\n\n Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBS\n CRIBE, NOTIFY, INFO, REFER, UPDATE\\r\\n\n Supported: path, replaces, timer, tdialog\\r\\n\n Session-Expires: 1800\\r\\n\n Referred-By: \\r\\n\n Expires: 300\\r\\n\n Organization: Dialogic\\r\\n\n Content-Type: application/sdp\\r\\n\n Content-Length: 264\\r\\n\n \\r\\n\n v=0\\r\\n\n o=Dialogic_SDP 12489 0 IN IP4 10.129.47.204\\r\\n\n s=Dialogic-SIP\\r\\n\n c=IN IP4 10.129.47.205\\r\\n\n t=0 0\\r\\n\n m=audio 8056 RTP/AVP 0 18 4\\r\\n\n a=rtpmap:0 PCMU/8000\\r\\n\n a=rtpmap:18 G729/8000\\r\\n\n a=fmtp:18 annexb=yes\\r\\n\n a=rtpmap:4 G723/8000\\r\\n\n a=fmtp:4 bitrate=5.3\\r\\n\n a=silenceSupp:off - - - -\\r\\n","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Additional Information","type":"text","marks":[{"type":"strong"}]}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"The header containing tel URI is transparently transferred to the outgoing leg without any modifications except for the phone number separators which are removed.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If the tel URI is not present in the incoming Header, the IMG 2020 will continue to generate and pass a SIP-URI to the outgoing leg but not the tel URI.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"tel URI is enabled by default and cannot be disabled.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If a SIP/SIPS URI is the only header present in the incoming leg, only the SIP/SIPS URI will be transferred to the outgoing leg.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"If both a SIP/SIPS URI and tel URI are present in the incoming leg, both will be transferred to the outgoing leg.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Fax and Modem URI schemes described in RFC 3966 are not supported.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"tel URI for ISDN to SIP Call Interworking","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph","content":[{"text":"This feature (FR14356) adds tel URI for ISDN to SIP Call Interworking. When enabled, a receiving ISDN call would be interworked to SIP with the outgoing SIP INVITE using tel: URI as shown below:","type":"text"}]},{"type":"codeBlock","content":[{"text":"15:33:09.207 CALL(ISD) (00:00007:00) RCVD Setup from Network\n. . .\n15:33:09.217 CALL(SIP) (00:00007:01)\n <--- [172.21.0.112, 5070 <- 172.21.5.220, 5060]\n INVITE tel:4441234 SIP/2.0\\r\\n\n Via: SIP/2.0/UDP 172.21.5.220:5060;rport;branch=z9hG4bK-\n 5d0c-1408980789-21997-430\\r\\n\n Call-ID: 6d55-d81-725201415339-Node0-0-172.21.5.220\\r\\n","type":"text"}]},{"type":"paragraph","content":[{"text":"By default, this functionality is disabled. It will be read only in the SIP Default profile. To enable the tel URI usage in SIP INVITE for ISDN incoming call, user must create another SIP profile in which it will enable the \"Tel URI for Outgoing request URI for incoming ISDN\" property when selecting the value Enabled as shown below.","type":"text"}]},{"type":"mediaSingle","attrs":{"layout":"align-start","width":65.0},"content":[{"type":"media","attrs":{"width":468,"id":"2ce03836-491f-4f45-84c0-f77e699f15a1","collection":"contentId-50889167","type":"file","height":195}}]},{"type":"paragraph","content":[{"text":"For more details, refer to ","type":"text"},{"text":"SIP_ISDN Interworking","type":"text","marks":[{"type":"link","attrs":{"href":"/wiki/spaces/DIMG/pages/52134518"}}]},{"text":" topic.","type":"text"}]}],"version":1}

Browser not supported