キャンセル
次の結果を表示 
次の代わりに検索 
もしかして: 
cancel
告知

JTAC-Mid-Career-Recruitment-2021.3

 AMATopBanner2021.4.23.JPG

 2021Apr.TopBanner.JPG

FAQ

 

Webex Calling - ローカルゲートウェイ コールフロー (WxC ↔ PRI)

851
閲覧回数
5
いいね!
0
コメント

 

はじめに

本ドキュメントは、Cisco Webex Calling クラウド電話システムに接続するローカルゲートウェイ (LGW: Local Gateway) のコールフローを紹介します。

 

本ドキュメントの内容は、2019 年 11 月 21 日時点の情報および IOS-XE 16.9.4 の構成を前提としています。

 

概要

本ドキュメントでは、Webex Calling アプリケーションや MPP などのエンドポイントから Webex Calling クラウド経由でローカルゲートウェイに発着信し、PRI 経由で PSTN に接続するコールフローについて説明します。ローカルゲートウェイと Webex Calling クラウド間は SIP で接続されます。

 

call.png

 

 

Webex Calling クラウドからの着信

Webex Calling アプリケーションや MPP から Webex Calling クラウド経由でローカルゲートウェイに着信するコールフローの例について紹介します。

  1. ローカルゲートウェイは、Webex Calling クラウドとの間で REGISTER 時に確立された TLS コネクションを使って、Webex Calling クラウドからの SIP INVITE を受信します。番号は E164 番号 (+81) で着信します。
  2. Q.931 SETUP を PRI に送信します。
  3. PRI から Q.931 ALERTING with PI (Progress Indicator) を受信します。Progress Indicator によって、PRI からのリングバックトーンを IP 側に流す準備を行います。
  4. SIP 183 Session Progress with SDP を Webex Calling クラウドに送信し、PRI からのリングバックトーンを送信します。
  5. PSTN 側の端末が応答すると、PRI から Q.931 CONNECT を受信します。
  6. SIP 200 OK を Webex Calling クラウドへ送信し、SIP ACK を受信して、通話を開始します。
  7. Webex Calling 側の端末が通話を切断すると、Webex Calling クラウドから SIP BYE を受信し、PRI へ DISCONNECT を送信して通話を終了します。

 

 

incoming.png

    

ローカルゲートウェイの SIP メッセージ例(一部内容は加工されています)

1751629: Oct 1 08:07:09.756: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+81312342222@192.168.43.197:5061;transport=tls;dtg=isr4331new8583_lgu SIP/2.0
Via: SIP/2.0/TLS 135.84.169.x:8934;branch=z9hG4bKn7edb11068t5p821m1d0.1
From: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>;tag=SDdcjla01-320162269-1569917124661-
To: "Test 2"<sip:+81312342222@59685258.jp10.bcld.webex.com;user=phone>
Call-ID: SDdcjla01-fbdaf5829818385d37b7e88cf513c692-agho7a0030
CSeq: 53288987 INVITE
Contact: <sip:+81312341111@135.84.169.x:8934;transport=tls>
P-Asserted-Identity: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>
Privacy: none
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Recv-Info: x-broadworks-client-session-info
Accept: application/dtmf-relay,application/media_control+xml,application/sdp,multipart/mixed
Supported:
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 390

v=0
o=BroadWorks 9326 1 IN IP4 135.84.169.x
s=-
c=IN IP4 135.84.169.x
t=0 0
m=audio 54882 RTP/SAVP 9 18 0 8 120 101
a=sendrecv
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:120 opus/48000/2
a=rtpmap:101 telephone-event/8000
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:HZz6rVxcacQIAtIAt+SY6cMle791FbBxtxp6PSWL

1751996: Oct 1 08:07:09.790: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0089
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x0081, '12341111'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '0312342222'
Plan:Unknown, Type:Unknown

1751997: Oct 1 08:07:09.791: //1926/4D27F4D5809B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 135.84.169.x:8934;branch=z9hG4bKn7edb11068t5p821m1d0.1
From: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>;tag=SDdcjla01-320162269-1569917124661-
To: "Test 2"<sip:+81312342222@59685258.jp10.bcld.webex.com;user=phone>
Date: Tue, 01 Oct 2019 08:07:09 GMT
Call-ID: SDdcjla01-fbdaf5829818385d37b7e88cf513c692-agho7a0030
CSeq: 53288987 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-16.9.4
Session-ID: 00000000000000000000000000000000;remote=7579a5dac1475fc29b4db037c8c4aa5f
Content-Length: 0

1751999: Oct 1 08:07:09.896: ISDN Se0/1/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8089
Channel ID i = 0xA98381
Exclusive, Channel 1

