Hello,
I've needed to reboot www.kamailio.org two times for maintenance (kernel and grub boot loader update) a few minutes ago. The machine which its services is now up again, please let me know if you find some issues because of the change.
Thanks and regards,
Henning
--
Henning Westerholt - Head of IT Operations Internet Access & Communications
Tel. +49 721 91374-4483, Fax. +49 721 91374-2734
1&1 Internet AG, Brauerstraße 48, 76135 Karlsruhe, Germany
Vorstände: Henning Ahlert, Ralph Dommermuth, Robert Hoffmann, Andreas Hofmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen, Martin Witt, Christian Würst. Aufsichtsratsvorsitzender: Michael Scheeren. Amtsgericht Montabaur / HRB 6484
Hello,
The BYE, generated by Kamailio in case of dialog timeout, is malformed:
BYE <sip:anonymous@192.168.225.2:50601> sip:anonymous@192.168.225.2:50601
SIP/2.0
Via: SIP/2.0/UDP 172.16.60.113;branch=z9hG4bK77b6.941684b6.0
Via: SIP/2.0/UDP
10.1.1.10;branch=z9hG4bKsr-JfymiMenCtp4urS5CXSnCHJnCXJZiHvRCHYJb6ggNPN9NVDL3
-TWhdW0UvOfN1KPTReRiHy1CHmcs6mZiHS*
To: <sip:anonymous;cpc=ordinary@192.168.225.2;tag=01e3a8c0-c1c2-t-1>
sip:anonymous;cpc=ordinary@192.168.225.2;tag=01e3a8c0-c1c2-t-1
From:
<sip:1255010006@192.168.225.2:5060;user=phone;tag=813142547-1366730270587>
sip:1255010006@192.168.225.2:5060;user=phone;tag=813142547-1366730270587
CSeq: 465332801 BYE
Call-ID: <mailto:1aebb42c-01e3a8c0-000007c2@192.168.225.2>
1aebb42c-01e3a8c0-000007c2(a)192.168.225.2
Content-Length: 0
User-Agent: kamailio (3.3.2 (x86_64/linux))
Max-Forwards: 69
The bad syntax is located in the "To" header field.
According to the RFC 3261 section 25.1, the grammar of the To header field
is as follow:
To = ( "To" / "t" ) HCOLON ( name-addr
/ addr-spec ) *( SEMI to-param )
name-addr = [ display-name ] LAQUOT addr-spec RAQUOT
addr-spec = SIP-URI / SIPS-URI / absoluteURI
to-param = tag-param / generic-param
The RFC 3261 section 20.10 explains that:
Even if the "display-name" is empty, the "name-addr" form MUST be
used if the "addr-spec" contains a comma, semicolon, or question
mark. There may or may not be LWS between the display-name and the
"<".
As the "addr-spec" <sip:anonymous;cpc=ordinary@192.168.225.2>
sip:anonymous;cpc=ordinary@192.168.225.2 contains a semicolon, it means that
the "name-addr" form must be used. The "To" header field should be encoded
as follow:
To: < <sip:anonymous;cpc=ordinary@192.168.225.2>
sip:anonymous;cpc=ordinary@192.168.225.2>;tag=01e3a8c0-c1c2-t-1
BR,
Julia
Hi,
can anyone tell me if it is possible to save the time and date using accdb
(mysql) with milisec as well? the field on the DB is set as TIMESTAMP.
BR,
Uri
Thanks Carsten.
We have also started some other docs with Richard and Olle. Olle have you
managed to publish the doc Rich and I shared with you - at least this is a
nice overview of the modules, etc? I know there are still some module docs
outstanding from me which I will get to ASAP - apologies for that!
Cheers
Jason
On Tue, Apr 23, 2013 at 11:40 AM, Pavel Segeč <Pavel.Segec(a)fri.uniza.sk>wrote:
> Thank you Carsten very much****
>
> ** **
>
> Palo73****
>
> ** **
>
> *From:* sr-users-bounces(a)lists.sip-router.org [mailto:
> sr-users-bounces(a)lists.sip-router.org] *On Behalf Of *Carsten Bock
> *Sent:* Tuesday, April 23, 2013 10:08 AM
> *To:* Kamailio (SER) - Users Mailing List
> *Cc:* andreea.ancuta.corici(a)fokus.fraunhofer.de; Dragos Vingarzan
> *Subject:* Re: [SR-Users] Kamailio 4.0 IMS****
>
> ** **
>
> Hi,****
>
> i was approached by several people after Kamailio World 2013, that our
> installation guide is not available anymore.****
>
> The "old" version was at some point quite outdated, that is the reason why
> i disabled the page. However, due to the great demand i will update the IMS
> on Kamailio how-to later this week and publish the updated version (and i
> will move it to the Kamailio Wiki so other points can be easily added by
> different people).****
>
> IMS rocks!****
>
> ** **
>
> Kind regards,
> Carsten****
>
> ** **
>
> ** **
>
> 2013/4/23 Pavel Segeč <pavel.segec(a)fri.uniza.sk>****
>
> Sir,
>
> Thank you for your answer. Aggree all you wrote and I'm aware of that.
> Just I'm saying helps us..we use, popularize and love Kamailio project
> however we need some help ...that's all... Kamilio 4.0 IMS is a quite new
> thing and we are starting to use it during official student classes and
> labs, we are gaining experiences and we share them,we reports bugs and so
> on, we do not hide our knowledge
>
> palo73****
>
>
>
>
>
>
>
>
> _______________________________________________
> 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****
>
>
>
>
> -- ****
>
> Carsten Bock
> CEO (Geschäftsführer)
>
> ng-voice GmbH
> Schomburgstr. 80
> D-22767 Hamburg / Germany
>
> http://www.ng-voice.com
> mailto:carsten@ng-voice.com
>
> Office +49 40 34927219
> Fax +49 40 34927220
>
> Sitz der Gesellschaft: Hamburg
> Registergericht: Amtsgericht Hamburg, HRB 120189
> Geschäftsführer: Carsten Bock
> Ust-ID: DE279344284
>
> Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
> http://www.ng-voice.com/imprint/****
>
> ** **
>
> __________ Informacia od ESET NOD32 Antivirus, verzia databazy 8255
> (20130422) __________****
>
> ** **
>
> Tuto spravu preveril ESET NOD32 Antivirus.****
>
> ** **
>
> http://www.eset.sk****
>
>
> __________ Informacia od ESET NOD32 Antivirus, verzia databazy 8255
> (20130422) __________
>
> 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
>
>
--
Jason Penton
Senior Manager: Applications and Services
Smile Communications
Johannesburg, South Africa
Phone: +27 83 283 7000
This email is subject to the disclaimer of Smile Communications at http://www.smilecoms.com/disclaimer
Hi,
I'd like to put a topic up for discussion to test kamailio config logics.
The standard way of doing so is to start kamailio as usual and write
sipp or sipsak scenarios to perform automated tests. This can get quite
complex pretty quickly, as you always have to take care of covering the
full transaction on the client side, where in most of the cases you
really just want to know which IP/port kamailio would send the message
to, and how some headers look like after processing. Also, it doesn't
really allow to inspect your variables and avps etc. on the fly other
than logging them to syslog and parsing it from there.
Let me know if this is stupid and/or a complete overkill, but what about
introducing some kind of dummy mode, where you'd pipe a message into
kamailio via stdin, and get the resulting message out on stdout (e.g. in
ngrep style with ip information as first line, plus the content
following), plus a dump of internals (e.g. vars, avps) on stderr as
they're being assigned, and once the message is processed, kamailio
would just shut down again?
There are quite some things to consider, like not doing any timer
handling in tm, but would this be something anyone would be interesting
to discuss in more detail?
If I'm completely on a wrong track, what are suggested alternatives to
testing full sip call flows other than running automated UAs against
kamailio?
Andreas
Hi,
Once in a while it captures outbound SIP Invite but it captures always 100
trying, 180 and 200 OK and some times it captures inbound SIP INVITE as
well.
Thanks
Ram
i have in config:
setbflag(8);
xlog("L_INFO", "bflags are <$bf/$bF>\n");
save("location", "0x02");
and i correctly get to syslog:
Apr 10 19:51:48 wheezy1 /usr/sbin/sip-proxy[6722]: INFO: bflags are <256/00000100>
however, when i look what gets stores in location table, cflags column
of the contact has value 384. it is also shown by ul_dump:
Cflag:: 384
384 = 256 + 128. i must be missing something trivial. how is it
possible that also flag 7 (which is my nat_bflag) gets set in usrloc?
-- juha
Hi,
I'm totally new to Kamailio and I attempt to add Kamailio functionality to
an already working Asterisk implementation.
I have been following this link:
http://kb.asipto.com/asterisk:realtime:kamailio-3.3.x-asterisk-10.7.0-astdb
Everything seems to work with an exception of encountering NAT issues. The
location table in Kamailio reports the local NAT address, instead of the
public address, where then Asterisk reports UNREACHABLE status.
I have installed and started RTPproxy as adviced in the above link - no
changes.
Best regards,
Henning Bragge
Hi all Kamailio IMS community,
after a time, we are starting to use Kamailio 4.0 based IMS platform
during our university lessons (before we used Kamailio 3.2 based).
However I'm missing some usefull links, docs, tutorials regarding of
Kamailio 4.0 IMS procesess. The situation was quite poor alerady
before for 3.2 but some was available on ng-voice web page, at least,
now nothing (especially about new ng-voice HSS). Does anybody know and
help us with some usefull information about the Kamailio IMS 4.0 and
HSS? I promise to prepare and make publicly available guides on our
site nil.uniza.sk (Kamailio award for 2010)
Thanks again
palo73
Hi,
I think there is a bug with the BYE that is sent to the caller and callee
when dialog timeout happends.
The BYE headers are sent with no "<" or ">".
So, some sip singaling points decline the BYE.
BR,
Uri