Hey Razvan, Can i take following patch and directly apply to my existing install branch instead of downloading new Master?
https://github.com/OpenSIPS/opensips/commit/178b0cc26b05a81947de150fe1c2df36d600ccaa Currently i am running: [root@sip ]# opensips -V version: opensips 2.1.1dev-tls (x86_64/linux) flags: STATS: On, USE_IPV6, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. git revision: b3beb20 main.c compiled on 11:44:56 Dec 31 2014 with gcc 4.4.7 On Mon, Mar 9, 2015 at 10:39 AM, Satish Patel <satish....@gmail.com> wrote: > Thanks Razvan, > > It is working great!! you guys are awesome! > > > On Mon, Mar 9, 2015 at 9:43 AM, Satish Patel <satish....@gmail.com> wrote: > >> Sorry It was "branch" >> >> My iPhone is over smart :( >> >> -- >> Sent from my iPhone >> >> On Mar 9, 2015, at 9:12 AM, Satish Patel <satish....@gmail.com> wrote: >> >> Superb, definitely going to give a try, I have a silly question. Can I >> apply that patch manually on my beach because if I try new master then >> fires it require any change in mysql? >> >> Reason we have couple of box running 2.1.x so want to keep it same. But >> any way let me test code first. And get back to you. >> >> -- >> Sent from my iPhone >> >> On Mar 9, 2015, at 5:03 AM, Răzvan Crainea <raz...@opensips.org> wrote: >> >> Hi, Satish! >> >> Indeed, there was an issue with the protocol check. I fixed it in the >> master branch. Please give it another try and let me know if you still have >> problems. >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Solutionswww.opensips-solutions.com >> >> On 03/08/2015 09:31 PM, Satish Patel wrote: >> >> I got your point, but our plan is to use 2.1.x and we are already using >> it since last 6 month without issue. >> >> But it should work in 2.1.x right? >> >> On Sun, Mar 8, 2015 at 3:20 PM, <shah...@voip-demos.com> wrote: >> >>> OpenSIPS v2.x is much different then v1.x. So, if you are not familiar >>> with it, you should better use 1.x >>> >>> Thank you. >>> >>> >>> >>> On 2015-03-08 19:52, Satish Patel wrote: >>> >>> I tried same configuration on 1.11 version and it works! so look like >>> something wrong in 2.1.x version please fix that bug as soon as possible >>> >>> On Sun, Mar 8, 2015 at 2:04 PM, Satish Patel <satish....@gmail.com> >>> wrote: >>> >>>> sorry for push but it wired error! >>>> >>>> I have configure siptrace to send packet to "Homer" but getting >>>> following error in logs >>>> >>>> ERROR:siptrace:pipport2su: bad protocol udp >>>> ERROR:siptrace:pipport2su: bad protocol udp >>>> ERROR:siptrace:pipport2su: bad protocol udp >>>> >>>> Opensips 2.1.x >>>> >>>> #### SIP Capture agent >>>> loadmodule "siptrace.so" >>>> modparam("siptrace", "duplicate_uri", "sip:192.168.1.200:9060") >>>> modparam("siptrace", "duplicate_with_hep", 1) >>>> modparam("siptrace", "trace_to_database", 0) >>>> modparam("siptrace", "trace_flag", 22) >>>> modparam("siptrace", "trace_on", 1) >>>> #HEPv2 == timestamp will be included to HEP header >>>> modparam("siptrace", "hep_version", 1) >>>> modparam("siptrace", "db_url", "mysql://opensips:xxxxxx@localhost >>>> /opensips") >>>> >>>> ... >>>> ... >>>> route{ >>>> >>>> setflag(22); >>>> >>>> sip_trace(); >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users@lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> >> >> _______________________________________________ >> Users mailing >> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> 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