When manually assigning `$du`, the destination port pseudo-var `$dp` is set to 5060 unless explicitly overridden in the URI.
This should probably be inferred from the transport param, as it yields an incorrect value when transport=tls (which, unless explicitly overridden, should default to port 5061).
---
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/700
Many platforms with 4 byte integers define RAND_MAX as INT_MAX but some (Solaris and derivatives for example), RAND_MAX is only 32767 but INT_MAX is 2147483647. This change allows falling back to the posix random() and srandom() variants with casts to int if both int and long are 4 bytes, then defining a consistent KAM_RAND_MAX of 2147483647. If both INT_MAX and RAND_MAX are 2 bytes, then we are stuck with ANSI rand().
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/701
-- Commit Summary --
* core: add portable rand() macros
* ims_charging: update to use kam_rand()
* auth: update to use kam_rand()
* carrierroute: update to use kam_rand()
* cdp: update to use kam_rand()
* cfgutils: update to use kam_rand()
* dialog: update to use kam_rand()
* dispatcher: update to use kam_rand()
* drouting: update to use kam_rand()
* ims_auth: update to use kam_rand()
* ims_dialog: update to use kam_rand()
* ims_registrar_scscf: update to use kam_rand()
* iptrtpproxy: update to use kam_rand()
* lcr: update to use kam_rand()
* nat_traversal: update to use kam_rand()
* nsq: update to use kam_rand()
* pipelimit: update to use kam_rand()
* presence: update to use kam_rand()
* registrar: update to use kam_rand()
* rls: update to use kam_rand()
* sipcapture: update to use kam_rand()
* tm: update to use kam_rand()
* tsilo: update to use kam_rand()
* usrloc: update to use kam_rand()
* xmpp: update to use kam_rand()
* xprint: update to use kam_rand()
* core: update to use kam_rand()
-- File Changes --
M main.c (9)
M modules/auth/auth_mod.c (5)
M modules/carrierroute/cr_func.c (3)
M modules/carrierroute/prime_hash.c (4)
M modules/cdp/peermanager.c (6)
M modules/cdp/session.c (4)
M modules/cdp/utils.h (1)
M modules/cfgutils/cfgutils.c (5)
M modules/dialog/dlg_hash.c (3)
M modules/dispatcher/dispatch.c (6)
M modules/dispatcher/dispatch.h (1)
M modules/dispatcher/dispatcher.c (2)
M modules/drouting/drouting.c (11)
M modules/ims_auth/authorize.c (5)
M modules/ims_charging/ro_session_hash.c (2)
M modules/ims_charging/ro_session_hash.h (1)
M modules/ims_dialog/dlg_hash.c (3)
M modules/ims_registrar_scscf/reg_mod.h (1)
M modules/ims_registrar_scscf/registrar_notify.c (2)
M modules/ims_registrar_scscf/save.c (2)
M modules/ims_registrar_scscf/sip_msg.c (2)
M modules/iptrtpproxy/iptrtpproxy.c (3)
M modules/lcr/lcr_mod.c (3)
M modules/nat_traversal/nat_traversal.c (9)
M modules/nsq/reader.c (5)
M modules/pipelimit/pipelimit.c (3)
M modules/presence/presence.c (3)
M modules/registrar/sip_msg.c (3)
M modules/rls/notify.c (5)
M modules/sipcapture/sipcapture.c (5)
M modules/tm/callid.c (7)
M modules/tm/h_table.c (5)
M modules/tm/uac.c (3)
M modules/tsilo/ts_hash.c (3)
M modules/usrloc/ul_mi.c (3)
M modules/xmpp/util.c (4)
M modules/xprint/xp_lib.c (5)
M msg_translator.c (3)
M pt.c (13)
A rand/kam_rand.h (35)
M select_core.c (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/701.patchhttps://github.com/kamailio/kamailio/pull/701.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/701
The new module contains the http_client and http_async_client module.
A few difficulties with this change:
1. Modules are right now grouped by lib dependencies. This caused the http_client module to end up in the kamailio-utils-modules package. No one would ever search for it there.
2. I tried to package a kamailio-http_async-modules package, but this isn't a valid Debian package name. But when renaming it into kamailio-http-modules, it felt wrong to include just the async http client and leave the http_client module stuck in the utils package, where no one would look for it. So I moved the http_client package, too.
3. The package depends on libevent, which is actually just a dependency of http_async_client. http_client would compile without. I don't know whether this breaks any policies.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/699
-- Commit Summary --
* Packaging: Add new http package for Debian
-- File Changes --
M Makefile.groups (8)
M pkg/kamailio/deb/debian/control (16)
M pkg/kamailio/deb/debian/rules (2)
M pkg/kamailio/deb/jessie/control (16)
M pkg/kamailio/deb/jessie/rules (2)
M pkg/kamailio/deb/precise/control (16)
M pkg/kamailio/deb/precise/rules (2)
M pkg/kamailio/deb/sid/control (16)
M pkg/kamailio/deb/sid/rules (2)
M pkg/kamailio/deb/squeeze/control (16)
M pkg/kamailio/deb/squeeze/rules (2)
M pkg/kamailio/deb/stretch/control (16)
M pkg/kamailio/deb/stretch/rules (2)
M pkg/kamailio/deb/trusty/control (16)
M pkg/kamailio/deb/trusty/rules (2)
M pkg/kamailio/deb/wheezy/control (16)
M pkg/kamailio/deb/wheezy/rules (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/699.patchhttps://github.com/kamailio/kamailio/pull/699.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/699
I have a situation that I can't get my head around. Every so often I have a SCA seized and I need to manually release it. Here is the log of the sca and bye from the event logs.
messages-20150920:Sep 18 14:35:28 sip-registrar /usr/sbin/kamailio[7608]: ERROR: sca [sca_call_info.c:1580]: sca_call_info_bye_handler(): sca_call_info_bye_handler: sip:Mindfield@kamailio.newgarllc.com dialog leg 96b9ad37-9a7fa462-15c35d3(a)192.168.1.117;1c389191866 is not active
messages-20150920:Sep 18 14:35:28 sip-registrar /usr/sbin/kamailio[7610]: NOTICE: acc [acc.c:317]: acc_log_request(): ACC: transaction answered: timestamp=1442601328;method=BYE;from_tag=76C3EC1F-114D759A;to_tag=1c389191866;call_id=96b9ad37-9a7fa462-15c35d3(a)192.168.1.117;code=200;reason=OK;src_user=Mindfield;src_domain=kamailio.newgarllc.com;src_ip=192.168.1.40;dst_ouser=Mindfield;dst_user=Mindfield;dst_domain=192.168.1.117
And the kamcmd showing the seize line (in this case both are seized)
sip:Mindfield@kamailio.newgarllc.com 1 active 1442601278 sip:Mindfield@192.168.1.117 sip:1030@192.168.1.40:5060 96b9ad37-9a7fa462-15c35d3(a)192.168.1.117 76C3EC1F-114D759A 1c389191866
I am running Kamailio 4.2.6. The phones are Polycom VVX 310/410 running 5.3.1. And the PSTN gateway is an Audiocodes Mediant 1000 running 6.60A.292.001.
The call volume is light so I don't think there is a lot of traffic but there is about 16 phones one SCA. It is not happening all time. Could be a couple days that nothing happens and then there could be a couple days that it happens multiple times a day. I can't find a common element that would be causing this unless the 'bye' is closing the call before the SCA has a chance to do something with it.
Thanks
Kev
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/341