On 8/5/11 5:17 PM, Alex Hermann wrote:
On Thursday 04 August 2011, Daniel-Constantin Mierla wrote:
I committed a patch to master branch in order to skip setting the
dst_uri to next hop address for branch route, link to commit:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h
On Thursday 04 August 2011, Daniel-Constantin Mierla wrote:
> I committed a patch to master branch in order to skip setting the
> dst_uri to next hop address for branch route, link to commit:
> http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fb4ecbf
> 986f4af366e5be9cbad26ceba92
Hello,
I committed a patch to master branch in order to skip setting the
dst_uri to next hop address for branch route, link to commit:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fb4ecbf986f4af366e5be9cbad26ceba924c77fd
It would be great if you can give it a try and let
On 8/1/11 7:23 PM, Alex Hermann wrote:
On Monday 01 August 2011 19:00:36 Daniel-Constantin Mierla wrote:
while trying to upgrade from 1.5 to 3.1 i noticed that between t_relay()
and branch_route, $du gets automatically set to $ru if it has not been
set before.
have you spotted the code that d
On Monday 01 August 2011 19:00:36 Daniel-Constantin Mierla wrote:
> > while trying to upgrade from 1.5 to 3.1 i noticed that between t_relay()
> > and branch_route, $du gets automatically set to $ru if it has not been
> > set before.
>
> have you spotted the code that does it? It should not happen
On Monday 01 August 2011 17:58:17 Alex Balashov wrote:
> On 08/01/2011 11:57 AM, Alex Hermann wrote:
> > Is it even guaranteed that $du gets set to $ru in every possible
> > scenario?
>
> No, it is set only in a few cases.
>
> Good way to check:
>
> if(!defined $du)
That does not work:
The
Hello,
On 8/1/11 5:57 PM, Alex Hermann wrote:
Hello,
while trying to upgrade from 1.5 to 3.1 i noticed that between t_relay() and
branch_route, $du gets automatically set to $ru if it has not been set before.
have you spotted the code that does it? It should not happen like that,
I see no r
On 08/01/2011 11:57 AM, Alex Hermann wrote:
Is it even guaranteed that $du gets set to $ru in every possible
scenario?
No, it is set only in a few cases.
Good way to check:
if(!defined $du)
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 3
Hello,
while trying to upgrade from 1.5 to 3.1 i noticed that between t_relay() and
branch_route, $du gets automatically set to $ru if it has not been set before.
This is a change from 1.5 i could not find documentation for, so it might have
been unintened.
Can someone enlighten me on the p
