Polycom 450 and VVX 1500 lines not registering

[Rick Cogley]

Hello - I have a Polycom VVX 1500 and a couple 450s that boot up, and the lines appear in the LCD but won't register. My 670's, 331's and 7000 are fine. 

I have device files set up like this - 

* Active - firmware 3.2.6, bootrom 4.3.1 (what I was using with openUC 4.4 and all phones were fine with it)

* Active - firmware 4.0.7, bootrom 4.4.0B - working for my 670s, 331s and 7000.

* Inactive - firmware 4.0.10, bootrom 4.4.0B

Apparently, the VVX 1500 won't accept the 4.0.7 firmware, per Polycom's gigantic PDF matrix online. It appears to need 4.0.10. 

In the phone groups I created, I can only select general 3.x.x or 4.x.x series from the dropdown, not specific firmware revisions. 

So firstly, can anyone say, how can I specify that the VVX 1500 use the 4.0.10 after I activate it - is that automatic if that device file set is active, or will that cause all the 670s to try (and maybe fail) to use it? 

Secondly, I tried specifying the 3.x.x version in the phone group for the 450s. But no matter what I do, I cannot get it to take. I tried resetting to factory using those emacs-like keypresses you have to do (er, 1357 or 468* iirc) but, they just keep coming up with the same registration error, and confirming in the LCD, version 4.0.7. Is it even possible to downgrade one of these phones once you upgrade it? 

Just worried about bricking my phones and I hope someone on the list can shed some light. 

Thanks sincerely for your time,

Rick 

[Rick Cogley]

Hmm, I thought I would experiment so I tried enabling the 4.0.10. Sipxecs says: 

You must undeploy SPIP fw 4.0.7 br 4.4.0B before you can deploy these files. You can only have one set of files of type Polycom SoundPoint IP/SoundStation IP/VVX deployed at a time.

Just worried about bricking my phones so I'd appreciate anyone's comments on this. 

Thanks,

Rick

[Rick Cogley]

Ok, for what it's worth I enabled 4.0.10 and restarted everything. All the same phones work with that version, yet my 450's and VVX still won't register lines. 

On Wednesday, April 13, 2016 at 7:59:04 AM UTC+9, Rick Cogley wrote:

[Rick Cogley]

Ok, the problem was that I had entered (for some reason) 5060 in the port box, with nothing in the IP address, on the Outbound Proxy setting in SIP Servers, in the affected phone groups. 

Removing that port, so both IP and port are blank, saving, and resetting the phones, allowed them to register as normal. 

All my other phone groups had both those set to blank, which is the default. 

Perhaps when you set just the port and not the IP, the code strings together an URL like: http://5060 which won't work of course.

Anyway, sorry to bother.

[Joegen E. Baclor]

It's actually not the blank host that is the issue.  If the proxy host is blank, then it is assumed to be the domain.  If you put an explicit port (5060), the proxy URI ceases to be an SRV record.    If your domain is not fully qualified, then it can't be resolved using a plain A/AAAA lookup.  I am sure someone will commit the same mistake in the future so we need to treat this as a bug.   The rule should be, if port is specified, then the proxy host must also be specified.

-joegen

--
You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/8d2e325f-e02b-4d78-b8a2-2c30c1631e3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ryan Colobong]

Will create a redmine ticket for this.

Thanks Rick for reporting this issue.

regards,

To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/570F2D5F.3000905%40gmail.com.

[Rick Cogley]

Thanks Joergen, Ryan for the explanation and support. 

Today I additionally found out that with 4.0.10, BLA stops working, so, I am reverting the phones to 4.0.7, which tested fine with BLA yesterday.

Another related site to yours mentions that this BLA issue gets fixed with 5.2.5 but, there's no 5.x.x to choose from in the phone groups, so I'll just stick with what works for now. 

Kind regards,

Rick 

On Thursday, April 14, 2016 at 2:44:12 PM UTC+9, Ryan Colobong wrote:

Will create a redmine ticket for this.

Thanks Rick for reporting this issue.

regards,

On Thu, Apr 14, 2016 at 1:40 PM, Joegen E. Baclor <joegen...@gmail.com> wrote:

It's actually not the blank host that is the issue.  If the proxy host is blank, then it is assumed to be the domain.  If you put an explicit port (5060), the proxy URI ceases to be an SRV record.    If your domain is not fully qualified, then it can't be resolved using a plain A/AAAA lookup.  I am sure someone will commit the same mistake in the future so we need to treat this as a bug.   The rule should be, if port is specified, then the proxy host must also be specified.

-joegen

On 04/14/2016 12:51 PM, Rick Cogley wrote:

Ok, the problem was that I had entered (for some reason) 5060 in the port box, with nothing in the IP address, on the Outbound Proxy setting in SIP Servers, in the affected phone groups. 

Removing that port, so both IP and port are blank, saving, and resetting the phones, allowed them to register as normal. 

All my other phone groups had both those set to blank, which is the default. 

Perhaps when you set just the port and not the IP, the code strings together an URL like: http://5060 which won't work of course.

Anyway, sorry to bother.

--
You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-developers-group+unsubscribe@googlegroups.com.
To post to this group, send email to sipfoundry-users-and-developers-group@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/8d2e325f-e02b-4d78-b8a2-2c30c1631e3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "SIPfoundry users and developers group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipfoundry-users-and-developers-group+unsubscribe@googlegroups.com.
To post to this group, send email to sipfoundry-users-and-developers-group@googlegroups.com.

Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.