Re: [OpenSIPS-Users] Opensips 3.1 and Homer 7

2021-01-06 Thread Sunil More 
Hello Bogdan-Andrei,

Looks like I had two versions of opensips installed in different
prefixes and the one used was opensips 3.0.0 .
I created a fresh setup with opensips-3.1.1 and yes the logs are available.
I will take up the rtpengine issue with their channel.

Thanks.

Sunil More

Manager - DevOps

91 95033 38275

sunil.m...@samespace.com






On Wed, Jan 6, 2021 at 9:01 PM Bogdan-Andrei Iancu 
wrote:

> Hi Sunil,
>
> What is the exact version of opensips you are using ? do an "opensips -V"
> and check for the revision number.
> Also
>
> 1) OpenSIPS does not sent any QoS data as it does not have it. This is
> something for RTPengine to do
>
> 2) The type of the log records was fixed, so consider an update to latest
> 3.1 (3.1.1)
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Bootcamp 2020 online
>   https://opensips.org/training/OpenSIPS_eBootcamp_2020/
>
> On 1/5/21 3:01 PM, Sunil More wrote:
>
>
> Hello All,
>
> I am using homer 7 and opensips 3.1. I am using the tracer module along
> with hep to send to helify-server.
>
> here is a snippet of the config.
>
> #--- Loading Tracer
> loadmodule "tracer.so"
> modparam("tracer", "trace_on", 1)
> modparam("tracer", "trace_id","[tid]uri=hep:hep_dst")
>
> #- Loading PROTOCOLs 
> -
> loadmodule "proto_udp.so"
> loadmodule "proto_tls.so"
> loadmodule "proto_hep.so"
> modparam("proto_hep", "hep_id", "[hep_dst] 10.153.53.167:9060
> ; transport=udp")
> modparam("proto_hep", "homer5_on", 1)
> modparam("proto_hep", "hep_port", )
>
> Using trace as below
>
> trace("tid", "t", "sip|xlog",100);
>
> I am able to get sip traces in Homer UI .  I am using rtpengine with
> opensips and getting rtcp logs.  However
>
> - I am not able to get Qos
>
> - logs are sent to Homer but with *method RTP and type RTP.* (they are
> not displayed in the logs tab)
>
>
> I tried hep.js and I could populate Qos , SIP msgs and Logs in respective
> tabs.
>
>
> Could anyone please point me in the right direction?
>
>
> Sunil More
>
> Manager - DevOps
>
> 91 95033 38275
>
> sunil.m...@samespace.com
>
>
>
> 
>
>
>
> 
>
>
>
> ___
> 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

Re: [OpenSIPS-Users] Mediaproxy Relay start error - 'MediaRelayBase' is not defined

2021-01-06 Thread Adrian Georgescu 
This was a bug.

You must update to the latest mediaproxy version:

sudo apt update 
sudo apt install mediaproxy-relay mediaproxy-common mediaproxy-dispatcher

Regards,
Adrian

> On 6 Jan 2021, at 12:59, Mark Allen  wrote:
> 
> Hi all - not sure what I'm missing here... 
> 
> I'm installing Mediaproxy onto our Debian Buster box which is also running 
> OpenSIPS 3.1 but when I start the relay I'm getting an error in syslog...
> 
> 15:40:07 opensipsx media-relay[4983]: INFO Starting MediaProxy Relay 4.0.4
> 15:40:07 opensipsx media-relay[4983]: INFO Set resource limit for maximum 
> open file descriptors to 11000
> 15:40:07 opensipsx media-relay[4983]: CRITICAL Failed to create MediaProxy 
> Relay: name 'MediaRelayBase' is not defined
> 15:40:07 opensipsx media-relay[4983]: ERRORTraceback (most recent call 
> last):#012ERROR  File "/usr/bin/media-relay", line 100, in 
> #012ERRORfrom mediaproxy.relay import MediaRelay#012ERROR 
>  File "/usr/lib/python3/dist-packages/mediaproxy/relay.py", line 290, in 
> #012ERRORclass MediaRelay(MediaRelayBase):#012ERROR
> NameError: name 'MediaRelayBase' is not defined
> 15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Main process exited, 
> code=exited, status=1/FAILURE
> 15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Failed with result 
> 'exit-code'.
> 
> I'm starting the relay with the command...
> 
> systemctl start mediaproxy-relay
> 
> ...I installed Mediaproxy using the Debian package using the instructions at 
> http://mediaproxy.ag-projects.com/installation-guide/ 
>  and 
> https://github.com/AGProjects/mediaproxy 
> . mediaproxy-dispatcher is starting 
> successfully.
> 
> In the /etc/mediaproxy/config.ini file - everything is left at the default 
> setting except for...
> 
> dispatchers = xxx.xxx.xxx.xxx
> advertised_ip = xxx.xxx.xxx.xxx
> 
> Certificates are in place in /etc/mediaproxy/tls
> 
> 
> Anybody got any ideas about where I've gone wrong
> 
> 
> 
> ___
> 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

[OpenSIPS-Users] Digest Auth with LDAP/RADIUS

2021-01-06 Thread bobsy via Users 
Hello everyone,

I’m attempting to use digest auth on Freeradius with LDAP and plaintext 
userPassword’s.

When the radius server goes to auth the digest hashes don’t match up.

  authenticate {
(17) digest: A1 = bobsy:opensips.vale.ski:password
(17) digest: A2 = REGISTER:sip:opensips.vale.ski
H(A1) = 0342aafbaea975d9fde3c46f3f093993
H(A2) = b0605d01a41aac18c7f1a84c8ca1c4f5
(17) digest: KD = 
0342aafbaea975d9fde3c46f3f093993:5ff5eaca15917970591b0edf7c7c6bbd13698c0dd5e6:b0605d01a41aac18c7f1a84c8ca1c4f5
EXPECTED a8d6639edfd61ac7b1bb247f7832b8e5
RECEIVED a817470a4e1612532d167bed0354a88b
(17) digest: FAILED authentication
(17) [digest] = reject
(17)   } # authenticate = reject
(17) Failed to authenticate the user

I have calculate_ha1 set to 1.

Any insight would be great.

And after this is resolved maybe someone can help me find out why the Kerberos 
module looks for “User-Password”.  I believe it should be looking for 
“Cleartext-Password” and that’s why Kerberos won’t work for me.

Regards,

Michael Vale.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Mediaproxy Relay start error - 'MediaRelayBase' is not defined

2021-01-06 Thread Mark Allen 
Hi all - not sure what I'm missing here...

I'm installing Mediaproxy onto our Debian Buster box which is also running
OpenSIPS 3.1 but when I start the relay I'm getting an error in syslog...

15:40:07 opensipsx media-relay[4983]: INFO Starting MediaProxy Relay
4.0.4
15:40:07 opensipsx media-relay[4983]: INFO Set resource limit for
maximum open file descriptors to 11000
15:40:07 opensipsx media-relay[4983]: CRITICAL Failed to create MediaProxy
Relay: name 'MediaRelayBase' is not defined
15:40:07 opensipsx media-relay[4983]: ERRORTraceback (most recent call
last):#012ERROR  File "/usr/bin/media-relay", line 100, in
#012ERRORfrom mediaproxy.relay import MediaRelay#012ERROR
   File "/usr/lib/python3/dist-packages/mediaproxy/relay.py", line 290, in
#012ERRORclass MediaRelay(MediaRelayBase):#012ERROR
 NameError: name 'MediaRelayBase' is not defined
15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Main process
exited, code=exited, status=1/FAILURE
15:40:07 opensipsx systemd[1]: mediaproxy-relay.service: Failed with result
'exit-code'.

I'm starting the relay with the command...

systemctl start mediaproxy-relay

...I installed Mediaproxy using the Debian package using the instructions
at http://mediaproxy.ag-projects.com/installation-guide/ and
https://github.com/AGProjects/mediaproxy. mediaproxy-dispatcher is starting
successfully.

In the /etc/mediaproxy/config.ini file - everything is left at the default
setting except for...

dispatchers = xxx.xxx.xxx.xxx
advertised_ip = xxx.xxx.xxx.xxx

Certificates are in place in /etc/mediaproxy/tls


Anybody got any ideas about where I've gone wrong
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips 3.1 and Homer 7

2021-01-06 Thread Bogdan-Andrei Iancu 

Hi Sunil,

What is the exact version of opensips you are using ? do an "opensips 
-V" and check for the revision number.

Also

1) OpenSIPS does not sent any QoS data as it does not have it. This is 
something for RTPengine to do