1752011: Oct 1 08:07:10.824: ISDN Se0/1/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x8089
Progress Ind i = 0x8488 - In-band info or appropriate now available

1752176: Oct 1 08:07:10.844: //1926/4D27F4D5809B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/TLS 135.84.169.x:8934;branch=z9hG4bKn7edb11068t5p821m1d0.1
From: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>;tag=SDdcjla01-320162269-1569917124661-
To: "Test 2"<sip:+81312342222@59685258.jp10.bcld.webex.com;user=phone>;tag=6BFB173-A
Date: Tue, 01 Oct 2019 08:07:09 GMT
Call-ID: SDdcjla01-fbdaf5829818385d37b7e88cf513c692-agho7a0030
CSeq: 53288987 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:0312342222@192.168.43.197>
Contact: <sip:+81312342222@192.168.43.197:5061;transport=tls>
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-16.9.4
Session-ID: a44541b42b0155019846302c0578b2fb;remote=7579a5dac1475fc29b4db037c8c4aa5f
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 325

v=0
o=CiscoSystemsSIP-GW-UserAgent 2495 3974 IN IP4 192.168.43.197
s=SIP Call
c=IN IP4 192.168.43.197
t=0 0
m=audio 8050 RTP/SAVP 0 101
c=IN IP4 192.168.43.197
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:PPYOuFcS/1HJZOgKeaP/9unu6lMrKg/dgGDPCfDb

1752178: Oct 1 08:07:13.003: ISDN Se0/1/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x8089

1752180: Oct 1 08:07:13.004: ISDN Se0/1/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0089

1752249: Oct 1 08:07:13.012: //1926/4D27F4D5809B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TLS 135.84.169.x:8934;branch=z9hG4bKn7edb11068t5p821m1d0.1
From: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>;tag=SDdcjla01-320162269-1569917124661-
To: "Test 2"<sip:+81312342222@59685258.jp10.bcld.webex.com;user=phone>;tag=6BFB173-A
Date: Tue, 01 Oct 2019 08:07:09 GMT
Call-ID: SDdcjla01-fbdaf5829818385d37b7e88cf513c692-agho7a0030
CSeq: 53288987 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:0312342222@192.168.43.197>
Contact: <sip:+81312342222@192.168.43.197:5061;transport=tls>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-16.9.4
Cisco-Gcid: 4D292DBE-E359-11E9-809E-C6D4898AAC8A
Session-ID: a44541b42b0155019846302c0578b2fb;remote=7579a5dac1475fc29b4db037c8c4aa5f
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 325

v=0
o=CiscoSystemsSIP-GW-UserAgent 2495 3974 IN IP4 192.168.43.197
s=SIP Call
c=IN IP4 192.168.43.197
t=0 0
m=audio 8050 RTP/SAVP 0 101
c=IN IP4 192.168.43.197
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:PPYOuFcS/1HJZOgKeaP/9unu6lMrKg/dgGDPCfDb

1752286: Oct 1 08:07:13.689: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+81312342222@192.168.43.197:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 135.84.169.x:8934;branch=z9hG4bK1d092d0050hdjc1p2cv0.1
From: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>;tag=SDdcjla01-320162269-1569917124661-
To: "Test 2"<sip:+81312342222@59685258.jp10.bcld.webex.com;user=phone>;tag=6BFB173-A
Call-ID: SDdcjla01-fbdaf5829818385d37b7e88cf513c692-agho7a0030
CSeq: 53288987 ACK
Contact: <sip:+81312341111@135.84.169.x:8934;transport=tls>
Max-Forwards: 69
Content-Length: 0

1753400: Oct 1 08:07:44.917: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:+81312342222@192.168.43.197:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 135.84.169.x:8934;branch=z9hG4bK1d092d0050hdjc1p2cv0cd38b0if0.1
From: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>;tag=SDdcjla01-320162269-1569917124661-
To: "Test 2"<sip:+81312342222@59685258.jp10.bcld.webex.com;user=phone>;tag=6BFB173-A
Call-ID: SDdcjla01-fbdaf5829818385d37b7e88cf513c692-agho7a0030
CSeq: 53288991 BYE
Max-Forwards: 69
Content-Length: 0

1753524: Oct 1 08:07:44.932: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TLS 135.84.169.x:8934;branch=z9hG4bK1d092d0050hdjc1p2cv0cd38b0if0.1
From: "Test 1"<sip:+81312341111@135.84.169.x;user=phone>;tag=SDdcjla01-320162269-1569917124661-
To: "Test 2"<sip:+81312342222@59685258.jp10.bcld.webex.com;user=phone>;tag=6BFB173-A
Date: Tue, 01 Oct 2019 08:07:44 GMT
Call-ID: SDdcjla01-fbdaf5829818385d37b7e88cf513c692-agho7a0030
Server: Cisco-SIPGateway/IOS-16.9.4
CSeq: 53288991 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=1646,OS=124320,PR=1562,OR=118160,PL=0,JI=0,LA=0,DU=31
Session-ID: 7579a5dac1475fc29b4db037c8c4aa5f;remote=a44541b42b0155019846302c0578b2fb
Content-Length: 0

