Ok, in Kamailio lingo - you want a configurable number of in-dialog
transactions to fail before terminating the dialog, not just one. Just as a
note, RFC-compliance says "one failed in-dialog transaction" causes dialog to
fail. I think adding a config option for this - if possible - makes sense.
I use it over UDP and the SIP transaction setup does the job perfectly. The
problem is when you use it over mobile networks and do network switching (eg.
from WiFi to LTE) and at that instance when an OPTIONS message goes out; it
goes out to the WiFi IP Address from where the request is bound to
Updated the title to indicate what needs to be changed in Kamailio.
---
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/531#issuecomment-204268174__
Hmm. I am thinking that the dialog module doesn't update the counters after
reloading dialogs from database at startup. Don't think this is really a SNMP
issue - the counter is managed by the dialog module.
---
You are receiving this because you are subscribed to this thread.
Reply to this email
Are you using TCP or UDP? Are you sure we only send ONE request? It's one
transaction, but normally over UDP we retransmit a number of times before
giving up - it's part of the transaction setup in SIP.
---
You are receiving this because you are subscribed to this thread.
Reply to this email dir
Ok. I think you misunderstand how TLS works. Every server is required to have a
certificate. If Zoiper doesn't have a certificate we can not set up a TLS
connection to the client. This is why we implemented SIP Outbound, which allows
the client to set up a TLS connection and keep it open, and al
Closed #551.
---
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/551#event-610831722___
sr-dev mailing list
sr-dev@lists.sip-router.org
http:
I have some Zoiper/Android clients which use TLS, but don't (yet) have the
ability to specify the certificate that is used and don't seem to send a
certificate when receiving a call. When Kamailio routes a call to one of these
devices that register with dynamic addresses, Kamailio (acting as a
The connection timeout was hardcoded to 1 sec. This can now be set from cfg
file.
If the redis server became unresponsive kamailio would wait for the standard
Linux TCP timeout for an answer (very long time).
This patch has added an timeout value for redis commands.
The default timeout is 1 se
Closed #556.
---
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/556#event-610163751___
sr-dev mailing list
sr-dev@lists.sip-router.org
http:
We had two checkouts saying otherwise, but now mine says the same as yours.
Arrrggghh.
---
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/556#issuecomment-204045937___
Hello,
Would it be possible to add in the next release/development version a
new transformation type "ip" for manipulating IP addresses ?
The inet_ntop and inet_pton transformations would be particularly useful
when it is needed to send/receive IP addresses in binary format (e.g.
RADIUS AVPs w
This is from branch 4.4:
```
CREATE TABLE `trusted` (
`id` INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL,
`src_ip` VARCHAR(50) NOT NULL,
`proto` VARCHAR(4) NOT NULL,
`from_pattern` VARCHAR(64) DEFAULT NULL,
`ruri_pattern` VARCHAR(64) DEFAULT NULL,
`tag`
Well, the module requires a database structure that we haven't got in
/utils/kamctl :-)
---
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/556#issuecomment-203905550__
I see it also in branch 4.4, if you refer to sql creating scripts from
kamctl/kamdbct. That change was before branching 4.4, iirc.
---
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/
I guess we need to cherry-pick commit 6b76de9f7d991ed3fdc5f2f28dde7bcb1962108b
to 4.4
---
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/556#issuecomment-203902930
The database schemas has version 5, the module requires version 6. It seems
like the schemas in master is up-to-date
---
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/556
Module: kamailio
Branch: master
Commit: 6643604b1406af7be704b4f669fc238fe3d89418
URL:
https://github.com/kamailio/kamailio/commit/6643604b1406af7be704b4f669fc238fe3d89418
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2016-03-31T12:07:24+02:00
README.md: coherent ti
18 matches
Mail list logo
