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
