Advertisement
pavelsc

SIP.js 621 Ch69

Oct 17th, 2018
290
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 15.65 KB | None | 0 0
  1. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  2.  
  3. INVITE sip:internal.device-6564@10.0.14.88:5068 SIP/2.0
  4. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  5. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  6. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.0
  7. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK2ca2a546;rport=50600
  8. Max-Forwards: 69
  9. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  10. To: <sip:internal.device-6564@10.0.14.88:5068>
  11. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  12. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  13. CSeq: 102 INVITE
  14. User-Agent: Staging PBX
  15. Date: Wed, 17 Oct 2018 14:44:43 GMT
  16. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
  17. Supported: replaces
  18. Content-Type: application/sdp
  19. Content-Length: 622
  20.  
  21. v=0
  22. o=root 988379943 988379943 IN IP4 18.148.13.82
  23. s=Staging PBX
  24. c=IN IP4 18.148.13.82
  25. t=0 0
  26. m=audio 53990 RTP/SAVPF 0 8 3 101
  27. a=maxptime:150
  28. a=rtpmap:0 PCMU/8000
  29. a=rtpmap:8 PCMA/8000
  30. a=rtpmap:3 GSM/8000
  31. a=rtpmap:101 telephone-event/8000
  32. a=fmtp:101 0-16
  33. a=sendrecv
  34. a=rtcp:53991
  35. a=rtcp-mux
  36. a=setup:actpass
  37. a=fingerprint:sha-1 B1:CD:F6:15:4C:27:6A:F0:B0:24:AC:8B:3C:C4:23:F7:22:B5:B0:C0
  38. a=ice-ufrag:Ff1IdMJB
  39. a=ice-pwd:PkB0PmzBIHONxlGzGwL7RCCtaw
  40. a=candidate:62HXkmKaZqN6SxDo 1 UDP 2130706431 18.148.13.82 53990 typ host
  41. a=candidate:62HXkmKaZqN6SxDo 2 UDP 2130706430 18.148.13.82 53991 typ host
  42.  
  43.  
  44. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.sipmessage | header "Content-Disposition" not present
  45. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  46.  
  47. SIP/2.0 100 Trying
  48. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.0
  49. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK2ca2a546;rport=50600
  50. To: <sip:internal.device-6564@10.0.14.88:5068>
  51. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  52. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  53. CSeq: 102 INVITE
  54. Supported: outbound
  55. User-Agent: SIP.js/0.11.4
  56. Content-Length: 0
  57.  
  58.  
  59.  
  60. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.dialog | new UAS dialog created with status EARLY
  61. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  62.  
  63. SIP/2.0 180 Ringing
  64. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  65. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  66. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.0
  67. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK2ca2a546;rport=50600
  68. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=4onsanhm1s
  69. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  70. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  71. CSeq: 102 INVITE
  72. Contact: <sip:62amjohv@hnnumq4h6865.invalid;transport=ws>
  73. Supported: outbound
  74. User-Agent: SIP.js/0.11.4
  75. Content-Length: 0
  76.  
  77.  
  78.  
  79. Stack.js:128 New incoming call
  80. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  81.  
  82. INVITE sip:internal.device-6564@95.15.117.16 SIP/2.0
  83. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  84. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  85. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.1
  86. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK2ca2a546;rport=50600
  87. Max-Forwards: 69
  88. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  89. To: <sip:internal.device-6564@10.0.14.88:5068>
  90. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  91. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  92. CSeq: 102 INVITE
  93. User-Agent: Staging PBX
  94. Date: Wed, 17 Oct 2018 14:44:43 GMT
  95. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
  96. Supported: replaces
  97. Content-Type: application/sdp
  98. Content-Length: 622
  99.  
  100. v=0
  101. o=root 988379943 988379943 IN IP4 18.148.13.82
  102. s=Staging PBX
  103. c=IN IP4 18.148.13.82
  104. t=0 0
  105. m=audio 53990 RTP/SAVPF 0 8 3 101
  106. a=maxptime:150
  107. a=rtpmap:0 PCMU/8000
  108. a=rtpmap:8 PCMA/8000
  109. a=rtpmap:3 GSM/8000
  110. a=rtpmap:101 telephone-event/8000
  111. a=fmtp:101 0-16
  112. a=sendrecv
  113. a=rtcp:53991
  114. a=rtcp-mux
  115. a=setup:actpass
  116. a=fingerprint:sha-1 B1:CD:F6:15:4C:27:6A:F0:B0:24:AC:8B:3C:C4:23:F7:22:B5:B0:C0
  117. a=ice-ufrag:Ff1IdMJB
  118. a=ice-pwd:PkB0PmzBIHONxlGzGwL7RCCtaw
  119. a=candidate:62HXkmKaZqN6SxDo 1 UDP 2130706431 18.148.13.82 53990 typ host
  120. a=candidate:62HXkmKaZqN6SxDo 2 UDP 2130706430 18.148.13.82 53991 typ host
  121.  
  122.  
  123. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  124.  
  125. SIP/2.0 482 Loop Detected
  126. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.1
  127. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK2ca2a546;rport=50600
  128. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=9tn52et0nv
  129. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  130. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  131. CSeq: 102 INVITE
  132.  
  133.  
  134.  
  135. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:44 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  136.  
  137. REGISTER sip:sip.example.com SIP/2.0
  138. Via: SIP/2.0/WSS hnnumq4h6865.invalid;branch=z9hG4bK9931534
  139. Max-Forwards: 70
  140. To: <sip:internal.device-6564@sip.example.com>
  141. From: <sip:internal.device-6564@sip.example.com>;tag=oebafigms6
  142. Call-ID: fp5oe5m7di6998373f4152
  143. CSeq: 1456 REGISTER
  144. Authorization: Digest algorithm=MD5, username="internal.device-6564", realm="sip.example.com", nonce="W8dL5lvHSrqZLMTp8WDLaS0NKjAHqz3Z", uri="sip:sip.example.com", response="fed34504ed4993e1a8c8a946f6b000f9"
  145. Contact: <sip:62amjohv@hnnumq4h6865.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:dbc1ecfd-4d4e-4dc3-b336-d14de2bfcafb>";expires=600
  146. Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
  147. Supported: path, gruu, outbound
  148. User-Agent: SIP.js/0.11.4
  149. Content-Length: 0
  150.  
  151.  
  152.  
  153. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:45 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  154.  
  155. ACK sip:internal.device-6564@95.15.117.16 SIP/2.0
  156. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.1
  157. Max-Forwards: 69
  158. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  159. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=9tn52et0nv
  160. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  161. CSeq: 102 ACK
  162. Content-Length: 0
  163.  
  164.  
  165.  
  166. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:45 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  167.  
  168. SIP/2.0 200 OK
  169. Via: SIP/2.0/WSS hnnumq4h6865.invalid;branch=z9hG4bK9931534;rport=12929;received=95.15.117.16
  170. To: <sip:internal.device-6564@sip.example.com>;tag=7224485d55e1d1f43dfe3a4d724dce9c.103d
  171. From: <sip:internal.device-6564@sip.example.com>;tag=oebafigms6
  172. Call-ID: fp5oe5m7di6998373f4152
  173. CSeq: 1456 REGISTER
  174. Contact: <sip:62amjohv@hnnumq4h6865.invalid;transport=ws>;expires=20;received="sip:95.15.117.16:12929;transport=ws";+sip.instance="<urn:uuid:dbc1ecfd-4d4e-4dc3-b336-d14de2bfcafb>";reg-id=1
  175. Server: MS Lync
  176. Content-Length: 0
  177.  
  178.  
  179.  
  180. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:47 GMT+0300 (Moscow Standard Time) | sip.dialog | dialog 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:506004onsanhm1sas49b02f79 changed to CONFIRMED state
  181. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:47 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | SessionDescriptionHandlerOptions: {"constraints":{},"peerConnectionOptions":{}}
  182. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:47 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | initPeerConnection
  183. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:47 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | New peer connection created
  184. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:47 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | track added
  185. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:47 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | acquiring local media
  186. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:48 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | acquired local media streams
  187. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:48 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | RTCIceGatheringState changed: gathering
  188. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:48 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate received: candidate:1434301788 1 udp 2113937151 192.168.0.10 60644 typ host generation 0 ufrag a9bp network-cost 999
  189. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:48 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate received: candidate:842163049 1 udp 1677729535 95.15.117.16 60644 typ srflx raddr 192.168.0.10 rport 60644 generation 0 ufrag a9bp network-cost 999
  190. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:48 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | RTCIceGatheringState changed: complete
  191. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:48 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  192.  
  193. SIP/2.0 200 OK
  194. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  195. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  196. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.0
  197. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK2ca2a546;rport=50600
  198. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=4onsanhm1s
  199. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  200. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  201. CSeq: 102 INVITE
  202. Contact: <sip:62amjohv@hnnumq4h6865.invalid;transport=ws>
  203. Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
  204. Supported: outbound
  205. User-Agent: SIP.js/0.11.4
  206. Content-Type: application/sdp
  207. Content-Length: 1026
  208.  
  209. v=0
  210. o=- 5142061225849306342 2 IN IP4 127.0.0.1
  211. s=-
  212. t=0 0
  213. a=msid-semantic: WMS Q6AsjIe6iQe4iW6BGzOTaTXEcCcvoeiP5KyZ
  214. m=audio 60644 RTP/SAVPF 0 8 101
  215. c=IN IP4 95.15.117.16
  216. a=rtcp:9 IN IP4 0.0.0.0
  217. a=candidate:1434301788 1 udp 2113937151 192.168.0.10 60644 typ host generation 0 network-cost 999
  218. a=candidate:842163049 1 udp 1677729535 95.15.117.16 60644 typ srflx raddr 192.168.0.10 rport 60644 generation 0 network-cost 999
  219. a=ice-ufrag:a9bp
  220. a=ice-pwd:F6x8iHt7VetuWu23FtGg/ZQn
  221. a=ice-options:trickle
  222. a=fingerprint:sha-256 5B:6C:66:CF:84:24:FB:A2:43:F0:33:D4:55:10:D3:40:9F:99:2B:38:16:82:04:B2:F6:D5:E9:8C:47:B7:2F:BD
  223. a=setup:active
  224. a=mid:audio
  225. a=sendrecv
  226. a=rtcp-mux
  227. a=rtpmap:0 PCMU/8000
  228. a=rtpmap:8 PCMA/8000
  229. a=rtpmap:101 telephone-event/8000
  230. a=ssrc:2791269843 cname:3xL7k8PPxJft1mls
  231. a=ssrc:2791269843 msid:Q6AsjIe6iQe4iW6BGzOTaTXEcCcvoeiP5KyZ 70600e5c-adaa-4eee-bba3-6db6da135bfc
  232. a=ssrc:2791269843 mslabel:Q6AsjIe6iQe4iW6BGzOTaTXEcCcvoeiP5KyZ
  233. a=ssrc:2791269843 label:70600e5c-adaa-4eee-bba3-6db6da135bfc
  234.  
  235.  
  236. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:48 GMT+0300 (Moscow Standard Time) | sip.invitecontext.sessionDescriptionHandler | ICE candidate gathering complete
  237. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:49 GMT+0300 (Moscow Standard Time) | sip.inviteservercontext | no ACK received, attempting to retransmit OK
  238. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:49 GMT+0300 (Moscow Standard Time) | sip.transport | sending WebSocket message:
  239.  
  240. SIP/2.0 200 OK
  241. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  242. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49b02f79;lr=on;did=30a.08e2;did=83.8e72>
  243. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.f5333e531c1d22b8b759dc34f14c8838.0
  244. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK2ca2a546;rport=50600
  245. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=4onsanhm1s
  246. From: "Pablo Escobar" <sip:1111@10.2.2.68:50600>;tag=as49b02f79
  247. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  248. CSeq: 102 INVITE
  249. Contact: <sip:62amjohv@hnnumq4h6865.invalid;transport=ws>
  250. Supported: outbound
  251. User-Agent: SIP.js/0.11.4
  252. Content-Type: application/sdp
  253. Content-Length: 1026
  254.  
  255. v=0
  256. o=- 5142061225849306342 2 IN IP4 127.0.0.1
  257. s=-
  258. t=0 0
  259. a=msid-semantic: WMS Q6AsjIe6iQe4iW6BGzOTaTXEcCcvoeiP5KyZ
  260. m=audio 60644 RTP/SAVPF 0 8 101
  261. c=IN IP4 95.15.117.16
  262. a=rtcp:9 IN IP4 0.0.0.0
  263. a=candidate:1434301788 1 udp 2113937151 192.168.0.10 60644 typ host generation 0 network-cost 999
  264. a=candidate:842163049 1 udp 1677729535 95.15.117.16 60644 typ srflx raddr 192.168.0.10 rport 60644 generation 0 network-cost 999
  265. a=ice-ufrag:a9bp
  266. a=ice-pwd:F6x8iHt7VetuWu23FtGg/ZQn
  267. a=ice-options:trickle
  268. a=fingerprint:sha-256 5B:6C:66:CF:84:24:FB:A2:43:F0:33:D4:55:10:D3:40:9F:99:2B:38:16:82:04:B2:F6:D5:E9:8C:47:B7:2F:BD
  269. a=setup:active
  270. a=mid:audio
  271. a=sendrecv
  272. a=rtcp-mux
  273. a=rtpmap:0 PCMU/8000
  274. a=rtpmap:8 PCMA/8000
  275. a=rtpmap:101 telephone-event/8000
  276. a=ssrc:2791269843 cname:3xL7k8PPxJft1mls
  277. a=ssrc:2791269843 msid:Q6AsjIe6iQe4iW6BGzOTaTXEcCcvoeiP5KyZ 70600e5c-adaa-4eee-bba3-6db6da135bfc
  278. a=ssrc:2791269843 mslabel:Q6AsjIe6iQe4iW6BGzOTaTXEcCcvoeiP5KyZ
  279. a=ssrc:2791269843 label:70600e5c-adaa-4eee-bba3-6db6da135bfc
  280.  
  281.  
  282. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:50 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  283.  
  284. ACK sip:62amjohv@hnnumq4h6865.invalid;transport=ws SIP/2.0
  285. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49b02f79;lr=on;did=132.ccd2>
  286. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49b02f79;lr=on;did=132.ccd2>
  287. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.a282990e67e7163254a3d3d006f329ff.0
  288. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK7ddd58ca;rport=50600
  289. Max-Forwards: 69
  290. From: "Pablo Escobar" <sip:internal.device-5000@10.2.2.68:50600>;tag=as49b02f79
  291. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=4onsanhm1s
  292. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  293. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  294. CSeq: 102 ACK
  295. User-Agent: Staging PBX
  296. Content-Length: 0
  297.  
  298.  
  299.  
  300. sip-0.11.4.js:586 Wed Oct 17 2018 17:44:51 GMT+0300 (Moscow Standard Time) | sip.transport | received WebSocket text message:
  301.  
  302. ACK sip:62amjohv@hnnumq4h6865.invalid;transport=ws SIP/2.0
  303. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=ws;r2=on;ftag=as49b02f79;lr=on>
  304. Record-Route: <sip:kam2.example.com:5068;nat=yes;transport=udp;r2=on;ftag=as49b02f79;lr=on>
  305. Via: SIP/2.0/WSS kam2.example.com:5068;branch=z9hG4bK70f5.eec1866d5921ecb276fc863b50fc17d2.0
  306. Via: SIP/2.0/UDP 10.2.2.68:50600;received=10.2.2.68;branch=z9hG4bK4296123f;rport=50600
  307. Max-Forwards: 69
  308. From: "Pablo Escobar" <sip:internal.device-5000@10.2.2.68:50600>;tag=as49b02f79
  309. To: <sip:internal.device-6564@10.0.14.88:5068>;tag=4onsanhm1s
  310. Contact: <sip:internal.device-5000@10.2.2.68:50600;alias=10.2.2.68~50600~1>
  311. Call-ID: 2dc37fd66be6a4690636378e75fd0c28@10.2.2.68:50600
  312. CSeq: 102 ACK
  313. User-Agent: Staging PBX
  314. Content-Length: 0
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement