Topic: Selintra with latest version remote handsets won't register

[pmacdona]

Upgraded to the latest version, now remote handsets won't register - wrong password??, local phones ok.

[SARK devs]

Hi pmacdona,

Upgraded to the latest version, now remote handsets won't register - wrong password?

Version 340 has improvements to remote provisioning. However, I'm not sure how these would affect your remote phones.

Version 340 allows you to specify the registrar for the remote phone. Remote phones are provisioned using http. You must specify http and the server ip address in the phone.

Since, I'm not sure of the phone or setup you are using, all I can suggest is that you delete the extension for your remote phone, and recreate it.

Also, if you are using a Snom I have noticed that occassionally they have password problems. I have found that reentering the password fixes this problem.

Regards,

Selintra

[Franco]

I'm still using 334 and not having such problem, but saw this post and I wonder if what's causing this isn't the fact that service providers block port 80?

[pmacdona]

I had it working with SPA-941's, but since upgrading when they are on the same remote site as before they will not not register, asterisk -r -vvv, shows wrong password, I have tried deleting and re-creating the extension and still no go, funnily enough x-lite still works ok, just the 941's??, the 941's are fine on the same subnet as the server, but I have had the phones working previously at 2 remote sites and since upgrade none will register remotely?

[pmacdona]

OK, fresh install, this time sme as gateway & all is well, however I am having trouble with call quality, I am using g726, from remote phones having some packet loss & jitter issues, one site should have heaps of b/w 1.5/256 dsl, with no other activity, will look into in depth tonight, may be router issues, anyone else een down this same path?