9 Mar
2013
9 Mar
'13
8:25 p.m.
nathelper readme on this flag tells:
What branch flag should be used by the module to disable
NAT pings on a per-registration basis. If the given flag
is set for a
particular registration, then no NAT pings will be sent at all,
regardless of any other conditions.
however, the name of the flag is sipping_disable_bflag, which indicates
that it would apply to nat ping via sip requests only.
which way it is? please either fix the name of the flag or readme
text.
-- juha
11 Mar
11 Mar
8:17 a.m.
New subject: git:jason.penton/ims_ro_interface: nathelper: add new option sipping_disable_bflag
Hey Juha,
did you mean to send this mail? I am confused! ;)
Cheers
Jason
On Sat, Mar 9, 2013 at 9:25 PM, Juha Heinanen <jh(a)tutpro.com> wrote:
nathelper readme on this flag tells:
What branch flag should be used by the module to disable
NAT pings on a per-registration basis. If the given flag
is set for a
particular registration, then no NAT pings will be sent at
all,
regardless of any other conditions.
however, the name of the flag is sipping_disable_bflag, which indicates
that it would apply to nat ping via sip requests only.
which way it is? please either fix the name of the flag or readme
text.
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
8:17 a.m.
New subject: git:jason.penton/ims_ro_interface: nathelper: add new option sipping_disable_bflag
Jason Penton writes:
did you mean to send this mail? I am confused! ;)
formatting may be obscure (sorry about that). i tried to say that the
name of the flag is sipping_disable_bflag, i.e., it refers to ping with
a sip method (like other sipping* vars), but based on the description in
readme, it claims to have nothing to do with pinging with sip method,
but nat ping in general.
please fix either the name of the var or description.
-- juha
8:34 a.m.
New subject: git:jason.penton/ims_ro_interface: nathelper: add new option sipping_disable_bflag
Hey Juha,
This is my branch I'm using to build Ro Interface for IMS. I am not
concerned about nathelper??? The only code that will move into master when
I am done is the ims_ro module......
Cheers
Jason
On Mon, Mar 11, 2013 at 9:17 AM, Juha Heinanen <jh(a)tutpro.com> wrote:
Jason Penton writes:
--
Jason Penton
Senior Manager: Applications and Services
Smile Communications
Johannesburg, South Africa
Phone: +27 83 283 7000
This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at
http://www.smilecoms.com/disclaimer
did you mean to send this mail? I am confused! ;)
formatting may be obscure (sorry about that). i tried to say that the
name of the flag is sipping_disable_bflag, i.e., it refers to ping with
a sip method (like other sipping* vars), but based on the description in
readme, it claims to have nothing to do with pinging with sip method,
but nat ping in general.
please fix either the name of the var or description.
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
8:28 a.m.
New subject: git:jason.penton/ims_ro_interface: nathelper: add new option sipping_disable_bflag
Jason Penton writes:
This is my branch I'm using to build Ro Interface
for IMS. I am not
concerned about nathelper??? The only code that will move into master when
I am done is the ims_ro module......
the commit was to nathelper module. fine with me if it does not ever
end up merged with master.
-- juha
8:46 a.m.
New subject: git:jason.penton/ims_ro_interface: nathelper: add new option sipping_disable_bflag
Ahh yes, Ok that was becuase I synced form master (looks like a change from
rfuchs). but again, this will only affect my branch.
FYI:
commit 6543308deaf3ac029ec7db06f7535883006b1f00
Author: Richard Fuchs <rfuchs(a)sipwise.com>
Date: Wed Feb 27 11:17:03 2013 -0500
nathelper: add new option sipping_disable_bflag
Cheers
Jason
On Mon, Mar 11, 2013 at 9:28 AM, Juha Heinanen <jh(a)tutpro.com> wrote:
Jason Penton writes:
--
Jason Penton
Senior Manager: Applications and Services
Smile Communications
Johannesburg, South Africa
Phone: +27 83 283 7000
This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at
http://www.smilecoms.com/disclaimer
This is my branch I'm using to build Ro
Interface for IMS. I am not
concerned about nathelper??? The only code that will move into master
when
I am done is the ims_ro module......
the commit was to nathelper module. fine with me if it does not ever
end up merged with master.
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
8:32 a.m.
New subject: git:jason.penton/ims_ro_interface: nathelper: add new option sipping_disable_bflag
i just checked and
4.8. sipping_disable_bflag (integer)
is in current master.
i don't know who put it there, but please either remove the var or fix
its name/description.
-- juha
4253
days inactive
4255
days old
6 comments
3 participants
participants (3)
-
Jason Penton -
Jason Penton -
Juha Heinanen