Re: [OpenSIPS-Users] www_challenge qop type failed with AAA

2021-01-05 Thread Michael Vale via Users 
The script wouldn’t load if I specified a auth-int as well as auth.  I removed 
auth-int entirely and the script runs.

> On 6 Jan 2021, at 5:26 am, Vlad Patrascu  wrote:
> 
> Hi Michael,
> 
> Regarding the qop issue, you should pass for that parameter a string value of 
> "auth", "auth-int", or both separated by ','.
> 
> Regards,
> 
> -- 
> Vlad Patrascu
> OpenSIPS Developer
> http://www.opensips-solutions.com
> 
> On 05.01.2021 19:50, Michael Vale via Users wrote:
>> Hi,
>> 
>> I’m attempting to do auth with AAA,
>> 
>> I was met with an error of no Cisco vendor and no SIP-URI-Host Attribute 
>> which I added to the dictionaries.
>> 
>> Now www_challenge thinks either “0” or “1” is an invalid qop type.   
>> 
>> 
>>  
>>  ERROR:auth:fixup_qop: Bad qop type
>> Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_cmd: Fixup 
>> failed for param [2]
>> Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_actions: 
>> Failed to fix command 
>> Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_actions: 
>> fixing failed (code=-1) at /etc/opensips/opensips.cfg:216
>> Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:main: failed to 
>> fix configuration with err code -1
>> Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: INFO:core:cleanup: cleanup
>> Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: NOTICE:core:main: 
>> Exiting
>> Jan 06 04:42:14 unispy opensips[29709]: INFO:core:daemonize: pre-daemon proce
>> 
>>  if (!aaa_www_authorize("")) {
>> www_challenge("", "1");
>>  };
>> 
>> 
>> Could someone please shed some light on the subject?
>> 
>> Also it would be nice if there was another approach to handling the 
>> SIP-URI-Host and Cisco issue or at least some confirmation that my approach 
>> was the best way to deal with it.
>> 
>> 
>> Regards,
>> 
>> Michael.
>> ___
>> 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


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

Re: [OpenSIPS-Users] www_challenge qop type failed with AAA

2021-01-05 Thread Vlad Patrascu 

Hi Michael,

Regarding the qop issue, you should pass for that parameter a string 
value of "auth", "auth-int", or both separated by ','.


Regards,

--
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 05.01.2021 19:50, Michael Vale via Users wrote:

Hi,

I’m attempting to do auth with AAA,

I was met with an error of no Cisco vendor and no SIP-URI-Host Attribute which 
I added to the dictionaries.

Now www_challenge thinks either “0” or “1” is an invalid qop type.  



 ERROR:auth:fixup_qop: Bad qop type
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_cmd: Fixup 
failed for param [2]
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_actions: Failed to 
fix command 
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_actions: 
fixing failed (code=-1) at /etc/opensips/opensips.cfg:216
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:main: failed to 
fix configuration with err code -1
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: INFO:core:cleanup: cleanup
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: NOTICE:core:main: Exiting
Jan 06 04:42:14 unispy opensips[29709]: INFO:core:daemonize: pre-daemon proce

  if (!aaa_www_authorize("")) {
 www_challenge("", "1");
  };


Could someone please shed some light on the subject?

Also it would be nice if there was another approach to handling the 
SIP-URI-Host and Cisco issue or at least some confirmation that my approach was 
the best way to deal with it.


Regards,

Michael.
___
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] www_challenge qop type failed with AAA

2021-01-05 Thread Michael Vale via Users 
Hi,

I’m attempting to do auth with AAA,

I was met with an error of no Cisco vendor and no SIP-URI-Host Attribute which 
I added to the dictionaries.

Now www_challenge thinks either “0” or “1” is an invalid qop type.  



 ERROR:auth:fixup_qop: Bad qop type
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_cmd: Fixup 
failed for param [2]
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_actions: 
Failed to fix command 
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:fix_actions: 
fixing failed (code=-1) at /etc/opensips/opensips.cfg:216
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: ERROR:core:main: failed to 
fix configuration with err code -1
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: INFO:core:cleanup: cleanup
Jan 06 04:42:14 unispy /usr/sbin/opensips[29711]: NOTICE:core:main: Exiting
Jan 06 04:42:14 unispy opensips[29709]: INFO:core:daemonize: pre-daemon proce

 if (!aaa_www_authorize("")) {
www_challenge("", "1");
 };


Could someone please shed some light on the subject?

Also it would be nice if there was another approach to handling the 
SIP-URI-Host and Cisco issue or at least some confirmation that my approach was 
the best way to deal with it.


Regards,

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

[OpenSIPS-Users] Opensips 3.1 and Homer 7

2021-01-05 Thread Sunil More 
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

Re: [OpenSIPS-Users] Introducing OpenSIPS 3.2

2021-01-05 Thread Bogdan-Andrei Iancu 

A Happy New Year to you all !!

Have you filled in the poll for OpenSIPS 3.2 planning ? Time is ticking 
and the deadline is getting closer, so do it now https://bit.ly/2WDmAlV.


Keep in mind thatOpenSIPS is for the community, by the community. So 
your opinion matters!


Best 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 12/23/20 4:27 PM, Bogdan-Andrei Iancu wrote:



Well, let's spin the wheel again for a new cycle – one more year, one 
more evolution cycle, one more OpenSIPS major release. Even more, a 
new topic is to be addressed. So let me introduce you to the upcoming 
OpenSIPS 3.2 .


For the upcoming OpenSIPS 3.2 release the main focus is on the 
*/in-cloud integration and distribution /*topic. Shortly said, this 
translates into:


  * distributed call center / queuing
  * clustering support for modules
  * Multi-level presence subscription
  * RTP stream re-anchoring
  * integration with Kafka, MQTT, Prometheus, ElasticSearch
  * AWS support - DynamoDB, SSM, SQS, SNS
  * script driven Back-2-Back

For the full list with technical description and details, visit :

https://www.opensips.org/Development/Opensips-3-2-Planning


*IMPORTANT*

As community is important to us and we want to align the OpenSIPS 
roadmap with the needs of our users, be part of the shaping and 
decision making for the OpenSIPS 3.2 Dev Plan via this *Feature Survey 
* - any feedback is important and it matters to us.



Best regards and enjoy the winter holidays!!

--
Bogdan-Andrei Iancu

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


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