Hello guys,
Is there a method upon using lookup("location") to also pull out the
"socket" information for the original location the UAC registered to, for
scenarios of this example:
P1 & P2 share same usrloc database.
UA1 registers to P1
UA2 registers to P2
UA1 calls UA2
UA1 invites -> P1 -> INVITES -> UA2 (bypassing P2 -- where the actual nat
binding is).
Now upon P1 looking up usrloc for UA2, I would like to recognize that P1 is
not the Proxy to deliver the call, and forward the request to P2 to send to
UA2.
So currently I have:
UA1 INVITE -> P1 INVITE -> UA2
I wish to have:
UA1 INVITE -> P1 INVITE -> P2 INVITE -> UA2
Is there an easy method to do this? I have been looking at the new nat
traversal module it looks like it is doable with this (any further input as
far as that?). Also is it possible with the classic Nat Helper module? Any
input is appreciated, thanks!
Hello,
First off going to thank you guys ahead of time, I'm currently running
into the following issue:
I'm trying to account for internal calls, i.e. example scenarios such as:
UA1 and UA2 are both on P1
UA1 calls UA2 so, effectively: UA1 -> P1 -> UA2
Now the problem I'm running into is with the direction of the calls, I am
having trouble accounting for both sides of the call, i.e. I store an avp
such as: $avp(s:account-id)
Obviously the AVP is going to be set to one account_id, and my problem is
that the Callee is what ends up "being accounted" for not, the "Caller".
Another scenario I would like some insight on and having problems with is:
UA1 is on P1, UA2 is on P2
UA1 calls P1 -> P2 -> UA2
same type scenario, only one end of the call (Callee is being accounted for)
-- how can I accurately account using kamailio acc module for both sides of
the call for both users?
Any thought / input on this is very much appreciated, thanks!
Hi. When starting SER, I get the following line in the logs:
new_connection(): Access denied for user 'ser'@'localhost' (using
password: YES)
I have the following line in ser.cfg:
modparam("auth_db|uri_db|usrloc", "db_url",
"mysql://ser:heslo@localhost/ser")
along with the required modules loaded.
I can log into mysql with mysql -h localhost -u ser -pheslo ser , so I
think all the mysql stuff is set right and the parameter has the correct
info.
Any ideas why it's not connecting with the ser.cfg file setup?
Thanks.
I am working to get LCR implemented on my migration system, and when I
try to start kamailio i find the below information in the log file,
and kamailio fails to start. My lcr table has 30667 rows in it. I
have read about changing the config.h file to increase the private
memory, but my question is how much should I allocate. I forsee
going up to more than 200,000 routes within the next 12 month period.
I am currently working towards migrating up from openser 1.3.3 to
kamailio-1.4.4-notls. I am currently not using LCR in my production
openser 1.3.3 system. This is new functionality that we are
implementing as part of the upgrade.
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:db_mysql:db_mysql_convert_row: no private memory left
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:db_mysql:db_mysql_convert_rows: error while converting row #2808
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:db_mysql:db_mysql_convert_result: error while converting rows
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:db_mysql:db_mysql_store_result: error while converting result
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:core:db_do_query: error while storing result
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:lcr:reload_gws: Failed to query lcr data
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
CRITICAL:lcr:mod_init: Failed to reload gateways and routes
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:core:init_mod: failed to initialize module lcr
Apr 29 17:13:49 n01-sip-c61-56-atl /sbin/kamailio[5372]:
ERROR:core:main: error while initializing modules
Thanks
Stagg