Phones Suddenly get URL call is disabled

1,028 views
Skip to first unread message

tommy...@gmail.com

unread,
Oct 21, 2016, 8:01:08 PM10/21/16
to sipxcom-users
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

Tommy Laino

unread,
Oct 21, 2016, 8:11:58 PM10/21/16
to Tommy Huie, sipxcom-users

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.

tommy...@gmail.com

unread,
Oct 21, 2016, 8:42:59 PM10/21/16
to sipxcom-users, tommy...@gmail.com
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.

Tommy Laino

unread,
Oct 21, 2016, 8:48:57 PM10/21/16
to Tommy Huie, sipxcom-users

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.

Tommy Huie

unread,
Oct 21, 2016, 11:22:39 PM10/21/16
to Tommy Laino, sipxcom-users
here's the output:

   12  1515 ACCEPT     all  --  eth0   *       10.0.0.49            0.0.0.0/0   
 6201  549K DROP       all  --  *      *       10.0.0.122           0.0.0.0/0   
48075 3449K DROP       all  --  *      *       10.0.0.79            0.0.0.0/0   
 421K   30M DROP       all  --  *      *       10.0.0.134           0.0.0.0/0   
 464K   33M DROP       all  --  *      *       10.0.0.137           0.0.0.0/0   

does 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

Tommy Laino

unread,
Oct 21, 2016, 11:39:40 PM10/21/16
to Tommy Huie, sipxcom-users

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

Tommy Huie

unread,
Oct 22, 2016, 3:11:45 AM10/22/16
to Tommy Laino, sipxcom-users
ok thanks for the suggestion. i'll try it out on monday!

Michael Picher

unread,
Oct 22, 2016, 3:49:04 AM10/22/16
to Tommy Huie, Tommy Laino, sipxcom-users
The phones are getting blocked for some reason...  I'd look into that before blanket whitelisting things.

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-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.

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.

Todd Hodgen

unread,
Oct 22, 2016, 4:02:38 AM10/22/16
to Michael Picher, Tommy Huie, Tommy Laino, sipxcom-users

Maybe a rogue DNS server.

Sent with my two left twiddling thumbs. Please excuse the brevity.


From: sipxco...@googlegroups.com <sipxco...@googlegroups.com> on behalf of Michael Picher <mpi...@gmail.com>
Sent: Saturday, October 22, 2016 12:48:52 AM
To: Tommy Huie; Tommy Laino
Cc: sipxcom-users
Subject: Re: [sipxcom-users] Re: Phones Suddenly get URL call is disabled
 

Gerald Drouillard

unread,
Oct 22, 2016, 10:21:31 AM10/22/16
to Todd Hodgen, Michael Picher, Tommy Huie, Tommy Laino, sipxcom-users
I have seen duplicate IP's on the network cause this...especially if there are more than 1 dhcp servers.

On Sat, Oct 22, 2016 at 4:02 AM, Todd Hodgen <t.ho...@misiusystems.com> wrote:

Maybe a rogue DNS server.

Sent with my two left twiddling thumbs. Please excuse the brevity.


To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@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.
--
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.

--
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.

For more options, visit https://groups.google.com/d/optout.



--
Regards
--------------------------------------
Gerald Drouillard
Cell: 734.502.4356

Jim Gill

unread,
Oct 31, 2016, 1:59:41 PM10/31/16
to sipxcom-users, m...@tommyx.com
I just went through this where suddenly my Polycom 335 displayed "URL Call Disabled"  Not sure what changed but they were not able to register or provision.  Adding the subnet to the Whitelist fixed this for me.
Thanks Tommy!
Jim.


On Friday, October 21, 2016 at 11:39:40 PM UTC-4, Tommy Laino wrote:

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/0   
 6201  549K DROP       all  --  *      *       10.0.0.122           0.0.0.0/0   
48075 3449K DROP       all  --  *      *       10.0.0.79            0.0.0.0/0   
 421K   30M DROP       all  --  *      *       10.0.0.134           0.0.0.0/0   
 464K   33M DROP       all  --  *      *       10.0.0.137           0.0.0.0/0   

does 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.

buzz...@gmail.com

unread,
Nov 8, 2017, 12:30:14 PM11/8/17
to sipxcom-users
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



Gerald Drouillard

unread,
Nov 8, 2017, 3:20:46 PM11/8/17
to buzz...@gmail.com, sipxcom-users
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.

--
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.

For more options, visit https://groups.google.com/d/optout.

Tommy Laino

unread,
Nov 8, 2017, 3:26:46 PM11/8/17
to Gerald Drouillard, buzz...@gmail.com, sipxcom-users
If it's a smaller system, I've found this to be related to SipXcom firewall. Try adding the IP address of the phone to the white list to see if the phone comes back up. If it does, you will need to make some tweaks to the timers for the blacklist

Todd Hodgen

unread,
Nov 8, 2017, 3:27:09 PM11/8/17
to Gerald Drouillard, buzz...@gmail.com, sipxcom-users

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.



 

--

Regards
--------------------------------------
Gerald Drouillard
Cell: 734.502.4356

--

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.

Michael Picher

unread,
Nov 8, 2017, 3:50:46 PM11/8/17
to Todd Hodgen, Gerald Drouillard, buzz...@gmail.com, sipxcom-users
well, you can find out easily if it's firwall by just restarting iptables. it should clear out the entries...

whitelisting phones is a bad practice. if firewall is doing it, it's doing it for a reason...  sort it out.

create a new phone group, move the phone into that group (before you put any settings on it) and re-send the phone profiles.


Michael Picher, VP of Product Management
eZuce, Inc.

300 Brickstone Square

Suite 104

Andover, MA. 01810


Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you.

On Wed, Nov 8, 2017 at 3:27 PM, Todd Hodgen <t.ho...@misiusystems.com> wrote:

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.



 

--

Regards
--------------------------------------
Gerald Drouillard
Cell: 734.502.4356

--
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.

--
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.

Tommy Laino

unread,
Nov 8, 2017, 3:54:24 PM11/8/17
to Michael Picher, Todd Hodgen, Gerald Drouillard, buzz...@gmail.com, sipxcom-users
Agreed Mike. Just something I do for troubleshooting purposes. I should have clarified to not leave it that way. You can also do iptables -L -n -v | grep {phone IP} and see if the phone ip is listed

ja...@dscope.com

unread,
Nov 22, 2017, 10:54:55 PM11/22/17
to sipxcom-users
I ran into this exact problem and what worked for me was:

1) I changed the users SIP PASSWORD.
2) Sent the Profile for the particular phone.
3) Restarted the phone.

Like I said that did the trick for me.
Reply all
Reply to author
Forward
0 new messages