Re: [OpenSIPS-Users] set_advertised_address suspected bug 1.9
Hi, Terrance! No, you cannot change the advertised address in the onreply_route, since the Route headers have already been sent to your UAS. The proper way to do this is to make all the interface changes in the request route. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 03/24/2015 09:19 PM, Terrance Devor wrote: Hello Everyone, We are using Opensips 1.9.x and seeing that set_advertised_address is not changing the recoird route within the on_reply route. What we are trying to do is change the record route for internal vs. external signalling. Is it not possible to change the advertised address within the on_reply_route? Kind Regards, Terrance. ___ 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] opensips 1.9 error (I know it's very generic)
Thx for the reply, but what is the function of rtpproxy? I use asterisk to handle my rtp (media). So can I remove the module from opensip being loaded? Also network congestion, but is on the localhost which is itself, how can there be network congestion? Thx. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/opensips-1-9-error-I-know-it-s-very-generic-tp7596135p7596150.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] set_advertised_address suspected bug 1.9
Hello Razvan, Thank you for your response. The problem I am experiencing is that I cannot catch the 200OK that OpenSIPS sends out except for within the onreply_route. I put debug messages all over the script, and the only place the 200OK that opensips would fire was in the onreply. Can you please tell me where to catch the 200 that OpenSIPS sends out within the request route? Thanks in Advance, Terrance ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Opensips 1.11 on Centos 6.6, running but not listening?
I am currently running Opensips 1.9 on Debian Whizzy, but as stated on my other thread, I am getting some weird error which opensips would suddenly stop working. So, I am starting a new installation of Opensips 1.11 on Centos 6.6 using the yum install method: 1. I was able to install yum opensips install with no issue, but there are some module it didn't install which I need (e.g. db_unixodbc and db_mysql and httpd) 2. So I went ahead download the source and all the dependency files needed and re-complie the oepnsips to get those .so files 3. After some tweaking of the database table structure and some other stuff, I was able to get opensips 1.11 running without error (on the message.log file) using my 1.9 config file. So I did opensipsctl restart (just to make sure opensips starts) I see: INFO: Restarting OpenSIPS : INFO: stopped INFO: Starting OpenSIPS : INFO: Removing stale PID file /var/run/opensips.pid. INFO: started (pid: 2079) but when I try to use a VoIP device to register to it, it doesn't response. thus I did: sudo netstat -plnt The only think I see that opensips is listening on is port by PID 2080 (I don't see 2079 at all) So what is happening? why no error and it seems opensips running but yet is not listsening on port 5060? I have 2 nic card and eth0 is the one with public IP and the default route where as the eth1 is the one with private IP and no default route. Thus I am sure everything is route out of the eth0 (public IP). When I do simply the command opensips, it would simply return: Listening on udp: xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx]:5060 Aliases: *: (my FQDN):* So it looks like it think is listening on port 5060 but is not? Any help would be appreciated greatly! Thank you! -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-11-on-Centos-6-6-running-but-not-listening-tp7596152.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] DROUTING module changing Carrier IDs
I am using OpenSIPS 1.11 and I am recently getting some weird behavior from the
DROUTING module. The module is corrupting the Carrier ID that is being returned
via AVP. This behavior is occurring only with the Carrier ID, not the gateway
or rule IDs, and only when it is returned from the DROUTING module via
dr_is_gw() or do_routing(). If I query the database directly using AVPOPS, the
Carrier ID is returned correctly.
I have the following configuration. The startup_route was added specifically
for this issue.
Dynamic ROUTING module
loadmodule drouting.so
modparam(drouting, db_url, CFG_DB_URL)
modparam(drouting, persistent_state, DISABLE)
modparam(drouting, probing_interval, ENABLE)
modparam(drouting, force_dns, ENABLE)
modparam(drouting, ruri_avp, '$avp(dr_ruri)')
modparam(drouting, gw_id_avp, '$avp(dr_gw_id)')
modparam(drouting, gw_priprefix_avp, '$avp(dr_gw_prfx)')
modparam(drouting, rule_id_avp, '$avp(dr_rule_id)')
modparam(drouting, rule_prefix_avp, '$avp(dr_rule_prfx)')
modparam(drouting, carrier_id_avp, '$avp(dr_carr_id)')
.
.
.
startup_route {
avp_db_query(select carrierid from dr_carriers, $avp(ids));
for ($var(id) in $(avp(ids)[*]))
xlog(L_INFO, Carrier ID: $var(id)\n);
}
.
.
.
route[get_route]
{
if (!do_routing($avp(dr_group), , , $var(rule_attr), $var(gw_attr),
$var(carr_attr)))
{
xlog(L_ERR, get_route: failure from do_routing! $retcode\n);
route(reply_error, 500, Server Internal Error);
}
xlog(L_INFO, get_route: rule_attr - $var(rule_attr)\n);
xlog(L_INFO, get_route: gw_attr - $var(gw_attr)\n);
xlog(L_INFO, get_route: carr_attr - $var(carr_attr)\n);
xlog(L_INFO, get_route: ruri - $avp(dr_ruri)\n);
xlog(L_INFO, get_route: gw_id - $avp(dr_gw_id)\n);
xlog(L_INFO, get_route: gw_prfx - $avp(dr_gw_prfx)\n);
xlog(L_INFO, get_route: rule_id - $avp(dr_rule_id)\n);
xlog(L_INFO, get_route: rule_prfx - $avp(dr_rule_prfx)\n);
xlog(L_INFO, get_route: carr_id - $avp(dr_carr_id)\n\n);
}
The output from the above execution is:
opensips[9801]: Carrier ID: IndyEdges
opensips[9801]: Carrier ID: Level3-VT
opensips: INFO:core:daemonize: pre-daemon process exiting with 0
opensips[9801]: get_route: rule_attr -
opensips[9801]: get_route: gw_attr -
opensips[9801]: get_route: carr_attr - id=pai;history=hi
opensips[9801]: get_route: ruri - null
opensips[9801]: get_route: gw_id - Level3-VT1
opensips[9801]: get_route: gw_prfx - +
opensips[9801]: get_route: rule_id - 4
opensips[9801]: get_route: rule_prfx - 1
opensips[9801]: get_route: carr_id - Level3-VT#012
You can see that the string '#012' has been appended to the Carrier ID. So far
it has always been that string appended to the ID.
It started occurring after I moved from a RHEL 7 server using MariaDB to a RHEL
6 server using MySQL, but in both cases I am using the provided OpenSIPS
scripts to create all database tables.
Any help would be appreciated.
Ben Newlin
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
