In the two proxys? What would the value q be? as permanent contacts is with
an expiring date in 2080 for example no?
2016-09-28 17:58 GMT+02:00 Juha Heinanen :
> Igor Potjevlesch writes:
>
> > I have a proxy that manage fix calls and a proxy that manage mobile
> calls.
> > I want to implement cal
Hello Daniel,
The second option worked:
- relay first to the fixed proxy, which will bounce back to mobile proxy
the branch for mobile device
But now if I want to be able to choose which phone (mobile or fixe) rings
before I have tried by doing the "async_route("RELAY", "7");" in the fixe
proxy
Hello,
Thank you very much Daniel, I think that the second option is the most
simple one, i am going to try it.
Thanks!
Igor.
2016-08-19 9:24 GMT+02:00 Daniel-Constantin Mierla :
> Hello,
>
> try one of the variants:
>
> - relay to the fixed proxy, add a new branch and then suspend
>
> - r
Hello,
try one of the variants:
- relay to the fixed proxy, add a new branch and then suspend
- relay first to the fixed proxy, which will bounce back to mobile
proxy the branch for mobile device
- relay to fixed proxy and mobile proxy at the same time. When coming
from itself, mobile pro
Hello,
On 11/27/12 9:52 PM, Moacir Ferreira wrote:
All the topics/examples I found on the net is not what I am looking
for, so here is the question: How do I achieve parallel forking (call
all devices) if I have a single user registered using the same account
from different devices (i.e.: tabl
On 19.09.2012 16:13, Yufei Tao wrote:
I should have made it clearer: $du is null both before and after lookup
location in LOCATION_BRANCH when no fix_nated_register was done (thus
'received' column in location table was null). When fix_nated_register
was done, $du for each branch was null befor
l
be set), or 2. set $du after lookup if it is empty Wonder if it is worth
adding fixes in the source code. Thanks very much Klaus for pointing me
to the right direction! Yufei Date: Wed, 19 Sep 2012 15:13:29 +0100
From: Yufei Tao Subject: Re: [SR-Users] call
forking using dbaliases not worki
I should have made it clearer: $du is null both before and after lookup
location in LOCATION_BRANCH when no fix_nated_register was done (thus
'received' column in location table was null). When fix_nated_register
was done, $du for each branch was null before lookup location, but set
to 'received' a
On 19.09.2012 12:24, Yufei Tao wrote:
Hi Klaus
Thanks for the reply!
I check the $du, it is always null before and after the lookup. Is it
only set when relaying to a proxy (from record-route), and not to a client?
That's strange. For NATed clients, $du must contain the 'received' URI.
Oth
Hi Klaus
Thanks for the reply!
I check the $du, it is always null before and after the lookup. Is it
only set when relaying to a proxy (from record-route), and not to a client?
When no fix_nated_register is called, the lookup location for both
clients y2 and y3 is successful from the log, when p
I suspect that the branch route is first executed for the NATed client.
Then the 'received' column is used as destination URI. When executing
the branch route again, the destination URI is still the value from the
previous branch, and lookup() will not overwrite is as 'received' is not
availabl
11 matches
Mail list logo