1753527: Oct 1 08:07:44.964: ISDN Se0/1/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0089
Cause i = 0x8090 - Normal call clearing

1753528: Oct 1 08:07:45.072: ISDN Se0/1/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8089
Locking Shift to Codeset 6
Codeset 6 IE 0x1 i = 0x82, '9'

1753529: Oct 1 08:07:45.073: ISDN Se0/1/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0089

 

  

Webex Calling クラウドへの発信

PSTN の端末がローカルゲートウェイ経由で Webex Calling アプリケーションや MPP に発信するコールフローの例について紹介します。

  1. PSTN が契約されている PRI の番号にダイヤルし、ローカルゲートウェイは PRI から Q.931 SETUP を受信します。
  2. ローカルゲートウェイは、Webex Calling クラウドとの間で REGISTER 時に確立された TLS コネクションを使って、Webex Calling クラウドへ SIP INVITE を送信します。番号は E164 番号 (+81) で送信します。
  3. REGISTER 時と同様、SIP 401 Unauthorized レスポンスでチャレンジコードを受信します。
  4. 再度レスポンスコードを付与して INVITE を Webex Cloud へ送信します。
  5. Webex Calling 側の端末に着信すると、SIP 180 Ringing を受信します。
  6. PRI へ Q.931 ALERTING を送信し、PSTN 側の端末にリングバックトーンが流れます(リングバックトーンは PSTN 網で生成します)。
  7. Webex Calling Cloud 側の端末が応答すると、SIP 200 OK レスポンスを受信し、SIP ACK を送信します。
  8. PRI へ Q.931 CONNECT を送信し、通話が確立されます。
  9. PRI 側の端末が通話を切断すると、PRI から DISCONNECT を受信し、Webex Calling クラウドへ SIP BYE を送信して通話を終了します。

 

outgoiing.png

 

ローカルゲートウェイの SIP メッセージ例(一部内容は加工されています)

1786369: Oct 1 08:16:54.614: ISDN Se0/1/0:23 Q931: RX <- SETUP pd = 8 callref = 0x0079 
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA193040000
Preferred, Channel 4
Calling Party Number i = 0x0081, '0312342222'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '12341111'
Plan:Unknown, Type:Unknown

1786657: Oct 1 08:16:54.648: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:+81312341111@59685258.jp10.bcld.webex.com:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CB10CC
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>
Date: Tue, 01 Oct 2019 08:16:54 GMT
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2848077008-3814330857-2150764723-3329171744
User-Agent: Cisco-SIPGateway/IOS-16.9.4
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1569917814
Contact: <sip:0312342222@192.168.43.197:5061;transport=tls>
Expires: 180
Allow-Events: telephone-event
Cisco-Gcid: A9C234D0-E35A-11E9-8032-10B3C66F2120
P-Asserted-Identity: <sip:0312342222@192.168.43.197>
Session-ID: 8ac3ebd0a08855289b1fac90ca5c3b4b;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 337

v=0
o=CiscoSystemsSIP-GW-UserAgent 5000 8338 IN IP4 192.168.43.197
s=SIP Call
c=IN IP4 192.168.43.197
t=0 0
m=audio 8054 RTP/SAVP 0 101
c=IN IP4 192.168.43.197
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:BTbPD9nW+zP4oE8WDhztd0rYcYrQ78jLOHy9JBqm
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

1786659: Oct 1 08:16:54.649: ISDN Se0/1/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x8079
Channel ID i = 0xA993040000
Exclusive, Channel 4

1786671: Oct 1 08:16:54.788: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CB10CC
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
CSeq: 101 INVITE
Timestamp: 1569917814
Content-Length: 0

1786688: Oct 1 08:16:55.010: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CB10CC
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>;tag=SD7dcbe99-282988187-1569917709730
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
CSeq: 101 INVITE
Timestamp: 1569917814
WWW-Authenticate: DIGEST realm="BroadWorks",qop="auth",nonce="BroadWorksXk17kgxiaTkbfpbbBW",algorithm=MD5
Content-Length: 0

1786778: Oct 1 08:16:55.018: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:+81312341111@59685258.jp10.bcld.webex.com:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CB10CC
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>;tag=SD7dcbe99-282988187-1569917709730
Date: Tue, 01 Oct 2019 08:16:54 GMT
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 00000000000000000000000000000000;remote=8ac3ebd0a08855289b1fac90ca5c3b4b
Content-Length: 0