2) The type of the log records was fixed, so consider an update to 
latest 3.1 (3.1.1)


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Bootcamp 2020 online
  https://opensips.org/training/OpenSIPS_eBootcamp_2020/

On 1/5/21 3:01 PM, Sunil More wrote:



Hello All,

I am using homer 7 and opensips 3.1. I am using the tracer module 
along with hep to send to helify-server.


here is a snippet of the config.

#--- Loading Tracer
loadmodule "tracer.so"
modparam("tracer", "trace_on", 1)
modparam("tracer", "trace_id","[tid]uri=hep:hep_dst")
#- Loading PROTOCOLs 
-
loadmodule "proto_udp.so"
loadmodule "proto_tls.so"
loadmodule "proto_hep.so"
modparam("proto_hep", "hep_id", "[hep_dst] 10.153.53.167:9060 
; transport=udp")

modparam("proto_hep", "homer5_on", 1)
modparam("proto_hep", "hep_port", )

Using trace as below

trace("tid", "t", "sip|xlog",100);

I am able to get sip traces in Homer UI . I am using rtpengine with 
opensips and getting rtcp logs.  However


- I am not able to get Qos

- logs are sent to Homer but with *method RTP and type RTP.* (they are 
not displayed in the logs tab)



I tried hep.js and I could populate Qos , SIP msgs and Logs in 
respective tabs.



Could anyone please point me in the right direction?


Sunil More

Manager - DevOps

91 95033 38275

sunil.m...@samespace.com 










___
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