*De:* Camila Troncoso [mailto:ctroncoso@redvoiss.net]
*Enviado el:* jueves, 06 de marzo de 2014 16:03
*Para:* sr-users(a)lists.sip-router.org
*Asunto:* 500 I'm terribly sorry, server error occurred (1/SL)
Hi,
I have kamailio 3.2 as LCR with many gateways, weights and priorities.
Out of no ware It presented this error today: 500 I'm terribly sorry,
server error occurred (1/SL). This wasn't happening for all the calls , and
was arbitrary.
I read on google ,that this error comes form t_relay, so the server was
unable to relay the call to the gateway. But all the gateways are reachable
and active.
The server was on load , almost 30 cps. The same configuration have been
running for more than 2 years with any problem.
Could these happened for heavy load? I have children=32 in config file.
Has anyone an idea of what may happened?
Regards,
Camila Troncoso
*Camila Troncoso Solar **|* Ingeniero de Desarollo
+56 2 22408535 *·* +56 9 97327220 | ctroncoso(a)redvoiss.net
Badajoz 130, piso 16, Las Condes | Santiago - CHILE | *www.redvoiss.com
<http://www.redvoiss.com>*
Hi,
I would like to have a Kamailio Registrar/Location server on my private network and another one facing the public side:
KAM1 (Private Registrar) <—> KAM2 (Public Proxy)
I would like also to configure the proxy in this way:
- REGISTRATION TO Public Proxy KAM2 going to Private Registrar KAM1
In the reference guides I’ve seen almost always application specific configuration (WITH_ASTERISK, WITH_FREESWITCH).
Basically, how it is possible to forwards REGISTER messages to a generic upstream Registrar?
Which modules are involved?
I’m using Kamailio 4.1.1
Regards,
Francesco
Hi folks,
I'm new to Kamailio, and I am looking for some documentation on how to write config files, what should be included... etc.. I'm pretty much looking for product documentation and tutorials, not info on SIP (already went through the sip school).
- How do I write a basic config file
- Basic auth and forward examples
I'm familiar with the cookbooks, however they don't really provide context as to what the recommendations do.
Any resources that people could provide would be greatly appreciated.
Thanks,
Richard Seguin
Hi,
I have kamailio 3.2 as LCR with many gateways, weights and priorities.
Out of no ware It presented this error today: 500 I'm terribly sorry,
server error occurred (1/SL). This wasn't happening for all the calls , and
was arbitrary.
I read on google ,that this error comes form t_relay, so the server was
unable to relay the call to the gateway. But all the gateways are reachable
and active.
The server was on load , almost 30 cps. The same configuration have been
running for more than 2 years with any problem.
Could these happened for heavy load? I have children=32 in config file.
Has anyone an idea of what may happened?
Regards,
Camila Troncoso
*Camila Troncoso Solar **|* Ingeniero de Desarollo
+56 2 22408535 *·* +56 9 97327220 | ctroncoso(a)redvoiss.net
Badajoz 130, piso 16, Las Condes | Santiago - CHILE | *www.redvoiss.com
<http://www.redvoiss.com>*
Hello,
Kamailio SIP Server v4.1.2 stable release is out.
This is a maintenance release of the latest stable branch, 4.1, that
includes fixes since release of v4.1.1. There is no change to database
schema or configuration language structure that you have to do on
installations of v4.1.x. Deployments running previous v4.x.x versions
are strongly recommended to be upgraded to v4.1.2.
For more details about version 4.1.2 (including links and guidelines to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2014/03/kamailio-v4-1-2-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hello,
Kamailio SIP Server v4.0.6 stable release is out.
This is a maintenance release of the stable branch 4.0, that includes
fixes since release of v4.0.5. There is no change to database schema or
configuration language structure that you have to do on installations of
v4.0.x. Deployments running previous v4.0.x versions are strongly
recommended to be upgraded to v4.0.6.
For more details about version 4.0.6 (including links and guidelines to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2014/03/kamailio-v4-0-6-released/
Note that 4.0.x is previous stable release series, the latest one is now
4.1.x, with v4.1.2 released today as well.
In addition, 3.3.7 was packaged in order to have it included in the new
APT repository and make transition to newer versions easier for those
still on branch 3.3.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi All,
So an interesting one here. I'm doing pass through registrations using the dispatcher module in Kamailio and I'm using the Path Module to set the Path header In Register request so that Freeswitch knows to follow the route via Kamailio to find the sipPhone in future.
In summary:
[SIP Phone]------[NAT]------[(externalip)Kamailio(internalip)]-------[FS-Registrar]
The problem I'm having is that the Path header is being added with the external ip address of the Kamailio instance not the internal ip e.g. "Path: sip:(externalip);transport=tcp" which mean FS doesn't root new calls out to the SIPPhone correctly via kamailios internal ip.
I have noticed that if I remove the ;transport=tcp from the FS-Register address in my dispatcher group so that the last hop (from kamailio to FS-Register) is done over UDP then the problem corrects itself. (although this does present new issues whilst calling out back along the path from FS, and we also have a prerequisite to use TCP so this doesn't help).
Has anyone had any experience of this issue? I can't see what I've done wrong here.
Many Thanks
Rob
pkg memory run out here:
Mar 4 09:00:20 localhost /usr/sbin/sip-proxy[31923]: ERROR: sqlops [sql_api.c:318]: sql_do_query(): no more memory
then sip proxy crashed here:
(gdb) where
#0 0xb5fce89b in sql_reset_result (res=0xb6ce3438) at sql_api.c:233
#1 0xb5fd18db in sql_do_query (con=0xb6cd1e28, query=0xbfecd248, res=0xb6ce3438) at sql_api.c:410
#2 0xb5fd630d in sql_query (msg=0xb6ce8788, dbl=0xb6cd1e28 "\230\035Ͷ\t", query=0xb70436a8 "\310Y\004\267P", res=0xb6ce3438 "\245\246=|\r3ζ\006") at sqlops.c:209
...
goto error was executed when if(res->vals[i]==NULL) was true and at
error sql_reset_result was called. there the crash happened here:
if(res->vals)
{
for(i=0; i<res->nrows; i++)
{
for(j=0; j<res->ncols; j++)
{
if(res->vals[i][j].flags&PV_VAL_STR
&& res->vals[i][j].value.s.len>0) /* here */
looks to me that it should be tested if res->vals[i] is not null before
executing the if statement.
-- juha
ps. it there any chance to find out from the core dump, why memory run
out, i.e., how was most of it used? amount of pkg memory in this host
was defined to be 8 MB.
-- juha
Hi all, im using the dialog module with db_cassandra backend..
I dont believe this issue is related to cassandra, but its worth mentioning
anyways.
so... I run kamailio, make calls, see dialogs in the DB..
and I Can use "kamctl mi dlg_list" and see that dialogs go away when I
hangup a call..
When I query the DB Backend, I still see the queries, but they have a state
of 5.
I Initially thought this was a bug, but it seems dialogs in state 5 get
cleaned up after a period.
so I moved on.
now , lets restart kamailio..
kamailio loads all dialogs on startup, after kamailio starts I call "kamctl
mi dlg_list" again, and it shows all my dialogs from the DB. they DO show
as "State 5"
but for some reason, these dialogs appear to stick around for a long time,
and the bigger issue it causes me is that my channel limiting (
using get_profile_size ) seems to consider these dialogs ( in state 5 ) as
being active calls.
Please someone point me in the right direction... :)
what am I doing wrong ?
( or is this a bug somewhere )
Sincerely
Jay
