Re: [OpenSIPS-Users] TLS Error

Gary, Have you been able to take a look at the traffic to see what it is? I'm going to guess non-TLS OPTIONS pings. Try: tcpdump -nlvs0 -i eth0 host 66.81.1.2 and port 7604 Substitute the correct interface for eth0 isn't valid for your case. - Jeff On Wed, Nov 12, 2014 at 3:48 PM, Gary Ny

[OpenSIPS-Users] TLS Error

Hi, I am using "opensips 1.11.3-tls (x86_64/linux)" git revision: 7e5bbcf My log file is getting flooded with following errors. ERROR:core:_tls_read: SYSCALL error -> (0) ERROR:core:_tls_read: TLS connection to 66.81.1.2:7604 read failed ERROR:core:_tls_read: TLS read error: 5 ERROR:core:tcp_rea

Re: [OpenSIPS-Users] P-Asserted-ID

Hi, OK, you should have the following lines now (if I understand correctly) var(from)='sip:+'+$var(cid)+'@54.76.30.63'; append_hf("P-Asserted-Identity: <$var(from)>\r\n"); I suggest you add xlog line after append_hf like: xlog("P-Asserted-Identity: <$var(from)>"); Also run tcpdump/ngrep/sipgrep

Re: [OpenSIPS-Users] P-Asserted-ID

The + before the $var(from) was removed. On 12 November 2014 21:31, Răzvan Crainea wrote: > I was pointing to the way you are building the header in append_hf() > function. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 11/12/2014 11:35 AM, Sahil Gupt

Re: [OpenSIPS-Users] P-Asserted-ID

I was pointing to the way you are building the header in append_hf() function. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 11/12/2014 11:35 AM, Sahil Gupta wrote: Hi Razvan, Thanks for getting back to me. The code was: $var(from)='sip:'+$var(cid)+'@54.76.30.

Re: [OpenSIPS-Users] P-Asserted-ID

Hi Razvan, Thanks for getting back to me. The code was: $var(from)='sip:'+$var(cid)+'@54.76.30.63'; I modified it to become: var(from)='sip:+'+$var(cid)+'@54.76.30.63'; The PAID function is definately being called as our far end carrier receives the P-Asserted-ID but they don't see a "+" before

Re: [OpenSIPS-Users] P-Asserted-ID

Hi, Sahil! Are you sure the PAID function is called at all? The PAI header you are adding contains an invalid URI, it is something like +sip:+cid@54.76.30.63. Try to add some xlogs in the PAID route to check if it is really called. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-

Re: [OpenSIPS-Users] mi_open_reply_pipe: open error

I understand this is supposed to work out of the box, but it is not. Any traces, debugging or something that I can do to figure this out?? My installation was simple with make menuconfig where I configured the prefix as /usr/local/. Added some additional modules I needed and compiled and installed.