The captures you provided does not contain any useful information, there was no sip headers in there.
you should provide something like the file attached. Here is a command that you can extract the sip info from a tshark pcap tshark -r /hello.pcap -V -T fields -e ip -e udp.port -e tcp.port -e sip.Request-Line -e sip.msg_hdr -e sip.msg_body -w world.pcap -E separator=" " | tee > pcap.txt (Notice the newline for the separator, thats required if yu want the fields on new lines.) Here is a un-encrypted version of a pcap, and you should get something similar after decrypting with your private key. On Sun, Jul 12, 2015 at 1:49 PM, Nabeel <[email protected]> wrote: > The one attached has a bit more information after I set up Wireshark > correctly with the server's private key. > > On 12 July 2015 at 17:20, Nabeel <[email protected]> wrote: > >> Please find the decoded 'plain text' version exported from Wireshark >> attached to this Email. >> >> I am still unclear how to add this 'route header' or whatever else is >> required to make a call connect over TLS. >> >> Why must there be so many configurations just to set the correct port? >> >> On 12 July 2015 at 13:38, Podrigal, Aron <[email protected]> >> wrote: >> >>> >>> https://wiki.freeswitch.org/wiki/Packet_Capture#Analyze_a_packet_capture_with_SIP_TLS_on_port_5061 >>> On Jul 12, 2015 8:05 AM, "Nabeel" <[email protected]> wrote: >>> >>>> Well, that was the output of that command. How do I decrypt it? >>>> On 12 Jul 2015 13:03, "Podrigal, Aron" <[email protected]> >>>> wrote: >>>> >>>>> Encrypted :) >>>>> On Jul 12, 2015 3:17 AM, "Nabeel" <[email protected]> wrote: >>>>> >>>>>> I have attached the output of "# ngrep -tqd any -W byline port 5061" >>>>>> as you suggested. >>>>>> >>>>>> Please let me know how I can add transport=tls to contact, because >>>>>> in my config file I see nothing about contact header. >>>>>> >>>>>> On 12 July 2015 at 05:10, Podrigal, Aron <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hello Nabeel, >>>>>>> >>>>>>> I was expecting to get a textual file with all sip headers like the >>>>>>> output of ngrep -tqd any -W byline I did not have a pc to be able to >>>>>>> decode this pcap with tshark. I'll try to give a look at it tomorrow. >>>>>>> >>>>>>> Just a note, try adding a transport=tls to contact. >>>>>>> On Jul 11, 2015 2:59 AM, "Nabeel" <[email protected]> wrote: >>>>>>> >>>>>>>> In the log, I see that 'uri' does not have ';transport=tls', but >>>>>>>> the 'ruri' does have ';transport=tls' : >>>>>>>> >>>>>>>> DBG:core:parse_msg: uri: <sip:mydomain.com> >>>>>>>> >>>>>>>> DBG:core:parse_to: display={}, ruri={sip:[email protected] >>>>>>>> ;transport=tls} >>>>>>>> >>>>>>>> >>>>>>>> On 11 July 2015 at 07:33, Nabeel <[email protected]> wrote: >>>>>>>> >>>>>>>>> I checked the SIP capture in Wireshark and it seems the client is >>>>>>>>> using the wrong port: >>>>>>>>> >>>>>>>>> "Src port 3921 (3921) [Client IP] >>>>>>>>> >>>>>>>>> Dst port 5061 (5061) [OpenSIPS IP]" >>>>>>>>> >>>>>>>>> The client is set to use port 5061 in its settings and I have the >>>>>>>>> following in OpenSIPS config: >>>>>>>>> >>>>>>>>> $rp = 5061 >>>>>>>>> add_uri_param("transport=tls"); >>>>>>>>> force_send_socket("tls:ip:port"); >>>>>>>>> >>>>>>>>> So how can I add the route header to fix this? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Users mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>>>>> >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> Users mailing list >>>>>>> [email protected] >>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>>>> >>>>>>> >>>>>> >> > -- Aron Podrigal - //Be happy :-)
sample.pcap
Description: application/vnd.tcpdump.pcap
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
