Hello everyone,
I was looking for documentation for Radius AAA + Openser. I tried to
google but the links provided are not working. i think since the site
has been renamed. Can any provide me document if saved or any other
related link.
Link to which i was referring .
http://openser.org/docs/openser-radius-1.0.x.html
Regards,
Amit Jain
Hello everyone,
I was looking for documentation for Radius AAA + Openser. I tried to
google but the links provided are not working. i think since the site
has been renamed. Can any provide me document if saved or any other
related link.
Link to which i was referring .
http://openser.org/docs/openser-radius-1.0.x.html
Immediate help required :(
Regards,
Amit Jain
Hi, imagine this simple case:
--------------------------
route {
t_on_branch("1");
t_on_failure("2");
xlog("We are in 'route'");
t_relay("1.1.1.1");
}
branch_route[1] {
xlog("We are in 'branch_route[1]'");
# do something....
}
failure_route[2] {
xlog("We are in 'failure_route[2]'");
append_branch();
t_relay("2.2.2.2");
}
---------------------------
In case an error occurs when forwarding the request to 1.1.1.1 this would be
the screen log output:
We are in 'route'
We are in 'branch_route[1]'
We are in 'failure_route[2]'
We are in 'branch_route[1]'
This is: branch_route[1] will also be runned **again** after the failure route
since it was loaded in the first forward attemp.
I really don't know if this is intuitive or not. The only way to "dissable"
branch_route[1] in the failure route is by adding:
-------------------
failure_route[2] {
t_on_branch("2"); # <--- Dissable t_on_branch("1")
xlog("We are in 'failure_route[2]'");
append_branch();
t_relay("2.2.2.2");
}
branch_route[2] {
xlog("We are in 'branch_route[2]'");
# Nothing to do here.
# This route is neccesary to dissable t_on_branch("1")
}
------------------
This would show:
We are in 'route'
We are in 'branch_route[1]'
We are in 'failure_route[2]'
We are in 'branch_route[2]'
What about if "t_on_branch" wouldn't remain loaded after a failure route or
serial forking? wouldn't be more intuitive to re-enable it explicitely when
required?
--
Iñaki Baz Castillo
Hi Muhammad,
I will check the problem this week and return to you soon.
Regards,
Flavio
----- Mensagem original ----
De: muhammad akl <muhammad.akl(a)gmail.com>
Para: Flavio Goncalves <flavio(a)asteriskguide.com>
Cc: users(a)lists.kamailio.org
Enviadas: Domingo, 10 de Agosto de 2008 12:44:47
Assunto: Re: [Kamailio-Users] serMyAdmin login problem invalid username and/or password
thx Flavio for ur response but i still have another question the main problem with the user "admin@localhost " and password "openserrw" that were created by the openser_mysql.sh is still happening got the same message "invalid username and/or password "
but when i removed that account from the subscriber table and used the openser.sql file from sermyadmin i have successfully logged in but after modifying the openser.sql file to match my environment
so after that i tried to register with a new account from the home page using register button besides to login button and filled the account's information there everything worked fine
but the problem happend here now is when i logged with the "admin@setup" and password "secret " account to approve the new account for users i got this message
pastebin.com/m7154020b
p.s for alot of testing i have used more than one version of serMyAdmin beginning with ver 0.3 to 0.7 !!
sorry for my poor english as am not native
BR
muhammad
Hi Muhammad,
Check the updated procedure at www.sermyadmin.org. The default login is asmin@setup, password secret as stated in the procedure.
Flavio E. Goncalves
----- Mensagem original ----
De: muhammad akl <muhammad.akl(a)gmail.com>
Para: users(a)lists.kamailio.org
Enviadas: Domingo, 10 de Agosto de 2008 6:28:53
Assunto: [Kamailio-Users] serMyAdmin login problem invalid username and/or password
hey all
i'm trying to configure sermyadmin web interface to administrate openser-1.2.2 through it firstly i installed apache-tomcat and configure it successfully then i downloaded the sermyadmin.war and copied it to /usr/local/tomcat/webapps then downloaded mysql-jdbc and copied it to /usr/local/tomcat/lib also configure the context.xml and modified the Context element and added the user have full privileges to access openser databases then when tried to login with user "admin@locahost" and pass " openserrw" default values created by the openser_mysql.sh i got invalid username or password ? any suggestions ?
serMyAdmin version used .7-BETA
i also tried the howto found in sermyadmin.org but with no success by trying to use the prepared openser.sql file
if anyone could i'd appreciate that
Hi, I have a scenario in which the call is first forwarded to user location
using MediaProxy (so I modify the SDP in OpenSer) and if it gets a error
response a failure route forwards the request to a media server with public
IP for which I don't need and don't want to use MediaProxy.
But since I change the SDP in the first forwarding (to the user) then I can't
use the original SDP in the sequential forwarding to the media server. Is
possible to do it?
Thanks a lot.
--
Iñaki Baz Castillo
hey all
i'm trying to configure sermyadmin web interface to administrate
openser-1.2.2 through it firstly i installed apache-tomcat and configure it
successfully then i downloaded the sermyadmin.war and copied it to
/usr/local/tomcat/webapps then downloaded mysql-jdbc and copied it to
/usr/local/tomcat/lib also configure the context.xml and modified the
Context element and added the user have full privileges to access openser
databases then when tried to login with user "admin@locahost" and pass "
openserrw" default values created by the openser_mysql.sh i got invalid
username or password ? any suggestions ?
serMyAdmin version used .7-BETA
i also tried the howto found in sermyadmin.org but with no success by trying
to use the prepared openser.sql file
if anyone could i'd appreciate that
Hello everybody,
A new project - OpenSIPs (Open SIP Server) - became active today, with
its first release (OpenSIPS 1.4.0).
What is OpenSIPS about?
OpenSER History:
----------------
Voice System started the OpenSER project with a vision of running an
open project that will deliver a professional software. Along the years
Voice System was the main contributor and sustainer of the OpenSER
project, organizing conferences, events and tutorials, all aiming to
consolidate OpenSER as a top solution for industry VoIP.
OpenSER Issues:
---------------
In the past time, several critical problems related to OpenSER project
were identified by us:
- the need for a new reliable release - delayed or low-quality releases
are affecting the credibility of the project
- degradation of the project quality - testing, performance measurements
and code quality control are overlooked
- lack of the control, management and coordination of the project -
critical project issues could not be handled or solved
OpenSIPS Solutions:
--------------------
OpenSIPS is a continuation of the OpenSER project - we have a moral
obligation to develop and deliver the high quality and reliable software
we envisioned when starting OpenSER.
1) a 6 months release cycle, but with no compromise for the technical
issues
2) extensive testing and performance measurements before each major release
3) contributions are guaranteed to be answered and integrated (if
accepted) in less than 1 month
4) code review, architecture control and integrated design for software
quality
5) technical management with a strict developer hierarchy and developer
cooperation to prevent deadlocks or un-availabilities
6) intellectual honesty by having decisions taken on value-based
criteria and arguments.
To find more about the project, see the official web page :
http://www.opensips.org
OpenSIPS 1.4.0 release:
-----------------------
First major release of OpenSIPS is n**ow available. It incorporates new
functionalities like
* dialog profiling extension
* local route for internally generated requests
* dial plan / translation module
* general NAT traversal module (for non-invite signalling)
* peering and rate limit (traffic shaping) modules
, enhancements like:
* SRV load balancing (based on weights)
* nonce re-usage verification (safer authentication)
and bug fixing - code, specs and functionality bugs.
The full Changelog is available on the web site:
To get the OpenSIPS 1.4.0 version, see the download page at:
http://www.opensips.org/index.php?n=Resources.Downloads
Best regards,
Bogdan
Hello,
Does openser as soon as receives 603 Declined from the termination kills the call and not route it to the failover route?
Is this correct?
Thanks,
KC
---------------------------------
Unlimited freedom, unlimited storage. Get it now
I will be out of the office starting 08/08/2008 and will not return until
08/11/2008.
Please contact the CSC at 888-899-4227 if you need immediate assistance.