Ricardo Martinez writes:
> Can someone please explain to me hoy can i use the command “defunct_gw()” is
> used to mark a gw down?.
as the README tells, the function defuncts the gateway of previous
next_gw() call.
> I understand that the gateway is marked down for period of time with the
> comma
For what it's worth, make sure you have the mhomed patch in forward.c. As I
recall, the 3.1.2 source
tarball did not contain the fix, but the latest forward.c did.
http://www.mail-archive.com/sr-users@lists.sip-router.org/msg03892.html
Sean O'Donnell
Senior Engineer
uReach Technologies, Inc.
Hello.
Can someone please explain to me hoy can i use the command “defunct_gw()” is
used to mark a gw down?.
I understand that the gateway is marked down for period of time with the
command, but how can I check if a gateway is down?. Can someone show me
this with an example in the configuration?
Hi Timo,
Maybe I wasn't clear but access dialog data in the script it's not the issue
right now. My goal at this moment is to add a variable from the script into
the dialog _and_ make this information available from 'dlg_list_ctx' fifo
command.
I am justing parsing the output of 'dlg_list_ctx' an
Hey,
On 30.03.2011 17:55, Alexandre Abreu wrote:
> Using K 3.1.2. Before the setflag() that creates the dialog, I tried to use:
>
>
> $dlg_ctx(flags) = 1;
>
>
>
> Mar 30 12:29:03 devel kamailio: ERROR: dialog [dlg_var.c:165]: unknown
> PV name flags
I think the problem is that when using
Hello.
Using K 3.1.2. Before the setflag() that creates the dialog, I tried to use:
$dlg_ctx(flags) = 1;
Mar 30 12:29:03 devel kamailio: ERROR: dialog [dlg_var.c:165]: unknown PV
name flags
Mar 30 12:29:03 devel kamailio: ERROR: [pvapi.c:565]: pvar "dlg_ctx"
has an invalid name param
Hello,
it is almost 2 months since we packaged 3.1.2, there are commits
accumulated in branch 3.1, therefore I plan to package 3.1.3 Monday or
Tuesday next week. If anyone has something to add in this regards,
please reply.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
Hello,
On 3/30/11 3:01 PM, Klaus Feichtinger wrote:
Hello list,
I have a special situation in which string characters of the "root-line"
of the notify-body are overwritten by Kamailio. In detail: the root-line
of the NOTIFY message sent to the subscriber looks like:
instead of
In other word
Hi Henning
thanks.
min
On 03/30/2011 08:00 AM, Henning Westerholt wrote:
On Monday 28 March 2011, Min Wang wrote:
I have a bond interface (eth0_eth1), where -d any means any
interface, so I guess the ngrep will capture the traffic both from the
eth0 and bond0.
Hi Min,
yes, i
All,
Thanks for the tips and suggestions, I have now managed to get this
working using mhomed=1 and setting $fs, for some reason I could not get
"force_send_socket" to work with avp's (but thats a topic for another
thread).
Thanks again for your time.
___
Am 30.03.2011 15:01, schrieb Klaus Feichtinger:
> Can anybody comment this problem? Is this a bug of the
> presence_dialoginfo- or another module?
>
IIRC, the problem was reported before. I reviewed the code where the
aggregation happens several times but could not find a bug in the code.
So, w
Hello list,
I have a special situation in which string characters of the "root-line"
of the notify-body are overwritten by Kamailio. In detail: the root-line
of the NOTIFY message sent to the subscriber looks like:
instead of
In other words: the string
state="full" is overwritten by space charac
Thank you, that was the solution.
However, both from GTS telecom and from RDS networks asipto is not
reacheable.
I do not know which is your policy towards this, but maybe a cooldown
time should be advisable.
Maybe your firewall is just too strict.
For me, the webproxy solution works.
Others may
On Monday 28 March 2011, Min Wang wrote:
> I have a bond interface (eth0_eth1), where -d any means any
> interface, so I guess the ngrep will capture the traffic both from the
> eth0 and bond0.
Hi Min,
yes, it will capture from all (bonding) interfaces if you not specify only
one.
Cheers,
14 matches
Mail list logo
