[Asterisk-Users] Snom subscribe/notify problem

[Michael George]

On Mon, Apr 18, 2005 at 11:34:03AM -0400, Michael George wrote:
> I have a Snom-190 that I've successfully used on a * box with the LED's
> lighting up when a line goes active.
> 
> I have moved it to another box, though, and I'm having trouble with it.
> 
> It almost seems as though there is a limit to how long a sip channel name can
> be for the subscribe/notify to work right.
> 
> If I have the following in sip.conf:
> --------------------------------------------------------------------------
<snip> 
> --------------------------------------------------------------------------
> 
> and this in extensions.conf:
> --------------------------------------------------------------------------
<snip> 
> --------------------------------------------------------------------------
> 
> and the snom is set to light up it's LEDs for extensions 200-203.
> 
> The LED's work just find when I call the snom (SIP/snom), but the light for
> the grandstream will not light up (SIP/PewTest-grandstream).
> 
> If I change the entries for the grandstream from "PewTest-grandstream" to
> "grandstream", then the light will work for that line, too.
> 
> If I change the entries for the snom from "snom" to "PewTest-snom", then the
> snom light fails to work.
> 
> I have run sip debug mode on the snom peer and * is not sending out the NOTIFY
> messages, so it does not appear to be an issue with the Snom.
> 
> Is there some type of limit to the SIP SUBSCRIBE/NOTIFY stuff that only allows
> 8 character channel names?

It appears that the hyphen (-) in the channel name is what is breaking things.
If I take that out, all seems to work fine.

Anyone know why that might be?

-- 
-M

There are 10 kinds of people in this world:
	Those who can count in binary and those who cannot.