I haven't looked at the code, but probably the function doesn't accept
variable for the matching regular expression.
If the IP/port of asterisk are not changed, you can try:
#!substdef /ASTERISKIP/127.0.0.1/
#!substdef /ASTERISKPORT/5080/
asterisk.bindip = ASTERISKIP ...
asterisk.bindport =
On 08/08/14 18:39, Paul Belanger wrote:
On Fri, Aug 8, 2014 at 2:21 AM, Daniel-Constantin Mierla
mico...@gmail.com wrote:
There is no db-only for dispatcher, you have to do reload.
If you don't need keepalive mechanism, perhaps you can try loading the
addresses from database with sqlops and
Hello,
yes, transformations are the way to parse/extract values from a
variable. If it is something more complex, then using an embedded
language such as Lua, Perl, Python ... can be a more convenient alternative.
Cheers,
Daniel
On 08/08/14 13:41, Jonathan Hunter wrote:
Hello Daniel,
Greetings all.
I have following use case:
0) Peer A and B registers on kamailio via TLS.
1) Peer A establishes call to peer B.
2) Peer A changes network and call has to be refreshed. Peer A reregisters,
gathers ICE candidates, builds reINVITE and sends it to B. After peer A
changes network again,
The SIP reply is routed based on the address in the VIA header. The
address in VIA is set by each node sending a request, if between the
request and the response the sender is no longer available at the
address it added as VIA, then it is little one can do for that.
You can try not sending
You can try not sending the 100 trying, so the sender does retransmissions
Sender did not receive 100 answer; anyway it did not retransmit. It is
based on resiprocate.
maybe the sender should send a new re-invite as it changes to a new
network again.
Is it legal in SIP? I ask because such attempt
On 11/08/14 15:18, Dmytro Bogovych wrote:
You can try not sending the 100 trying, so the sender does retransmissions
Sender did not receive 100 answer; anyway it did not retransmit. It is
based on resiprocate.
Ahh, right, for tls the reliability of transmission is given by
transport layer. So
I see no problem from sip point of view -- each party can send re-invites
as they have something new to negotiate.
Will try to patch resiprocate :)
Thanks for your help !
On Mon, Aug 11, 2014 at 4:47 PM, Daniel-Constantin Mierla mico...@gmail.com
wrote:
On 11/08/14 15:18, Dmytro Bogovych
Hello,
I want to announce that a new developer got GIT write access to
repository: Jorj Bauer from University of Pennsylvania, USA - he is
mainly joining the efforts to maintain and develop further the SCA module:
* http://kamailio.org/docs/modules/stable/modules/sca.html
His git commit
Hello,
Is there any way rtpengine can be configured to use same UDP port to
receive and transmit RTP packets?
The set up I'm trying is
SIP_Client -- Kamailio/rtpengine -- Freeswitch
InternetInternet LAN LAN 192.168.1.10
I tried *rtpengine_offer * in
El 11/08/14 02:30, Daniel-Constantin Mierla escribió:
I haven't looked at the code, but probably the function doesn't accept variable
for the matching regular expression.
If the IP/port of asterisk are not changed, you can try:
#!substdef /ASTERISKIP/127.0.0.1/
#!substdef /ASTERISKPORT/5080/
Hi,
On 08/11/2014 08:34 PM, Narsay, Deep wrote:
Is there any way rtpengine can be configured to use same UDP port to
receive and transmit RTP packets?
The set up I'm trying is
SIP_Client -- Kamailio/rtpengine -- Freeswitch
InternetInternet LAN LAN
Hello Andreas,
Yes, that's what I had thought, but
I am actually seeing it using two different UDP ports towards Freeswitch
(send=40036 and recv=40042)
and two more ports towards SIP Client (send=40038, and recv=40040).
I am wondering if there is any setting (or flag at compilation time) that
Hello I try to use kamctl dispatcher reload cmd but in gives me an error
kamctl dispatcher reload
ERROR: Error opening Kamailio's FIFO /tmp/kamailio_fifo
ERROR: Make sure you have the line 'modparam(mi_fifo, fifo_name,
/tmp/kamailio_fifo)' in your config
ERROR: and also have loaded the mi_fifo
As the error says, make sure you have
*modparam(mi_fifo, fifo_name, /tmp/kamailio_fifo)* in your
kamailio.cfg?
If yes, check if the FIFO is really present in /tmp. ( file
/tmp/kamailio_fifo ).
I believe adding FIFOPATH=/tmp/kamailio_fifo to kamctlrc is optional,
since it is the default path.
On Aug 11, 2014, at 5:04 PM, Narsay, Deep deep.nar...@mezocliq.com wrote:
Hello Andreas,
Yes, that's what I had thought, but
I am actually seeing it using two different UDP ports towards Freeswitch
(send=40036 and recv=40042)
and two more ports towards SIP Client (send=40038, and
*modparam(mi_fifo, fifo_name, /tmp/kamailio_fifo)* in your
kamailio.cfg -It exisits
But /tmp/kamailo_fifo not found
I created it by myself (for test) through mkfifo
Then kamctl dispatcher reload started but not exit from itself (not
reliease at input string at server)
2014-08-12 1:29
Greetings,
I'm running into a slow memory leak on my kamailio 4.0.4 SIP proxies. I'm
observing a steady increase in the memory consumption until there is no more
left. Kamailio then starts repeating this in the logs:
ERROR: dispatcher [dispatch.c:279]: add_dest2list(): no more memory.
What
18 matches
Mail list logo
