Have a look at your system network configuration and aliases in opensips? Where do these messages come from and where do they go? Have you checked if they are set properly before they reach opensips.
Regards, Ali Pey On Tue, Apr 15, 2014 at 7:14 AM, B. Buitenhuis <bern...@buitenhuis.nu>wrote: > Anyone has any clue where to look? > > > > Van: MT <bern...@buitenhuis.nu> > Beantwoorden - Aan: OpenSIPS users mailling list <users@lists.opensips.org > > > Datum: maandag 14 april 2014 12:35 > > Aan: OpenSIPS users mailling list <users@lists.opensips.org> > Onderwerp: Re: [OpenSIPS-Users] Issue in VIA Header > > Also with the latest master branch I've got this problem. > After running opensips deamon for an hour the problems seems te be solved. > > Is this a known bug? > > Van: MT <bern...@buitenhuis.nu> > Beantwoorden - Aan: OpenSIPS users mailling list <users@lists.opensips.org > > > Datum: zaterdag 12 april 2014 00:09 > Aan: "users@lists.opensips.org" <users@lists.opensips.org> > Onderwerp: [OpenSIPS-Users] Issue in VIA Header > > Hello, > > I'm facing the same problem as: > https://github.com/OpenSIPS/opensips/issues/190 > > When I look at a wireshark, I see the following in the VIA header: > Via: SIP/2.0/UDP > \000\000\000\000\000\000\000\000\000\000\000\000\000:5060;branch=z9hG4bK9414.22d66c76.0 > > As far as I can see it's only with the CANCEL method, in the config it > looks like: > > if (method=="CANCEL") > { > set_advertised_address(185.XX.XX.XX); > > route("PROCESS_RTP_PROXY"); > unforce_rtp_proxy(); > if (t_check_trans()) > t_relay(); > exit; > } > > > I've tested it with 1.8.3 and 1.10.1 > > Does anyone has this same problem? > > > Regards, > > Bernard Buitenhuis > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
