Hello everybody!!! J
Did any of you know or have configured Kamailio servers in redundant and
load distribution mode on geographically dispersed servers. Can you share
some ideas how can this be done. I'm thinking about 2 -3 servers that can be
used to distribute load and for redundancy as well. Is Kamailio capable of
this or this needs to be done on OS level.
Thank you
Roman
Hello,
can you run kamailio with global parameter 'debug=3' and send the syslog
messages for such case?
That will give the hints about what is going wrong there. I see some
characters are hexa encoded, but better see first the logs.
Cheers,
Daniel
On 4/8/11 11:14 AM, Pavel Segeč wrote:
>
> Hi,
>
> I'm using Kamailio SIMPLE AS server as the presence and XCAP solution
> as the extension for my Kamailio based IMS platfom. As the base
> Presence configuration i'm using the default config as is described
> inside of the tutorial from ASIPTO site, it works well for pure ietf
> SIP SIMPLE environment. But when using it with the IMS, I sniff during
> putting the new record 500 Error. May somebody show me a direction
> what should be wrong?
>
> thanks
>
> palo
>
> PUT
> /xcap-root/resource-lists/users/palo/index/~~/resource-lists/list%5B@name=%22doubango%22%5D/entry%5B@uri=%22sip:segi@ims1.sip.uniza.sk%22%5D
> HTTP/1.1
>
> Host: 158.193.139.36:5060
>
> Content-Length: 151
>
> Connection: Keep-Alive
>
> User-Agent: XDM-client/OMA1.1
>
> X-3GPP-Intended-Identity: palo
>
> Content-Type: application/xcap-el+xml
>
> <entry uri="sip:segi@ims1.sip.uniza.sk"
> xmlns="urn:ietf:params:xml:ns:resource-lists">
>
> <display-name>segi(a)ims1.sip.uniza.sk</display-name>
>
> </entry>HTTP/1.1 500 Server error
>
> Via: SIP/2.0/TCP 158.193.152.64:20735
>
> Server: kamailio (3.1.2 (i386/linux))
>
> Content-Length: 0
>
>
>
> __________ Informacia od ESET NOD32 Antivirus, verzia databazy 6025
> (20110408) __________
>
> Tuto spravu preveril ESET NOD32 Antivirus.
>
> http://www.eset.sk
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com
i have
modparam("siputils", "ring_timeout", 30)
but i get
Apr 8 15:32:02 sip /usr/sbin/sip-proxy[23748]: ERROR: siputils [ring.c:378]: ring_insert_callid functionality deactivated, you need to set a positive ring_timeout
Apr 8 15:32:02 sip /usr/sbin/sip-proxy[23748]: ERROR: <core> [route.c:1216]: fixing failed (code=-1) at cfg:/etc/sip-proxy/sip-proxy.cfg:658
Apr 8 15:32:02 sip /usr/sbin/sip-proxy[23748]: ERROR: <core> [route.c:1216]: fixing failed (code=-1) at cfg:/etc/sip-proxy/sip-proxy.cfg:691
when i start sip router (master version).
i looked the code briefly and it tests module param value in fixup
function, which i have not seen before.
is this a bug or am i missing something?
-- juha
Hi all,
I am testing the scenario described here:
http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb
It works great with one instance of Asterisk, but now that I'm testing with
two Asterisk instances to load balance, and I see a problem regarding the
registration forwarding to the second Asterisk.
I tried adding a second "uac_req_send()" bellow the first one, but Kamailio
only sends the first request and the REGISTER never gets to the second
Asterisk:
# Forward REGISTER to Asterisk
route[REGFWD] {
if(!is_method("REGISTER"))
{
return;
}
$var(rip) = $sel(cfg_get.asterisk.bindip);
$uac_req(method)="REGISTER";
$uac_req(ruri)="sip:" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport);
$uac_req(furi)="sip:" + $au + "@" + $var(rip);
$uac_req(turi)="sip:" + $au + "@" + $var(rip);
$uac_req(hdrs)="Contact: <sip:" + $au + "@"
+ $sel(cfg_get.kamailio.bindip)
+ ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n";
if($sel(contact.expires) != $null)
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n";
else
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n";
uac_req_send();
$uac_req(all) = null;
$var(rip2) = $sel(cfg_get.asterisk2.bindip);
$uac_req(method)="REGISTER";
$uac_req(ruri)="sip:" + $var(rip2) + ":" + $sel(cfg_get.asterisk2.bindport);
$uac_req(furi)="sip:" + $au + "@" + $var(rip2);
$uac_req(turi)="sip:" + $au + "@" + $var(rip2);
$uac_req(hdrs)="Contact: <sip:" + $au + "@"
+ $sel(cfg_get.kamailio.bindip)
+ ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n";
if($sel(contact.expires) != $null)
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n";
else
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n";
uac_req_send();
}
I also tried appending another branch and sending the second
uac_req_send() from there, but it is not being sent.
How can I use uac_req_send() several times for the same request or in
parallel?
Thank you,
Alejandro Rios Peña
DISCLAIMER: The opinions expressed are my own, and not necessarily those of
my employer.
<http://www.avatar.com.co>
Hello everyone.
I am a student at University of Žilina (Faculty of Management Science and
Informatics), which has been recently awarded Kamailio 2010 Awards for
various articles about SIP and KAMAILIO on portal nil.uniza.sk.
I am doing a bachelor thesis on topic SIP/SIMPLE - XMPP traversal, but I am
experiencing some problems.
I have a working Kamailio server serving domain sip.uniza.sk and a working
Jabberd2 server serving domain xmpp.uniza.sk.
I am running Kamailio 3.1 with XMPP module with following configuration:
fork=yes
children=4
log_stderror=yes
alias="sip.uniza.sk"
...
loadmodule "XMPP.so"
...
modparam("xmpp", "backend", "component")
modparam("xmpp", "domain_separator", "*")
modparam("xmpp", "gateway_domain", "sip.uniza.sk")
modparam("xmpp", "xmpp_domain", "xmpp-sip.uniza.sk")
modparam("xmpp", "xmpp_host", "server.xmpp.uniza.sk")
modparam("xmpp", "xmpp_password", "secret")
...
#main routing logic
route {
...
if( uri=~"sip:.+[*].+@sip.uniza.sk")
{
# absorb retransmissions ###
if (!t_newtran())
{
sl_reply_error();
return;
}
if (method == "MESSAGE")
{
log("*** xmpp-handled MESSAGE message.\n");
if (xmpp_send_message())
{
t_reply("200", "Accepted");
} else
{
t_reply("404", "Not found");
}
return;
} else
{
t_reply("403","not supported");
exit;
}
}
...
}
To my knowledge there is no configuration required on the Jabberd2 server
(except the password, that the XMPP component authenticates with).
I am trying to enable SIP clients to chat with the XMPP clients and vice
versa.
SIP clients can send messages to XMPP clients. XMPP modules translates SIP
to XMPP and forwards the massage to Jabberd2 server.
URIs look like:
XMPP client from SIP view: xmpp_client*xmpp.uniza.sk(a)sip.uniza.sk
SIP client from XMPP view: sip_client*sip.uniza.sk(a)xmpp-sip.uniza.sk
The message arrives to XMPP client, but he can not reply.
I have sniffed the traffic on the Kamailio server. The XMPP message arrives
to kamailio XMPP module (correct port and everything), but the module
somehow ignores it, doesn't translate XMPP to SIP and doesn't send it to the
SIP recipient.
The sniffed message looks like:
<message xmlns='jabber:client' type='chat' to='SIP_client*sip.uniza.sk@
xmpp-sip.uniza.sk' id='mir_47' from='XMPP_client(a)xmpp.uniza.sk/Miranda
'><body>hello</body></message>
Any suggestions on where can the problem be ??
Do I have to add some lines to routing logic for XMPP module to process the
XMPP message (from Jabberd2) for SIP_client ??
Thanks
Martin
Heya,
just noticed that the TLS certificate on sip-router.org has expired
since 9.8.2010. Try an HTTPS connection to the web-page, i.e.,
https://sip-router.org to see.
It seems to be self-signed though. Anyways, I just wanted to let you know.
Cheers,
--Timo
Hi,
I'm using Kamailio SIMPLE AS server as the presence and XCAP solution as the
extension for my Kamailio based IMS platfom. As the base Presence
configuration i'm using the default config as is described inside of the
tutorial from ASIPTO site, it works well for pure ietf SIP SIMPLE
environment. But when using it with the IMS, I sniff during putting the new
record 500 Error. May somebody show me a direction what should be wrong?
thanks
palo
PUT
/xcap-root/resource-lists/users/palo/index/~~/resource-lists/list%5B@name=%2
2doubango%22%5D/entry%5B@uri=%22sip:segi@ims1.sip.uniza.sk%22%5D HTTP/1.1
Host: 158.193.139.36:5060
Content-Length: 151
Connection: Keep-Alive
User-Agent: XDM-client/OMA1.1
X-3GPP-Intended-Identity: palo
Content-Type: application/xcap-el+xml
<entry uri="sip:segi@ims1.sip.uniza.sk"
xmlns="urn:ietf:params:xml:ns:resource-lists">
<display-name>segi(a)ims1.sip.uniza.sk</display-name>
</entry>HTTP/1.1 500 Server error
Via: SIP/2.0/TCP 158.193.152.64:20735
Server: kamailio (3.1.2 (i386/linux))
Content-Length: 0