1786780: Oct 1 08:16:55.020: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:+81312341111@59685258.jp10.bcld.webex.com:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CC1F40
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>
Date: Tue, 01 Oct 2019 08:16:55 GMT
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2848077008-3814330857-2150764723-3329171744
User-Agent: Cisco-SIPGateway/IOS-16.9.4
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1569917815
Contact: <sip:+81312342222@192.168.43.197:5061;transport=tls>
Expires: 180
Allow-Events: telephone-event
Authorization: Digest username="isr4331new8583_LGU",realm="BroadWorks",uri="sips:+81312341111@59685258.jp10.bcld.webex.com:5061",response="f4bcaeac3680da6aa668099e234c2e0c",nonce="BroadWorksXk17kgxiaTkbfpbbBW",cnonce="826BD806",qop=auth,algorithm=MD5,nc=00000001
Cisco-Gcid: A9C234D0-E35A-11E9-8032-10B3C66F2120
P-Asserted-Identity: <sip:0312342222@192.168.43.197>
Session-ID: 8ac3ebd0a08855289b1fac90ca5c3b4b;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 337

v=0
o=CiscoSystemsSIP-GW-UserAgent 5000 8338 IN IP4 192.168.43.197
s=SIP Call
c=IN IP4 192.168.43.197
t=0 0
m=audio 8054 RTP/SAVP 0 101
c=IN IP4 192.168.43.197
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:BTbPD9nW+zP4oE8WDhztd0rYcYrQ78jLOHy9JBqm
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

1786793: Oct 1 08:16:55.164: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CC1F40
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
CSeq: 102 INVITE
Timestamp: 1569917815
Content-Length: 0

1786810: Oct 1 08:16:55.368: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CC1F40
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>;tag=SD7dcbe99-473308389-1569917710086
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
CSeq: 102 INVITE
Timestamp: 1569917815
Supported:
Contact: <sip:+81312341111@135.84.169.x:8934;transport=tls>
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Content-Length: 0

1786836: Oct 1 08:16:55.372: ISDN Se0/1/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x8079

1786873: Oct 1 08:16:58.664: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CC1F40
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>;tag=SD7dcbe99-422027280-1569917713522
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
CSeq: 102 INVITE
Timestamp: 1569917815
Supported:
Contact: <sip:+81312341111@135.84.169.x:8934;transport=tls>
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept: application/dtmf-relay,application/media_control+xml,application/sdp
Content-Type: application/sdp
Content-Length: 264

v=0
o=BroadWorks 9828 1 IN IP4 135.84.169.x
s=-
c=IN IP4 135.84.169.x
t=0 0
m=audio 54886 RTP/SAVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:bZbp87OjJSWTJukWO52uNhTy0USW7rYLg2SEM4on

1787140: Oct 1 08:16:58.694: ISDN Se0/1/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x8079

1787141: Oct 1 08:16:58.695: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:+81312341111@135.84.169.x:8934;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CDF23
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>;tag=SD7dcbe99-422027280-1569917713522
Date: Tue, 01 Oct 2019 08:16:55 GMT
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0

1787607: Oct 1 08:16:58.936: ISDN Se0/1/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0079

1804904: Oct 1 08:17:08.200: ISDN Se0/1/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x0079
Cause i = 0x8090 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available

1804993: Oct 1 08:17:08.215: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:+81312341111@135.84.169.x:8934;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CE1481
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>;tag=SD7dcbe99-422027280-1569917713522
Date: Tue, 01 Oct 2019 08:16:55 GMT
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
User-Agent: Cisco-SIPGateway/IOS-16.9.4
Max-Forwards: 70
Timestamp: 1569917828
CSeq: 103 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=474,OS=99540,PR=448,OR=94080,PL=0,JI=0,LA=0,DU=9
Session-ID: ;remote=
Content-Length: 0

1805073: Oct 1 08:17:08.262: ISDN Se0/1/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x8079

1805128: Oct 1 08:17:08.295: ISDN Se0/1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0079

1805272: Oct 1 08:17:08.391: //1942/A9C234D08032/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.43.197:5061;x-route-tag="tgrp:ISDN";branch=z9hG4bK7CE1481
From: <sip:0312342222@59685258.jp10.bcld.webex.com;otg=isr4331new8583_lgu>;tag=6C899F1-246F
To: <sip:+81312341111@59685258.jp10.bcld.webex.com>;tag=SD7dcbe99-422027280-1569917713522
Call-ID: A9C4CCC6-E35A11E9-80ACC6D4-898AAC8A@192.168.43.197
Timestamp: 1569917828
CSeq: 103 BYE
Content-Length: 0

  

参考情報