[VoiceOps] RE 3. ACMEs SIP Dynamic HNT (Ujjval Karihaloo)

Wed Feb 23 19:21:39 EST 2011

We use Dynamic HNT.  Feature works good and I have not seen an issue regarding this specific feature.  Other firewall issues can cause this feature to be null because the firewall manipulates the sip messaging.

All of our sip clients honor our sip expires timer hence we have no issues.

-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of voiceops-request at voiceops.org
Sent: Wednesday, February 23, 2011 6:12 PM
To: voiceops at voiceops.org
Subject: VoiceOps Digest, Vol 20, Issue 21

Send VoiceOps mailing list submissions to
	voiceops at voiceops.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
	voiceops-request at voiceops.org

You can reach the person managing the list at
	voiceops-owner at voiceops.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of VoiceOps digest..."

Today's Topics:

   1. Re: Screwy DSL modem NAT troubles (Scott Berkman)
   2. Question for VoiceOps: Platform Monitoring (Reid Stidolph)
   3. ACMEs SIP Dynamic HNT (Ujjval Karihaloo)

----------------------------------------------------------------------

Message: 1
Date: Wed, 23 Feb 2011 13:13:43 -0500
From: "Scott Berkman" <scott at sberkman.net>
To: "'anorexicpoodle'" <anorexicpoodle at gmail.com>, "'Carlos Alcantar'"
	<carlos at race.com>
Cc: VoiceOps at voiceops.org
Subject: Re: [VoiceOps] Screwy DSL modem NAT troubles
Message-ID: <00a501cbd385$67f26100$37d72300$@sberkman.net>
Content-Type: text/plain; charset="utf-8"

My favorite was the Netopia modems ATT/BS was deploying for some time with all their Business DSL circuits (anything with a static IP) that had an ?undocumented? ALG that could be disabled via the CLI but not the GUI, but it defaulted to on.  It was of course horribly broken.

                -Scott

From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of anorexicpoodle
Sent: Tuesday, February 22, 2011 2:28 AM
To: Carlos Alcantar
Cc: VoiceOps at voiceops.org
Subject: Re: [VoiceOps] Screwy DSL modem NAT troubles

Ill second Alex's sentiment on abandoning port 5060 and make the traffic look like something other than SIP so the ALG doesn't get triggered. We've been doing this for years, works like a charm. 

Speaking of, if anyone from Linksys, D-Link or any other residential grade router manufacturer is out there listening, you have obviously devoted time and effort to coding these ALG's, why not make them work? I would love to hear why it seems there is a concentrated effort to absolutely break voip with atrociously coded ALG's.

On Mon, 2011-02-21 at 22:19 -0800, Carlos Alcantar wrote: 

Linksys ALG seems to break everything sip on the firewall side sonicwall seems to be the death of sip.

Carlos Alcantar
Race Communications / Race Team Member
101 Haskins Way, So. San Francisco, CA. 94080
Phone: +1 415 376 3314  Fax:  +1 650 246 8901 / carlos *at* race.com / www.race.com

-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez
Sent: Monday, February 21, 2011 3:08 PM
Cc: voiceops
Subject: Re: [VoiceOps] Screwy DSL modem NAT troubles

We go through this all the time with Qwest DSL customers.  Unfortunately I don't have model numbers for you, we stopped documenting things when we noticed that they have all new modems every few months.  However we've had success with having the customer call Qwest and tell them they want to run VoIP phones, the Qwest reps seem to know that as a trigger and send a compatible modem.  I do recall that the best ones are Netopia, and we've had good support when we engage them directly via chat.

We also find that modems start going bad slowly after a couple years, and VoIP is the first to get impacted, of course.

Matthew S. Crocker wrote:
> Has anyone else noticed that the latest batch of DSL modems have broken NAT when it comes to VoIP?   I'm seeing stable VoIP customer get broken when the DSL modem is swapped out.  The modem NATs the phones to modem IP port 5060.  So, 10 phones behind the router become one phone to the SBC.  A race condition occurs and phones go in and out of service at random.  It looks like the router is trying to do a SIP ALG but very very broken.
> 
> Do anyone have a DSL modem/router they use that works well with VoIP?
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110223/01f2a9e4/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 23 Feb 2011 11:58:34 -0800
From: Reid Stidolph <reidstidolph at gmail.com>
To: voiceops at voiceops.org
Subject: [VoiceOps] Question for VoiceOps: Platform Monitoring
Message-ID:
	<AANLkTinVYibZazwGvyd+Ur6cOnw1AaQi_Cfn8kDmbT1s at mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"

Hi Voiceops,

Curiosity question:  What tools do you use to monitor and troubleshoot your platform?  Specifically, to track down and troubleshoot small scale issues such as isolated reports of poor call quality, call drops, protocol failures, ect. (i.e. not large scale, such as an entire system failure, interface failure, or switch/router failure)

I would categorize the options as:

-          *Node Level Monitoring *

o   Logs, CDRs, ect. from individual nodes.  These can contain detailed
information or protocol traces from that particular node?s perspective in the call flow.

o   For example, Acme CDRs containing detailed QoS info, disconnect cause
codes, network info ect.

o   Another example might be Broadworks Xlogs, with protocol traces.

-          *In house Network Monitoring*

o   Port-mirrors, SBC packet-trace, or passive/active taps at key locations
in the call flow, that mirror traffic to a in-house system for analysis.

o   For example, mirroring traffic to a Linux system and running tcpdump, or
snoop to gather pcap traces.

-          *3rd Party Network Monitoring*

o   Vendor provided monitoring solutions, that also gather network data from
taps or port mirrors.

o   For example, Brix, Empirix, Netscout, or other, that can provide call
data, protocol traces, and media analysis.

-          *Other?*

Note that I am not really interested in specific vendors here.  Just looking to poll VoicOps for their usage and preference of the four main categories.

In my past experience with service providers, I have used each of the above (some at the same time), and in my opinion they all have their strengths and weaknesses.  I would be interested to know your experience with this.

Thanks!

-Reid Stidolph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110223/de62fecf/attachment-0001.html>

------------------------------

Message: 3
Date: Wed, 23 Feb 2011 15:12:27 -0800
From: Ujjval Karihaloo <ujjval at simplesignal.com>
To: "voiceops at voiceops.org" <voiceops at voiceops.org>
Subject: [VoiceOps] ACMEs SIP Dynamic HNT
Message-ID:
	<EB7435A0AAA8874F845F4A88F1B399240665A8713A at EXMBXCLUS01.citservers.local>

Content-Type: text/plain; charset="us-ascii"

Hi Guys:

   We have not used the ACMEs SIP Dynamic HNT feature, where the ACME sends OPTIONS msgs to individual endpoints on its Access side and adjusts their expires times as per individual Firewalls that they are behind.

While it sounds cool, I was wondering if folks have noticed issues with using it given that some endpoints out there don't even honor the Expires header from REGISTRARs and as the ACME determines the correct NAT interval automatically, it may leave some endpoints de-registers for small intervals (as per ACME ACLI guide).

Thx for your input

UK

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110223/b0e40ffe/attachment.html>

------------------------------

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

End of VoiceOps Digest, Vol 20, Issue 21
****************************************