Hi guys,
I've baning my head for the last 6 7 days with something that have to
be universally simple but obviously for me it is not, so please do
help.
I have the following setup.
xx.xx.xx.xx (real IP 1:1 NAT) -> 10.2.47.201
Kamailio listens on 10.2.47.201
I have setup a domain xxx.itradebg.com and I've made the appropriate
records in the DNS.
I have inserted the domain xxx.itradebg.com in the domain table in the
database and kamctl domain show shows the correct thing.
Now when I try to register 999(a)xxx.itradebg.com I get Request timed out
I have this in my config:
if (is_method("REGISTER") || from_uri==myself)
{
if (!auth_check("$fd", "sip", "1")) {
auth_challenge("$fd", "0");
exit;
}
}
if (from_uri!=myself && uri!=myself)
{
if(lookup_domain("$fd", "@from.uri.host")){
xlog("LOCAL DOMAIN -> REGISTER");
exit;
}
else{
xlog("L_WARN","FROM NOT LOCAL");
sl_send_reply("403","Sorry mate not relaying");
exit;
}
}
By the time of writing this I realised that this should be all
rewritten to this only, as the second check is useless:
if (is_method("REGISTER") || from_uri==myself)
{
if (!auth_check("$fd", "sip", "1")) {
auth_challenge("$fd", "0");
exit;
}
}
However I get 401 Unauthorized. The previous setup was giving me 408 -
Request Timed out...
I am pretty sure I have the passwords correct.
What I cannot understand is why authentication fails ?!
Also, how do I set kamailio to print debug output ?
debug=9
log_stderror=no
This is what I have in the .conf file. /var/log/messages seems to only
have what I have printed with xlog... (think)
I am really out of ideas... perhaps I need some sleep.
Anyway any input is helpful guys.
Thanks,
Rumen
http://itradebg.com
Hello,
I started to use Kamailio few months ago. Maybe this is a stupid issue but
I can´t start Kamailio with NAT TRAVERSAL module and $keepalive.socket
pseudo-variable.
My script configuration is the default template adding this lines
(extracted from nat traversal doc):
...
loadmodule "nat_traversal.so"
...
...
$fs = $keepalive.socket($du);
...
I have this error:
-e
0(17455) ERROR: <core> [pvapi.c:501]: error searching pvar "keepalive"
0(17455) ERROR: <core> [pvapi.c:705]: wrong char [e/101] in [$keepalive]
at [9 (0)]
0(17455) : <core> [cfg.y:3330]: parse error in config file
/etc/kamailio/kamailio.cfg, line 410, column 8-17: unknown script pseudo
variable $keepalive
ERROR: bad config file (1 errors)
I tried in this environments:
Ubuntu 10.04.4 LTS x86_64 Kamailio 3.3.3+git20130128+lucid1
Ubuntu 10.04.4 LTS i686 Kamailio 3.0.4+lucid1
Ubuntu 12.04.1 LTS x86_64 Kamailio 3.3.2+precise1
All packages instaled from deb repositories (http://deb.kamailio.org/)
I think there are problem parsing "$keepalive.socket" pseudovariable,
because Kamailio doesn´t scape this character "." and it doesn´t recognise
the pseudovar.
Does anyone have this problem?
Regards
Dear ,
Can you please provide me link of sip express live Cd router .. I want to use it... waiting your kind response
Regards,
Kashif Shoukat | Analyst Software Engineer |
Work : + 1.202.289.9898 x 9077
Mobile : + 92.323.431.8548
Skype: kashif.shoukat.dgs
www.dgsworld.com<http://www.dgsworld.com/>
dgs
deliberate by design
This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by replying to kashif.shoukat(a)dgsworld.com<mailto:kashif.shoukat@dgsworld.com> and delete the message.
Hello all.
Our company buy Thawte SSL Web server certificate.
I'm enabled in Kamailio 3.3 TLS support and configured him.
Adding to "myhost.pem" certificate, two "intermediate" certificates (like
in chain) "cat myhost.pem SSL_SecondaryCA.pem SSL_PrimaryCA.pem >
chain-cert.pem".
Remark: I use this chain on apache2. And Android trusted to this
certificate chain.
After this i use chain-cert.pem with KAMAILIO 3.3 and SIP client "BRIA
Android". "Bria Android" says certificate is not trusted. Next step "BRIA
IPHONE" and certificate chain works (trusted)!
BRIA support says me - BRIA don't trusts certificate if system don't trusts.
Why Android don't trusts to my chain-certificates with KAMAILIO? If his
trust to same certificate with Apache?
I'm understand this is not Kamailio problem, but maybe any one who have
expirience in this problem help me? I know about bouncycastle, but this is
not best decision for me. Maybe something else can help?
I tryed this with Android 2.3.7, 4.0, 4.1.
Best regards Kirill.
Hi,
I think that it is more than likely not implemented, but is there any
event-route that is triggered just before event_route[dialog:start] ? I
need to check some security flags before the dialog is created. But it is
too early too check them in relay route..
Mino
Hi,
I made some DB test on our HA cluster, and I got that for 1 process I have
1000 queries/sec and for 11 processes 3000 queries/sec. That's why I would
to ask if every kamailio process that is spawned has its own database
connection or queries are put in the queue and executed by some main
process ? I would like to know this, so that I could assess maximum call
count/sec that db can handle.
Thank you,
Mino
Hello,
A while ago I came across the siptrace and sipcapture modules and thought this would be a good way to generate logging out of all the SIP messages that are passed through Kamailio and stored in the siptrace/sipcapture table.
My idea was to extract certain values from SIP messages and store these in our database. Also each SIP Request or Response would be mapped to a certain status so we would be able to monitor which call is in which state.
I still have a lot of work to do to think this all out, since it's still only an idea. I'm just wondering if anyone could give me some pointers into what to keep in mind when doing this.
Regards,
Grant
Hi,
I added in my local branch "$ct.inst" pseudo variable to retrieve instance.
Since instance could be an important attribute to make routing decisions,
having quick access to it in the message may be useful.
Anyone else need this functionality?
Krish Kura
hi guys,
hope u got time to help me.
Im first timer testing VoIP and SIP.
I created account to ur iptel.org site.
I downloaded "Jitsi"-software.
First when I opened it, I login with my username and password.
Then I go to "add new account", give same login username and password,
but Jitsi says that my password is wrong..wtf.
And
I installed Media5-Fone to my iPhone 4S.
When adding SIP-account it's says again that I got wrong password.
And YES, I didn't mistype it.
Thanks
- Kasper
Hi list,
I'm having some issues with dialog module. From time to time I get the
following error:
ERROR: dialog [dlg_req_within.c:231]: failed to update dialog lifetime
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea1c6840 tl->next=(nil) tl->prev=(nil)
[root@proxy ~]# cat /var/log/kamailio.log | grep "Jan 17" | grep "tl=" |
sort | uniq -c
1 Jan 17 13:27:00 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea09bf38 tl->next=(nil) tl->prev=(nil)
1 Jan 17 14:39:30 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea07c518 tl->next=(nil) tl->prev=(nil)
1 Jan 17 15:06:21 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea2da900 tl->next=(nil) tl->prev=(nil)
1 Jan 17 19:31:02 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea278cd0 tl->next=(nil) tl->prev=(nil)
1 Jan 17 19:31:42 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeee9f527a8 tl->next=(nil) tl->prev=(nil)
1 Jan 17 20:05:32 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea21fa30 tl->next=(nil) tl->prev=(nil)
This one was flooding my log file: tl=0x2aeeea1c6840
24322 Jan 17 21:53:02 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea1c6840 tl->next=(nil) tl->prev=(nil)
5709 Jan 17 21:53:23 proxy /usr/local/kamailio/sbin/kamailio[4100]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea1c6840 tl->next=(nil) tl->prev=(nil)
61314 Jan 17 21:53:23 proxy /usr/local/kamailio/sbin/kamailio[4102]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea1c6840 tl->next=(nil) tl->prev=(nil)
22812 Jan 17 21:54:01 proxy /usr/local/kamailio/sbin/kamailio[4102]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea1c6840 tl->next=(nil) tl->prev=(nil)
21137 Jan 17 21:54:02 proxy /usr/local/kamailio/sbin/kamailio[4102]:
CRITICAL: dialog [dlg_timer.c:205]: Trying to update a bogus dlg
tl=0x2aeeea1c6840 tl->next=(nil) tl->prev=(nil)
where pid 4100 is slow timer and pid 4102 is timer. Any idea why is this
happening and how to fix it.
(I suspect that may be some issues with our server memory...checking
now...and will inform). However wanted to raise this issue in case anyone
else is having the same.
Thanks, Rinor
