[OpenSIPS-Users] Call Center Module failed to load
Hey guys,
I am trying to load call_center module on openSIPS 2.4 but getting a lot of
erros. Here is my configuration -
# B2B Module
loadmodule "b2b_entities.so"
loadmodule "b2b_logic.so"
modparam("b2b_logic", "script_scenario",
"/usr/local/etc/opensips/scenario_callcenter.xml")
# Call center module
loadmodule "call_center.so"
modparam("call_center",
"db_url","mysql://opensipsuser:password@localhost/opensips") # CUSTOMIZE ME
#modparam("call_center", "acc_db_url","mysql://password@localhost/opensips") #
CUSTOMIZE ME
#modparam("b2b_logic", "script_scenario",
"/usr/local/etc/opensips/scenario_callcenter.xml")
modparam("call_center", "b2b_scenario", "call center")
modparam("call_center", "wrapup_time", 3)
--
I have tried all combinations but still no luck, I also have db_default_url
variable defined. And these are the error logs -
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]: INFO:dialplan:mod_init:
initializing module...
Jan 10 19:29:31 98 mysqld[1393]: 2020-01-10 19:29:31 28 [Warning] Aborted
connection 28 to db: 'opensips' user: 'opensipsuser' host: 'localhost' (Got an
error reading communication packets)
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]: INFO:call_center:mod_init:
Call Center module - initializing
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]:
WARNING:call_center:cc_load_db_data: table "cc_flows" empty
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]:
CRITICAL:call_center:mod_init: failed to load callcenter data
Jan 10 19:29:31 98 opensips[1599]: already running.
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]: ERROR:core:init_mod: failed
to initialize module call_center
Jan 10 19:29:31 98 systemd[1]: Started LSB: Start the OpenSIPS SIP server.
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]: ERROR:core:main: error while
initializing modules
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]: INFO:core:cleanup: cleanup
Jan 10 19:29:31 98 /usr/local/sbin/opensips[1617]: NOTICE:core:main: Exiting
Jan 10 19:29:31 98 opensips: INFO:core:daemonize: pre-daemon process exiting
with -1
I am thinking that this is mysql related issue or openSIPS bug. I have also
adjusted max_allowed_packet=256M on mysql server. Please help.
Thanks and regards___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Opensips Control Panel
Hello list, is there a way to have a LOG aboute the activity of OpenSIPs Control Panel? Thank you Regards -- --- I'm SoCIaL, MayBe ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] update from repo fails
Thanks! пт, 10 янв. 2020 г., 19:07 Nick Altmann : > Must be fixed for now. > > чт, 9 янв. 2020 г. в 12:13, Nick Altmann : > >> Hi, >> >> Thanks for reporting. I'll take a look at this today later. >> >> чт, 9 янв. 2020 г. в 11:35, Антон Ершов : >> >>> Hi, >>> when I try to upgrade from a repository with nightly builds I get this >>> error >>> rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by >>> opensips-yum-nightly-3.0-5.el7.noarch >>> >>> found on the network that you need to rebuild a package that supports >>> this dependency. >>> How can you solve this problem yourself? >>> ___ >>> 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] update from repo fails
Must be fixed for now. чт, 9 янв. 2020 г. в 12:13, Nick Altmann : > Hi, > > Thanks for reporting. I'll take a look at this today later. > > чт, 9 янв. 2020 г. в 11:35, Антон Ершов : > >> Hi, >> when I try to upgrade from a repository with nightly builds I get this >> error >> rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by >> opensips-yum-nightly-3.0-5.el7.noarch >> >> found on the network that you need to rebuild a package that supports >> this dependency. >> How can you solve this problem yourself? >> ___ >> 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] B2B user agent logic
Hi, Donat! Indeed, the B2B module(s) are not compatible with the dialog module. However, if your purpose is just to have different callids between the two legs, why not using the topology hiding module[1], which does change the callids (using the "C" flag for the topology_hiding() function[2]) and is built on top of the dialog module. The B2B does indeed offer a similar behavior, but it is usually used for much more complex calling scenarios - if you don't need those complex scenarios, simply use the topology_hiding mode. [1] https://opensips.org/html/docs/modules/3.0.x/topology_hiding.html [2] https://opensips.org/html/docs/modules/3.0.x/topology_hiding.html#func_topology_hiding Best regards, Răzvan On 1/10/20 5:21 PM, Donat Zenichev wrote: Hello OpenSIPS community! I have a brief question regarding how to better implement B2B user agent logic, within OpenSIPS installation. The goal is quite simple: - I have OpenSIPS as a routing system (making decisions on calls) - OpenSIPS at the same time separates dialog into two legs (so two Call-IDs as result) Firstly I've started looking into b2b_logic + b2b_entities modules I read manuals provided by OpenSIPS dev team and everything is quite clear for me. But, from what I understand provided b2b module is not compatible with a dialog module (paragraph 6 at Back-to-Back User Agent manual). But dialog module is quite significant for me, at least since of "dialog_replication_cluster" parameter. Another feature of the b2b_logic module is, that it only implements scenarios within a separate xml configuration file. And from the script routing you're only able to access coming requests and responses in a read-only mode. To sum up, the general goal is to separate call into two legs, to let both legs have different call-ids. And it's also quite important to be able to rule changes on requests (e.g. resetting of R-URI) from the routing script. Everything from mentioned above led me to a thought, that there could be some much elaborate solution for implementation of B2B within OpenSIPS installation. For sure b2b_logic and b2b_entities modules are great! But still I'm looking for a bit different installation. I know, OpenSIPS is a SIP proxy and it's not supposed to be run with a role of B2BUA. But still, might be someone can share his/her own experience and hint some better way out for this? Many thanks in advance and have a nice day! -- Best regards, Donat Zenichev ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2B user agent logic
If you just need to change the Call-ID you can look at the topology_hiding module [1]. It has the ability to mangle the Call-ID in addition to other identifying information. If you must have B2BUA functionality that won’t work. I believe that the B2BUA messages can be “caught” and modified to some extent in local_route [2]. [1] - https://opensips.org/html/docs/modules/3.0.x/topology_hiding.html [2] - https://www.opensips.org/Documentation/Script-Routes-3-0#toc6 Ben Newlin From: Users on behalf of Donat Zenichev Reply-To: OpenSIPS users mailling list Date: Friday, January 10, 2020 at 10:22 AM To: "users@lists.opensips.org" Subject: [OpenSIPS-Users] B2B user agent logic Hello OpenSIPS community! I have a brief question regarding how to better implement B2B user agent logic, within OpenSIPS installation. The goal is quite simple: - I have OpenSIPS as a routing system (making decisions on calls) - OpenSIPS at the same time separates dialog into two legs (so two Call-IDs as result) Firstly I've started looking into b2b_logic + b2b_entities modules I read manuals provided by OpenSIPS dev team and everything is quite clear for me. But, from what I understand provided b2b module is not compatible with a dialog module (paragraph 6 at Back-to-Back User Agent manual). But dialog module is quite significant for me, at least since of "dialog_replication_cluster" parameter. Another feature of the b2b_logic module is, that it only implements scenarios within a separate xml configuration file. And from the script routing you're only able to access coming requests and responses in a read-only mode. To sum up, the general goal is to separate call into two legs, to let both legs have different call-ids. And it's also quite important to be able to rule changes on requests (e.g. resetting of R-URI) from the routing script. Everything from mentioned above led me to a thought, that there could be some much elaborate solution for implementation of B2B within OpenSIPS installation. For sure b2b_logic and b2b_entities modules are great! But still I'm looking for a bit different installation. I know, OpenSIPS is a SIP proxy and it's not supposed to be run with a role of B2BUA. But still, might be someone can share his/her own experience and hint some better way out for this? Many thanks in advance and have a nice day! -- Best regards, Donat Zenichev ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] B2B user agent logic
Hello OpenSIPS community! I have a brief question regarding how to better implement B2B user agent logic, within OpenSIPS installation. The goal is quite simple: - I have OpenSIPS as a routing system (making decisions on calls) - OpenSIPS at the same time separates dialog into two legs (so two Call-IDs as result) Firstly I've started looking into b2b_logic + b2b_entities modules I read manuals provided by OpenSIPS dev team and everything is quite clear for me. But, from what I understand provided b2b module is not compatible with a dialog module (paragraph 6 at Back-to-Back User Agent manual). But dialog module is quite significant for me, at least since of "dialog_replication_cluster" parameter. Another feature of the b2b_logic module is, that it only implements scenarios within a separate xml configuration file. And from the script routing you're only able to access coming requests and responses in a read-only mode. To sum up, the general goal is to separate call into two legs, to let both legs have different call-ids. And it's also quite important to be able to rule changes on requests (e.g. resetting of R-URI) from the routing script. Everything from mentioned above led me to a thought, that there could be some much elaborate solution for implementation of B2B within OpenSIPS installation. For sure b2b_logic and b2b_entities modules are great! But still I'm looking for a bit different installation. I know, OpenSIPS is a SIP proxy and it's not supposed to be run with a role of B2BUA. But still, might be someone can share his/her own experience and hint some better way out for this? Many thanks in advance and have a nice day! -- Best regards, Donat Zenichev ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
