Are they possibly being blocked by iptables? I've had this happen before and I added the local network subnet to the White List and it stopped.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/859e441c-a2ec-4b2b-804e-7eed42182ac4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Doesn't matter. I have the same situation try iptables -L -n -v | grep 192.168* or whatever your network subnet is
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/dba77f31-af5a-4c2f-8bdd-d57fef7a7bfb%40googlegroups.com.
Are the .122, .79, .134 and. 137 addresses on your private network? Try adding your private network to the firewall white list in the format 10.0.0.0/24 or whatever your subnet format is. Apply it and wait for configuration deployment to finish. Plug the phones in and see if they come up
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/dba77f31-af5a-4c2f-8bdd-d57fef7a7bfb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAJybiSRS%3DTa4KSWod4aBd1Oui3fkvf2Ym4V5Tp42F84QSqTJUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Maybe a rogue DNS server.
Sent with my two left twiddling thumbs. Please excuse the brevity.
Maybe a rogue DNS server.
Sent with my two left twiddling thumbs. Please excuse the brevity.
From: sipxco...@googlegroups.com <sipxcom-users@googlegroups.com> on behalf of Michael Picher <mpi...@gmail.com>
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/dba77f31-af5a-4c2f-8bdd-d57fef7a7bfb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAJybiSRS%3DTa4KSWod4aBd1Oui3fkvf2Ym4V5Tp42F84QSqTJUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
--Thanks,Mike
-----------------------------------------------------------------------------------------There are 10 types of people in this world... Those who understand binary and those who don't.
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAAfvEN5JdMuLJZNE6ud8N6oq341HB-1twE5yY1Ht73coVajaBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/BLUPR0701MB1042A059B3289443EE390AB4FDD70%40BLUPR0701MB1042.namprd07.prod.outlook.com.
Are the .122, .79, .134 and. 137 addresses on your private network? Try adding your private network to the firewall white list in the format 10.0.0.0/24 or whatever your subnet format is. Apply it and wait for configuration deployment to finish. Plug the phones in and see if they come up
On Oct 21, 2016 11:22 PM, "Tommy Huie" <m...@tommyx.com> wrote:
here's the output:12 1515 ACCEPT all -- eth0 * 10.0.0.49 0.0.0.0/06201 549K DROP all -- * * 10.0.0.122 0.0.0.0/048075 3449K DROP all -- * * 10.0.0.79 0.0.0.0/0421K 30M DROP all -- * * 10.0.0.134 0.0.0.0/0464K 33M DROP all -- * * 10.0.0.137 0.0.0.0/0does this mean for these four units, the connection is 'blocked' and therefore, cannot register with the boot server (10.0.0.49)?thanks for your expertise...tommy
On Fri, Oct 21, 2016 at 5:48 PM, Tommy Laino <toml...@gmail.com> wrote:
Doesn't matter. I have the same situation try iptables -L -n -v | grep 192.168* or whatever your network subnet is
On Oct 21, 2016 8:43 PM, <tommy...@gmail.com> wrote:
hmmm. i can check but probably not as the PBX is on its own LAN and all the phones are on this LAN. i brought home an offending phone just to test it out from outside the PBX LAN.
On Friday, October 21, 2016 at 5:01:08 PM UTC-7, tommy...@gmail.com wrote:hi there:
a handful of our polycoms suddenly became disabled with the error message 'URL call is disabled'. but when i put one of these phones on my home network, it works and is connected to the work PBX. i think what is going on is that the phone cannot find the boot server and uses the existing configuration (which does work).
i tried reformatting a couple of the phones, deleting the config files on the boot server (basic sipxcom setup), and starting anew. no luck. these phones do pick up an IP address via DHCP but seem to not even touch the config files on the boot server.
thanks for any suggestions you may have...
tommy
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/20163fd2-2ede-405e-b1dd-9e4d313933dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAC_Y%2BMAAAP9vQ-a%2B64kXNMydOVonaNaWJURoYP7EsPbCrgOGpQ%40mail.gmail.com.
Or someone plugged a device onto the network that is handing out DHCP, and doesn’t include your Option 66 or SRV records.
Also, check security. As a matter of habit, I always change system/security Block DoS attackers to ban time 15, max retry 3, find time 60. There as an old bug in Polycom phones where their behavior looked like a Denial of Service attack. The default setting ban those phones from being able to register again once they meet the requirements of the rule. Those changes keep it from being a permanent BAN.
From: prg...@gmail.com [mailto:prg...@gmail.com]
On Behalf Of Gerald Drouillard
Sent: Wednesday, November 8, 2017 12:21 PM
To: buzz...@gmail.com
Cc: sipxcom-users <sipxco...@googlegroups.com>
Subject: Re: [sipxcom-users] Re: Phones Suddenly get URL call is disabled
In my experience it tends to be a duplicate IP on the network. Mostly because of poorly configured DCHP servers or maxing out their scope.
On Wed, Nov 8, 2017 at 12:30 PM, <buzz...@gmail.com> wrote:
I have experienced the same issue and the fix I found that worked was as follows:
1. delete the mac address from the dchp server
2. take the ip address out of the pool that was assigned to the phone
3. plug the phone back in and it is assigned a new ip address
4. phone is now able to make calls and no more URL disabled
I have linked this happening due to lack of use. This usually happens on phones that are not used on a regular basis.
To me, this is a band aide fix, still trying to figure out exactly why this happens, but this is the fix I have found to work in the interim.
--buzz
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/20163fd2-2ede-405e-b1dd-9e4d313933dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to
sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAC_Y%2BMAAAP9vQ-a%2B64kXNMydOVonaNaWJURoYP7EsPbCrgOGpQ%40mail.gmail.com.
300 Brickstone Square
Suite 104
Andover, MA. 01810
Or someone plugged a device onto the network that is handing out DHCP, and doesn’t include your Option 66 or SRV records.
Also, check security. As a matter of habit, I always change system/security Block DoS attackers to ban time 15, max retry 3, find time 60. There as an old bug in Polycom phones where their behavior looked like a Denial of Service attack. The default setting ban those phones from being able to register again once they meet the requirements of the rule. Those changes keep it from being a permanent BAN.
From: prg...@gmail.com [mailto:prg...@gmail.com] On Behalf Of Gerald Drouillard
Sent: Wednesday, November 8, 2017 12:21 PM
To: buzz...@gmail.com
Cc: sipxcom-users <sipxcom-users@googlegroups.com>
Subject: Re: [sipxcom-users] Re: Phones Suddenly get URL call is disabled
In my experience it tends to be a duplicate IP on the network. Mostly because of poorly configured DCHP servers or maxing out their scope.
On Wed, Nov 8, 2017 at 12:30 PM, <buzz...@gmail.com> wrote:
I have experienced the same issue and the fix I found that worked was as follows:
1. delete the mac address from the dchp server
2. take the ip address out of the pool that was assigned to the phone
3. plug the phone back in and it is assigned a new ip address
4. phone is now able to make calls and no more URL disabled
I have linked this happening due to lack of use. This usually happens on phones that are not used on a regular basis.
To me, this is a band aide fix, still trying to figure out exactly why this happens, but this is the fix I have found to work in the interim.
--buzz
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/20163fd2-2ede-405e-b1dd-9e4d313933dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAC_Y%2BMAAAP9vQ-a%2B64kXNMydOVonaNaWJURoYP7EsPbCrgOGpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/BL2PR07MB24188C038B7DE67351FABF18FD560%40BL2PR07MB2418.namprd07.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAAHujP6h_4DzG-0_%2BZ9RQGtNSzuMRGoHZQP0ANuLBu%2Bdw7HgkQ%40mail.gmail.com.