Hello,
on September 3, 2001, the first line of code was committed to SIP
Express Router (SER) project, since 2008 turning into Kamailio project.
>From pioneering large scale deployments of using SIP for Voice over IP
in early 2000s, the project impacted the evolution of real time
communications, disrupted the telecom vendors with its open source model
and enabled many businesses to grow and innovate.
Let's get together to a VUC session later this week, on Friday, Sep2,
2016, to share the good or bad stories while using SER or Kamailio
during the past 15 years. If it made your life easy or a nightmare, it's
time to tell it. If you have a funny photo or video, no matter is old or
recent, join us and show it.
More details about VUC and how one can join or watch the session are
available at:
- https://vuc.me
If you want to actively participate during the session, email me shortly
to coordinate a bit. If you cannot participate but you have something
interesting to share (story, media files, etc...) email me as well and I
will present it.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.orghttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
We've installed latest kamailio from master branch and we see an issue with CSeq numbers.
Scenario is as follow:
A <-> Kamailio <-> B
We do use uacreg to register to B from kamailio. If there is an call from A to B via Kamailio, B challenge DA and from that point the CSeq is not equal on both sides. We do use dlg_manage to track the Difference.
While establishing the call it works until the ACK as reply to 200 OK. The ACK is the first message the CSeq is not updated anymore. In X_log I can see the $dlg_var(cseq_diff) is still there and gives the correct difference. It seems it is not used anymore.
All following requests / responses do have this issue e.G. Bye.
I can provide a wireshark trace, Logs and I can reproduce it in our test lab. Let me know if you need anything.
We do use the latest master version because we had this issue:
https://github.com/kamailio/kamailio/issues/679
unfortunately we were not able to find any commit in 4.4 branch, so we tried master. (would be fine for us, if we would get it run)
cheers
Jöran
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/752
Reported by oej GH #580. Includes whitespace cleanup and normalizing.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/762
-- Commit Summary --
* Merge remote-tracking branch 'refs/remotes/kamailio/master'
* sca: terminate all error and debug messages with a new line
-- File Changes --
M modules/sca/sca.c (554)
M modules/sca/sca.h (36)
M modules/sca/sca_appearance.c (2239)
M modules/sca/sca_appearance.h (188)
M modules/sca/sca_call_info.c (3557)
M modules/sca/sca_call_info.h (42)
M modules/sca/sca_common.h (13)
M modules/sca/sca_db.c (251)
M modules/sca/sca_db.h (71)
M modules/sca/sca_dialog.c (151)
M modules/sca/sca_dialog.h (22)
M modules/sca/sca_event.c (73)
M modules/sca/sca_event.h (16)
M modules/sca/sca_hash.c (451)
M modules/sca/sca_hash.h (78)
M modules/sca/sca_notify.c (597)
M modules/sca/sca_notify.h (6)
M modules/sca/sca_reply.c (54)
M modules/sca/sca_reply.h (2)
M modules/sca/sca_rpc.c (820)
M modules/sca/sca_rpc.h (44)
M modules/sca/sca_subscribe.c (2668)
M modules/sca/sca_subscribe.h (71)
M modules/sca/sca_util.c (718)
M modules/sca/sca_util.h (32)
M utils/kamctl/mysql/ims_dialog-create.sql (104)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/762.patchhttps://github.com/kamailio/kamailio/pull/762.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/762
While using httpa_sync_client, I'm trying to retrieve the Content-Type of the body I got in a 200OK after an HTTP get using $var(my_content_type) =$ http_hdr(Content-Type);
Then When I launch Kamailio, I get a seg fault at the configuration file validation step because in http_async_client_mod.c the line 'return pv_api.parse_hdr_name(sp, in)' is trying to use parse_hdr_name before it being initialized.
I noticed that when I remove my previous line, the initialization is done but after the configuration file validation.
Any idea if I'm doing something wrong?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/760
Hi guys,I observed a crash in Kamailio IMS P-CSCF when there is an incoming
REGISTER.This is Kamailio 4.4.2 installed on Debian 8.3 Jessie on X86_64.
Below is the backtrace:Program terminated with signal SIGSEGV, Segmentation
fault.#0 0x00007fc9bfa9b143 in unlink_unsafe_dlg (d_entry=0x7fc9b6cd7a10,
dlg=0x7fc9c1371c90) at dlg_hash.h:208208 dlg->next->prev =
dlg->prev;(gdb) bt#0 0x00007fc9bfa9b143 in unlink_unsafe_dlg
(d_entry=0x7fc9b6cd7a10, dlg=0x7fc9c1371c90) at dlg_hash.h:208#1
0x00007fc9bfaabc1c in unref_dlg (dlg=0x7fc9c1371c90, cnt=1) at
dlg_hash.c:1056#2 0x00007fc9bfab3f00 in dlg_release (dlg=0x7fc9c1371c90) at
dlg_hash.c:1816#3 0x00007fc9baa81aa0 in NAT_Keepalive (msg=0x7fc9c1371c90)
at nat_traversal.c:1406#4 0x0000000000573fc1 in do_action
(h=0x7ffe69938980, a=0x7fc9c13008e0, msg=0x7fc9c1371c90) at action.c:1054#5
0x00000000005806a6 in run_actions (h=0x7ffe69938980, a=0x7fc9c13003c8,
msg=0x7fc9c1371c90) at action.c:1549#6 0x0000000000573f30 in do_action
(h=0x7ffe69938980, a=0x7fc9c1300a10, msg=0x7fc9c1371c90) at action.c:1045#7
0x00000000005806a6 in run_actions (h=0x7ffe69938980, a=0x7fc9c12ff6d0,
msg=0x7fc9c1371c90) at action.c:1549#8 0x0000000000573f30 in do_action
(h=0x7ffe69938980, a=0x7fc9c1300b40, msg=0x7fc9c1371c90) at action.c:1045#9
0x00000000005806a6 in run_actions (h=0x7ffe69938980, a=0x7fc9c12fdca8,
msg=0x7fc9c1371c90) at action.c:1549#10 0x0000000000570ae3 in do_action
(h=0x7ffe69938980, a=0x7fc9c12d6958, msg=0x7fc9c1371c90) at action.c:678#11
0x00000000005806a6 in run_actions (h=0x7ffe69938980, a=0x7fc9c12d64a0,
msg=0x7fc9c1371c90) at action.c:1549#12 0x0000000000580df3 in run_top_route
(a=0x7fc9c12d64a0, msg=0x7fc9c1371c90, c=0x0) at action.c:1635#13
0x0000000000588fe9 in receive_msg ( buf=0xa0efc0 "REGISTER
sip:domain.com:5432 SIP/2.0\r\nTo: bob<sip:bob@domain.com>\r\nFrom:
bob<sip:bob@domain.com>;tag=0e0eaf0d\r\nVia: SIP/2.0/UDP
1.2.3.4:9764;branch=z9hG4bK-d87543-56117650-1--d87543-;rpor"..., len=469,
rcv_info=0x7ffe69938c60) at receive.c:240#14 0x00000000004718f8 in
udp_rcv_loop () at udp_server.c:495#15 0x00000000004f4f76 in main_loop () at
main.c:1600#16 0x00000000004fc4ac in main (argc=3, argv=0x7ffe69939148) at
main.c:2616Let me know if any more details are required.Regards,Owais
--
View this message in context: http://sip-router.1086192.n5.nabble.com/Kamailio-4-4-2-Crashed-on-receiving…
Sent from the Development mailing list archive at Nabble.com.