Send VoiceOps mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."
Today's Topics:
1. Issue with one touch call list buttons on Polycom
501/Broadsoft (Robert Dawson)
2. Re: Issue with one touch call list buttons on Polycom
501/Broadsoft (Jay Ashworth)
3. Re: You MUST attend SIPNOC. You SHOULD propose a
presentation. (PE)
4. Re: Issue with one touch call list buttons on Polycom
501/Broadsoft (Nelson Hicks)
5. What does an ALG actually do? (John Levine)
----------------------------------------------------------------------
Message: 1
Date: Wed, 27 Feb 2013 20:37:40 +0000
From: Robert Dawson <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [VoiceOps] Issue with one touch call list buttons on Polycom
501/Broadsoft
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
We picked up a customer that had a number of 501s. I downloaded the latest
firmware, bootrom and configs and created a new device type. Phones boot,
provision and register fine however there is no icon displayed for the
registered lines and the one touch call list feature does not work.
If I boot against the vanilla configs everything is normal, as soon as I boot
against the "templated" configs it breaks. I have literally stripped everything
out of the configs that I can, they have basic registration information at this
point.
I have made up dozens of Polycom configurations in the past and never seen this
issue.
Of course since the device has been out of warranty since 2007 I have to open a
PPI ticket so I just wanted to see if anyone may have seen something similar in
the past.
Thanks,
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130227/ca7b0a23/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 27 Feb 2013 16:18:15 -0500
From: Jay Ashworth <[email protected]>
To: Robert Dawson <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [VoiceOps] Issue with one touch call list buttons on
Polycom 501/Broadsoft
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Dumb question: your configs are packed rather than prettyprinted, right?
My 601s wouldn't tolerate prettified xml; they puked.
Robert Dawson <[email protected]> wrote:
>We picked up a customer that had a number of 501s. I downloaded the
>latest firmware, bootrom and configs and created a new device type.
>Phones boot, provision and register fine however there is no icon
>displayed for the registered lines and the one touch call list feature
>does not work.
>
>If I boot against the vanilla configs everything is normal, as soon as
>I boot against the "templated" configs it breaks. I have literally
>stripped everything out of the configs that I can, they have basic
>registration information at this point.
>
>I have made up dozens of Polycom configurations in the past and never
>seen this issue.
>
>Of course since the device has been out of warranty since 2007 I have
>to open a PPI ticket so I just wanted to see if anyone may have seen
>something similar in the past.
>
>Thanks,
>Rob
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>VoiceOps mailing list
>[email protected]
>https://puck.nether.net/mailman/listinfo/voiceops
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130227/7aa75596/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 27 Feb 2013 16:45:46 -0500
From: PE <[email protected]>
To: Mark R Lindsey <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] You MUST attend SIPNOC. You SHOULD propose a
presentation.
Message-ID:
<CAHm=SaJQm-E=LCKpuqFTpVnDqw4yLRo+LhkJZhkYSduAh=h...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Well done, Mark.
And for the record, with this email you've already achieved "Acting in a
effortlessly nerdy manner."
On Thu, Feb 21, 2013 at 2:58 PM, Mark R Lindsey <[email protected]>wrote:
> You are REQUIRED to attend SIPNOC 2013, April 22-25, 2013 in Herndon,
> VA. It's a lot like voiceops, but with colocated participants. If
> an asteroid were to hit SIPNOC, the WebRTC Apocalypse would immediately
> ensue.
>
> In this document, the key words "MUST", "MUST NOT", "REQUIRED",
> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
> "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted
> as described in BCP 14, RFC 2119 and indicate requirement levels
> for compliant SIPNOC attendees.
>
> You MAY send a delegate to represent you at other technical conferences
> (or user group meetings) scheduled to occur at the same time.
> Watching a live stream of other concurrent events is OPTIONAL.
>
> You SHOULD propose a talk to present at SIPNOC to explain some
> interesting topic or challenge you've overcome. The talk MUST NOT
> be a marketing talk (except to brag on your own superpower VoIP
> skills.) It is RECOMMENDED that the talk include in-depth technical
> content.
>
> Acting in a effortlessly nerdy manner while at SIPNOC is RECOMMENDED;
> fortunately, 98% of attendees have accomplished this in past years.
> 2% had to apply effort to fit in.
>
> Talking smack about products and vendors or is OPTIONAL. It is
> RECOMMENDED that some technical representatives from vendors be
> sent to participate. The following vendors MUST send representatives
> to appear in person, because their products will surely be discussed:
> Sonus Snom Sansay Sangoma Polycom Metaswitch Grandstream EdgeWater
> Digium Cisco BroadSoft Adtran Acme Packet Aastra
>
> This email MUST NOT be construed as authorized communication of SIP
> Forum, the SIPNOC Program Committee, Marc Robins, or any of his
> cohorts or colleagues. This email does not express the opinions of
> my clients or my employer (unless they want correct opinions).
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130227/0f623f60/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 27 Feb 2013 15:29:00 -0600
From: Nelson Hicks <[email protected]>
To: [email protected]
Subject: Re: [VoiceOps] Issue with one touch call list buttons on
Polycom 501/Broadsoft
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Just to make sure you're aware, the Polycom SPIP 501 phones are not
supported on newer versions of the SIP application (anything 3.2 or
newer) and the configuration files were changed somewhat in version 3.3,
breaking backward compatibility. I think Broadsoft used to have CPE
kits with templates for Polycom verison 3.1.2-RevB, but I don't see them
anymore.
You may end up needing to compare the CPE kit template files for the
3.3.1 version to the stock Polycom config files from 3.3.1 to find the
differences and then apply them to stock Polycom 3.1.x files. Be sure
to download the SoundPoint IP Administrator's Guide - SIP 3.1 to review
config syntax if needed.
On 02/27/2013 02:37 PM, Robert Dawson wrote:
>
> We picked up a customer that had a number of 501s. I downloaded the
> latest firmware, bootrom and configs and created a new device type.
> Phones boot, provision and register fine however there is no icon
> displayed for the registered lines and the one touch call list feature
> does not work.
>
> If I boot against the vanilla configs everything is normal, as soon as
> I boot against the "templated" configs it breaks. I have literally
> stripped everything out of the configs that I can, they have basic
> registration information at this point.
>
> I have made up dozens of Polycom configurations in the past and never
> seen this issue.
>
> Of course since the device has been out of warranty since 2007 I have
> to open a PPI ticket so I just wanted to see if anyone may have seen
> something similar in the past.
>
> Thanks,
>
> Rob
>
>
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130227/b3c3e6ec/attachment-0001.html>
------------------------------
Message: 5
Date: 27 Feb 2013 21:33:04 -0000
From: "John Levine" <[email protected]>
To: [email protected]
Subject: [VoiceOps] What does an ALG actually do?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
I realize that an ALG is a hack in a router that is supposed to allow
SIP packets to go through a NAT router. I also realize that for
modern SIP equipment, ALG usually causes more problems than it solves,
and that it's described in RFCs 2663, 3424, and others.
What I can't find anywhere is what a SIP ALG actually does to the
packets. Is that written down anywhere, or is it just network
folklore?
------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
End of VoiceOps Digest, Vol 44, Issue 21
****************************************
