Advertisement
pavelsc

SIP.js 621 FF62

Oct 17th, 2018
127
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 21.16 KB | None | 0 0
  1. Wed Oct 17 2018 17:10:32 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  2.  
  3. REGISTER sip:sip.example.com SIP/2.0
  4.  
  5. Via: SIP/2.0/WSS tk4i9toum5sf.invalid;branch=z9hG4bK8600807
  6.  
  7. Max-Forwards: 70
  8.  
  9. To: <sip:internal.device-6564@sip.example.com>
  10.  
  11. From: <sip:internal.device-6564@sip.example.com>;tag=9693sv8iih
  12.  
  13. Call-ID: jinl1cnh8ig1l2vv1pe69b
  14.  
  15. CSeq: 3303 REGISTER
  16.  
  17. Authorization: Digest algorithm=MD5, username="internal.device-6564", realm="sip.example.com", nonce="W8dD4lvHQrYb2vdquizIwl4LJoxZmaFl", uri="sip:sip.example.com", response="f0b3922e4303385cf7806bbb065751df"
  18.  
  19. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:0a855fba-d4ef-4969-96d0-fcd0b13c0edb>";expires=600
  20.  
  21. Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
  22.  
  23. Supported: path, gruu, outbound
  24.  
  25. User-Agent: SIP.js/0.11.4
  26.  
  27. Content-Length: 0
  28.  
  29.  
  30.  
  31.  
  32. sip-0.11.4.js:586:5
  33. Wed Oct 17 2018 17:10:32 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  34.  
  35. SIP/2.0 200 OK
  36.  
  37. Via: SIP/2.0/WSS tk4i9toum5sf.invalid;branch=z9hG4bK8600807;rport=9474;received=95.15.117.16
  38.  
  39. To: <sip:internal.device-6564@sip.example.com>;tag=7224485d55e1d1f43dfe3a4d724dce9c.02d4
  40.  
  41. From: <sip:internal.device-6564@sip.example.com>;tag=9693sv8iih
  42.  
  43. Call-ID: jinl1cnh8ig1l2vv1pe69b
  44.  
  45. CSeq: 3303 REGISTER
  46.  
  47. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>;expires=20;received="sip:95.15.117.16:9474;transport=ws";+sip.instance="<urn:uuid:0a855fba-d4ef-4969-96d0-fcd0b13c0edb>";reg-id=1
  48.  
  49. Server: MS Lync
  50.  
  51. Content-Length: 0
  52.  
  53.  
  54.  
  55.  
  56. sip-0.11.4.js:586:5
  57.  
  58. Wed Oct 17 2018 17:10:36 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  59.  
  60. INVITE sip:internal.device-6564@10.0.14.88:5068 SIP/2.0
  61.  
  62. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  63.  
  64. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  65.  
  66. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.0
  67.  
  68. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  69.  
  70. Max-Forwards: 69
  71.  
  72. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  73.  
  74. To: <sip:internal.device-6564@10.0.14.88:5068>
  75.  
  76. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  77.  
  78. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  79.  
  80. CSeq: 102 INVITE
  81.  
  82. User-Agent: Staging PBX
  83.  
  84. Date: Wed, 17 Oct 2018 14:10:36 GMT
  85.  
  86. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
  87.  
  88. Supported: replaces
  89.  
  90. Content-Type: application/sdp
  91.  
  92. Content-Length: 624
  93.  
  94.  
  95.  
  96. v=0
  97.  
  98. o=root 1859926276 1859926276 IN IP4 18.148.13.82
  99.  
  100. s=Staging PBX
  101.  
  102. c=IN IP4 18.148.13.82
  103.  
  104. t=0 0
  105.  
  106. m=audio 50366 RTP/SAVPF 0 8 3 101
  107.  
  108. a=maxptime:150
  109.  
  110. a=rtpmap:0 PCMU/8000
  111.  
  112. a=rtpmap:8 PCMA/8000
  113.  
  114. a=rtpmap:3 GSM/8000
  115.  
  116. a=rtpmap:101 telephone-event/8000
  117.  
  118. a=fmtp:101 0-16
  119.  
  120. a=sendrecv
  121.  
  122. a=rtcp:50367
  123.  
  124. a=rtcp-mux
  125.  
  126. a=setup:actpass
  127.  
  128. a=fingerprint:sha-1 B1:CD:F6:15:4C:27:6A:F0:B0:24:AC:8B:3C:C4:23:F7:22:B5:B0:C0
  129.  
  130. a=ice-ufrag:5x1P9JYz
  131.  
  132. a=ice-pwd:G80l7OMrK668qIw996TMCHYXAV
  133.  
  134. a=candidate:62HXkmKaZqN6SxDo 1 UDP 2130706431 18.148.13.82 50366 typ host
  135.  
  136. a=candidate:62HXkmKaZqN6SxDo 2 UDP 2130706430 18.148.13.82 50367 typ host
  137.  
  138.  
  139. sip-0.11.4.js:586:5
  140. Wed Oct 17 2018 17:10:36 GMT+0300 (Moscow Standard Time) | sip.sipmessage | header "Content-Disposition" not present sip-0.11.4.js:586:5
  141. Wed Oct 17 2018 17:10:36 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  142.  
  143. SIP/2.0 100 Trying
  144.  
  145. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.0
  146.  
  147. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  148.  
  149. To: <sip:internal.device-6564@10.0.14.88:5068>
  150.  
  151. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  152.  
  153. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  154.  
  155. CSeq: 102 INVITE
  156.  
  157. Supported: outbound
  158.  
  159. User-Agent: SIP.js/0.11.4
  160.  
  161. Content-Length: 0
  162.  
  163.  
  164.  
  165.  
  166. sip-0.11.4.js:586:5
  167. Wed Oct 17 2018 17:10:36 GMT+0300 (Moscow Standard Time) | sip.dialog | new UAS dialog created with status EARLY sip-0.11.4.js:586:5
  168. Wed Oct 17 2018 17:10:36 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  169.  
  170. SIP/2.0 180 Ringing
  171.  
  172. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  173.  
  174. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  175.  
  176. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.0
  177.  
  178. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  179.  
  180. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=oa1r8gd20v
  181.  
  182. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  183.  
  184. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  185.  
  186. CSeq: 102 INVITE
  187.  
  188. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>
  189.  
  190. Supported: outbound
  191.  
  192. User-Agent: SIP.js/0.11.4
  193.  
  194. Content-Length: 0
  195.  
  196.  
  197.  
  198.  
  199. sip-0.11.4.js:586:5
  200. Wed Oct 17 2018 17:10:36 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  201.  
  202. INVITE sip:internal.device-6564@95.15.117.16 SIP/2.0
  203.  
  204. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  205.  
  206. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  207.  
  208. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.1
  209.  
  210. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  211.  
  212. Max-Forwards: 69
  213.  
  214. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  215.  
  216. To: <sip:internal.device-6564@10.0.14.88:5068>
  217.  
  218. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  219.  
  220. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  221.  
  222. CSeq: 102 INVITE
  223.  
  224. User-Agent: Staging PBX
  225.  
  226. Date: Wed, 17 Oct 2018 14:10:36 GMT
  227.  
  228. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
  229.  
  230. Supported: replaces
  231.  
  232. Content-Type: application/sdp
  233.  
  234. Content-Length: 624
  235.  
  236.  
  237.  
  238. v=0
  239.  
  240. o=root 1859926276 1859926276 IN IP4 18.148.13.82
  241.  
  242. s=Staging PBX
  243.  
  244. c=IN IP4 18.148.13.82
  245.  
  246. t=0 0
  247.  
  248. m=audio 50366 RTP/SAVPF 0 8 3 101
  249.  
  250. a=maxptime:150
  251.  
  252. a=rtpmap:0 PCMU/8000
  253.  
  254. a=rtpmap:8 PCMA/8000
  255.  
  256. a=rtpmap:3 GSM/8000
  257.  
  258. a=rtpmap:101 telephone-event/8000
  259.  
  260. a=fmtp:101 0-16
  261.  
  262. a=sendrecv
  263.  
  264. a=rtcp:50367
  265.  
  266. a=rtcp-mux
  267.  
  268. a=setup:actpass
  269.  
  270. a=fingerprint:sha-1 B1:CD:F6:15:4C:27:6A:F0:B0:24:AC:8B:3C:C4:23:F7:22:B5:B0:C0
  271.  
  272. a=ice-ufrag:5x1P9JYz
  273.  
  274. a=ice-pwd:G80l7OMrK668qIw996TMCHYXAV
  275.  
  276. a=candidate:62HXkmKaZqN6SxDo 1 UDP 2130706431 18.148.13.82 50366 typ host
  277.  
  278. a=candidate:62HXkmKaZqN6SxDo 2 UDP 2130706430 18.148.13.82 50367 typ host
  279.  
  280.  
  281. sip-0.11.4.js:586:5
  282. Wed Oct 17 2018 17:10:36 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  283.  
  284. SIP/2.0 482 Loop Detected
  285.  
  286. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.1
  287.  
  288. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  289.  
  290. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=knmc3d0pld
  291.  
  292. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  293.  
  294. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  295.  
  296. CSeq: 102 INVITE
  297.  
  298.  
  299.  
  300.  
  301. sip-0.11.4.js:586:5
  302. Wed Oct 17 2018 17:10:37 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  303.  
  304. ACK sip:internal.device-6564@95.15.117.16 SIP/2.0
  305.  
  306. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.1
  307.  
  308. Max-Forwards: 69
  309.  
  310. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  311.  
  312. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=knmc3d0pld
  313.  
  314. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  315.  
  316. CSeq: 102 ACK
  317.  
  318. Content-Length: 0
  319.  
  320.  
  321.  
  322.  
  323. sip-0.11.4.js:586:5
  324. Wed Oct 17 2018 17:10:40 GMT+0300 (Moscow Standard Time) | sip.dialog | dialog 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600oa1r8gd20vas49420a68 changed to CONFIRMED state sip-0.11.4.js:586:5
  325. Wed Oct 17 2018 17:10:40 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | SessionDescriptionHandlerOptions: {"constraints":{},"peerConnectionOptions":{}} sip-0.11.4.js:586:5
  326. Wed Oct 17 2018 17:10:40 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | initPeerConnection sip-0.11.4.js:586:5
  327. Wed Oct 17 2018 17:10:40 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | New peer connection created sip-0.11.4.js:586:5
  328. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | track added sip-0.11.4.js:586:5
  329. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | acquiring local media sip-0.11.4.js:586:5
  330. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | acquired local media streams sip-0.11.4.js:586:5
  331. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | RTCIceGatheringState changed: gathering sip-0.11.4.js:586:5
  332. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate received: candidate:0 1 UDP 2122252543 10.6.1.10 52128 typ host sip-0.11.4.js:586:5
  333. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate received: candidate:2 1 UDP 2122187007 192.168.0.10 52129 typ host sip-0.11.4.js:586:5
  334. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate received: candidate:4 1 TCP 2105524479 10.6.1.10 9 typ host tcptype active sip-0.11.4.js:586:5
  335. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate received: candidate:5 1 TCP 2105458943 192.168.0.10 9 typ host tcptype active sip-0.11.4.js:586:5
  336. Wed Oct 17 2018 17:10:41 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate received: candidate:3 1 UDP 1685987327 95.15.117.16 52129 typ srflx raddr 192.168.0.10 rport 52129 sip-0.11.4.js:586:5
  337. Wed Oct 17 2018 17:10:46 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | RTCIceChecking Timeout Triggered after 5000 milliseconds sip-0.11.4.js:586:5
  338. Wed Oct 17 2018 17:10:46 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  339.  
  340. SIP/2.0 200 OK
  341.  
  342. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  343.  
  344. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  345.  
  346. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.0
  347.  
  348. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  349.  
  350. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=oa1r8gd20v
  351.  
  352. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  353.  
  354. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  355.  
  356. CSeq: 102 INVITE
  357.  
  358. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>
  359.  
  360. Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
  361.  
  362. Supported: outbound
  363.  
  364. User-Agent: SIP.js/0.11.4
  365.  
  366. Content-Type: application/sdp
  367.  
  368. Content-Length: 1001
  369.  
  370.  
  371.  
  372. v=0
  373.  
  374. o=mozilla...THIS_IS_SDPARTA-62.0.3 4013890737116789720 0 IN IP4 0.0.0.0
  375.  
  376. s=-
  377.  
  378. t=0 0
  379.  
  380. a=sendrecv
  381.  
  382. a=fingerprint:sha-256 95:4C:35:DC:ED:FE:CE:A6:F9:11:EB:99:0A:E9:51:6A:54:2E:94:A2:52:E8:D3:19:D5:BB:9C:8E:ED:43:00:E7
  383.  
  384. a=ice-options:trickle
  385.  
  386. a=msid-semantic:WMS *
  387.  
  388. m=audio 52129 RTP/SAVPF 0 101
  389.  
  390. c=IN IP4 95.15.117.16
  391.  
  392. a=candidate:0 1 UDP 2122252543 10.6.1.10 52128 typ host
  393.  
  394. a=candidate:2 1 UDP 2122187007 192.168.0.10 52129 typ host
  395.  
  396. a=candidate:4 1 TCP 2105524479 10.6.1.10 9 typ host tcptype active
  397.  
  398. a=candidate:5 1 TCP 2105458943 192.168.0.10 9 typ host tcptype active
  399.  
  400. a=candidate:3 1 UDP 1685987327 95.15.117.16 52129 typ srflx raddr 192.168.0.10 rport 52129
  401.  
  402. a=sendrecv
  403.  
  404. a=fmtp:101 0-15
  405.  
  406. a=ice-pwd:b446558b3958080ea055cb28c16a34c7
  407.  
  408. a=ice-ufrag:2411180b
  409.  
  410. a=msid:{8d2327eb-ffa1-490b-b34b-5ee3b115b169} {300f8067-8d36-4093-bf0f-1e0bc7880688}
  411.  
  412. a=rtcp-mux
  413.  
  414. a=rtpmap:0 PCMU/8000
  415.  
  416. a=rtpmap:101 telephone-event/8000
  417.  
  418. a=setup:active
  419.  
  420. a=ssrc:3078438122 cname:{f2f40c9c-1708-4a40-bb3f-95edce41711a}
  421.  
  422.  
  423. sip-0.11.4.js:586:5
  424. Wed Oct 17 2018 17:10:47 GMT+0300 (Moscow Standard Time) | sip.inviteservercontext | no ACK received, attempting to retransmit OK sip-0.11.4.js:586:5
  425. Wed Oct 17 2018 17:10:47 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  426.  
  427. SIP/2.0 200 OK
  428.  
  429. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  430.  
  431. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  432.  
  433. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.0
  434.  
  435. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  436.  
  437. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=oa1r8gd20v
  438.  
  439. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  440.  
  441. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  442.  
  443. CSeq: 102 INVITE
  444.  
  445. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>
  446.  
  447. Supported: outbound
  448.  
  449. User-Agent: SIP.js/0.11.4
  450.  
  451. Content-Type: application/sdp
  452.  
  453. Content-Length: 1001
  454.  
  455.  
  456.  
  457. v=0
  458.  
  459. o=mozilla...THIS_IS_SDPARTA-62.0.3 4013890737116789720 0 IN IP4 0.0.0.0
  460.  
  461. s=-
  462.  
  463. t=0 0
  464.  
  465. a=sendrecv
  466.  
  467. a=fingerprint:sha-256 95:4C:35:DC:ED:FE:CE:A6:F9:11:EB:99:0A:E9:51:6A:54:2E:94:A2:52:E8:D3:19:D5:BB:9C:8E:ED:43:00:E7
  468.  
  469. a=ice-options:trickle
  470.  
  471. a=msid-semantic:WMS *
  472.  
  473. m=audio 52129 RTP/SAVPF 0 101
  474.  
  475. c=IN IP4 95.15.117.16
  476.  
  477. a=candidate:0 1 UDP 2122252543 10.6.1.10 52128 typ host
  478.  
  479. a=candidate:2 1 UDP 2122187007 192.168.0.10 52129 typ host
  480.  
  481. a=candidate:4 1 TCP 2105524479 10.6.1.10 9 typ host tcptype active
  482.  
  483. a=candidate:5 1 TCP 2105458943 192.168.0.10 9 typ host tcptype active
  484.  
  485. a=candidate:3 1 UDP 1685987327 95.15.117.16 52129 typ srflx raddr 192.168.0.10 rport 52129
  486.  
  487. a=sendrecv
  488.  
  489. a=fmtp:101 0-15
  490.  
  491. a=ice-pwd:b446558b3958080ea055cb28c16a34c7
  492.  
  493. a=ice-ufrag:2411180b
  494.  
  495. a=msid:{8d2327eb-ffa1-490b-b34b-5ee3b115b169} {300f8067-8d36-4093-bf0f-1e0bc7880688}
  496.  
  497. a=rtcp-mux
  498.  
  499. a=rtpmap:0 PCMU/8000
  500.  
  501. a=rtpmap:101 telephone-event/8000
  502.  
  503. a=setup:active
  504.  
  505. a=ssrc:3078438122 cname:{f2f40c9c-1708-4a40-bb3f-95edce41711a}
  506.  
  507.  
  508. sip-0.11.4.js:586:5
  509. Wed Oct 17 2018 17:10:48 GMT+0300 (Moscow Standard Time) | sip.inviteservercontext | no ACK received, attempting to retransmit OK sip-0.11.4.js:586:5
  510. Wed Oct 17 2018 17:10:48 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  511.  
  512. SIP/2.0 200 OK
  513.  
  514. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  515.  
  516. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=6db.c63;did=bfd.dab1>
  517.  
  518. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.4e6f5c18e3d29268dd37c09be4c42973.0
  519.  
  520. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK75b9ad28;rport=50600
  521.  
  522. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=oa1r8gd20v
  523.  
  524. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49420a68
  525.  
  526. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  527.  
  528. CSeq: 102 INVITE
  529.  
  530. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>
  531.  
  532. Supported: outbound
  533.  
  534. User-Agent: SIP.js/0.11.4
  535.  
  536. Content-Type: application/sdp
  537.  
  538. Content-Length: 1001
  539.  
  540.  
  541.  
  542. v=0
  543.  
  544. o=mozilla...THIS_IS_SDPARTA-62.0.3 4013890737116789720 0 IN IP4 0.0.0.0
  545.  
  546. s=-
  547.  
  548. t=0 0
  549.  
  550. a=sendrecv
  551.  
  552. a=fingerprint:sha-256 95:4C:35:DC:ED:FE:CE:A6:F9:11:EB:99:0A:E9:51:6A:54:2E:94:A2:52:E8:D3:19:D5:BB:9C:8E:ED:43:00:E7
  553.  
  554. a=ice-options:trickle
  555.  
  556. a=msid-semantic:WMS *
  557.  
  558. m=audio 52129 RTP/SAVPF 0 101
  559.  
  560. c=IN IP4 95.15.117.16
  561.  
  562. a=candidate:0 1 UDP 2122252543 10.6.1.10 52128 typ host
  563.  
  564. a=candidate:2 1 UDP 2122187007 192.168.0.10 52129 typ host
  565.  
  566. a=candidate:4 1 TCP 2105524479 10.6.1.10 9 typ host tcptype active
  567.  
  568. a=candidate:5 1 TCP 2105458943 192.168.0.10 9 typ host tcptype active
  569.  
  570. a=candidate:3 1 UDP 1685987327 95.15.117.16 52129 typ srflx raddr 192.168.0.10 rport 52129
  571.  
  572. a=sendrecv
  573.  
  574. a=fmtp:101 0-15
  575.  
  576. a=ice-pwd:b446558b3958080ea055cb28c16a34c7
  577.  
  578. a=ice-ufrag:2411180b
  579.  
  580. a=msid:{8d2327eb-ffa1-490b-b34b-5ee3b115b169} {300f8067-8d36-4093-bf0f-1e0bc7880688}
  581.  
  582. a=rtcp-mux
  583.  
  584. a=rtpmap:0 PCMU/8000
  585.  
  586. a=rtpmap:101 telephone-event/8000
  587.  
  588. a=setup:active
  589.  
  590. a=ssrc:3078438122 cname:{f2f40c9c-1708-4a40-bb3f-95edce41711a}
  591.  
  592.  
  593. sip-0.11.4.js:586:5
  594.  
  595. Wed Oct 17 2018 17:10:48 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  596.  
  597. ACK sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws SIP/2.0
  598.  
  599. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=30a.08e2>
  600.  
  601. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=30a.08e2>
  602.  
  603. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.670b98feed1c5d8c855db132724a61b8.0
  604.  
  605. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK5fde32d1;rport=50600
  606.  
  607. Max-Forwards: 69
  608.  
  609. From: "Pablo Escobar" <sip:internal.device-5000@10.2.2.68:50600>;tag=as49420a68
  610.  
  611. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=oa1r8gd20v
  612.  
  613. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  614.  
  615. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  616.  
  617. CSeq: 102 ACK
  618.  
  619. User-Agent: Staging PBX
  620.  
  621. Content-Length: 0
  622.  
  623.  
  624.  
  625.  
  626. sip-0.11.4.js:586:5
  627. Wed Oct 17 2018 17:10:49 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  628.  
  629. ACK sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws SIP/2.0
  630.  
  631. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=6db.c63>
  632.  
  633. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=6db.c63>
  634.  
  635. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.b6e2be8dda8f0f7ba62b9d8033a617e5.0
  636.  
  637. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK065c46f8;rport=50600
  638.  
  639. Max-Forwards: 69
  640.  
  641. From: "Pablo Escobar" <sip:internal.device-5000@10.2.2.68:50600>;tag=as49420a68
  642.  
  643. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=oa1r8gd20v
  644.  
  645. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  646.  
  647. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  648.  
  649. CSeq: 102 ACK
  650.  
  651. User-Agent: Staging PBX
  652.  
  653. Content-Length: 0
  654.  
  655.  
  656.  
  657.  
  658. sip-0.11.4.js:586:5
  659. Wed Oct 17 2018 17:10:49 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  660.  
  661. REGISTER sip:sip.example.com SIP/2.0
  662.  
  663. Via: SIP/2.0/WSS tk4i9toum5sf.invalid;branch=z9hG4bK6830082
  664.  
  665. Max-Forwards: 70
  666.  
  667. To: <sip:internal.device-6564@sip.example.com>
  668.  
  669. From: <sip:internal.device-6564@sip.example.com>;tag=9693sv8iih
  670.  
  671. Call-ID: jinl1cnh8ig1l2vv1pe69b
  672.  
  673. CSeq: 3304 REGISTER
  674.  
  675. Authorization: Digest algorithm=MD5, username="internal.device-6564", realm="sip.example.com", nonce="W8dD4lvHQrYb2vdquizIwl4LJoxZmaFl", uri="sip:sip.example.com", response="f0b3922e4303385cf7806bbb065751df"
  676.  
  677. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:0a855fba-d4ef-4969-96d0-fcd0b13c0edb>";expires=600
  678.  
  679. Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
  680.  
  681. Supported: path, gruu, outbound
  682.  
  683. User-Agent: SIP.js/0.11.4
  684.  
  685. Content-Length: 0
  686.  
  687.  
  688.  
  689.  
  690. sip-0.11.4.js:586:5
  691. Wed Oct 17 2018 17:10:50 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  692.  
  693. ACK sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws SIP/2.0
  694.  
  695. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49420a68;lr=on;did=d78.ad42>
  696.  
  697. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49420a68;lr=on;did=d78.ad42>
  698.  
  699. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bKccc7.5fd7a0cf05393af23f6a01d68a044d84.0
  700.  
  701. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK65b72247;rport=50600
  702.  
  703. Max-Forwards: 69
  704.  
  705. From: "Pablo Escobar" <sip:internal.device-5000@10.2.2.68:50600>;tag=as49420a68
  706.  
  707. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=oa1r8gd20v
  708.  
  709. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  710.  
  711. Call-ID: 1a8dc7fe56e5244e6825fb4c63f93727@10.2.2.68:50600
  712.  
  713. CSeq: 102 ACK
  714.  
  715. User-Agent: Staging PBX
  716.  
  717. Content-Length: 0
  718.  
  719.  
  720.  
  721.  
  722. sip-0.11.4.js:586:5
  723. Wed Oct 17 2018 17:10:50 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  724.  
  725. SIP/2.0 200 OK
  726.  
  727. Via: SIP/2.0/WSS tk4i9toum5sf.invalid;branch=z9hG4bK6830082;rport=9474;received=95.15.117.16
  728.  
  729. To: <sip:internal.device-6564@sip.example.com>;tag=7224485d55e1d1f43dfe3a4d724dce9c.02d4
  730.  
  731. From: <sip:internal.device-6564@sip.example.com>;tag=9693sv8iih
  732.  
  733. Call-ID: jinl1cnh8ig1l2vv1pe69b
  734.  
  735. CSeq: 3304 REGISTER
  736.  
  737. Contact: <sip:63g5m7mj@tk4i9toum5sf.invalid;transport=ws>;expires=20;received="sip:95.15.117.16:9474;transport=ws";+sip.instance="<urn:uuid:0a855fba-d4ef-4969-96d0-fcd0b13c0edb>";reg-id=1
  738.  
  739. Server: MS Lync
  740.  
  741. Content-Length: 0
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement