Graham

  • Joined
  • Level2
  • Points174
  • Posts16
  • Solutions0
  • Thanks Chris,

    I used to have Cisco routers there, but Swisscom kept upgrading the service faster than I could buy new routers. With the Cisco very little was obscured and you could make them do almost anything. However I am very happy to live with the minor Internet Box issue, but would welcome a fix - I have a messy workaround.

    Thanks for your help. I’ll take it up with Swisscom in a few weeks.

    Graham

  • The NAS is set to DHCP and always acquires the correct IP address (192.168.1.4) given out by the router whenever it is powered on.

    The problem is that if it has been off for a few weeks, there is no way for the router to issue the WOL frame to power it on and I am at a distance…

  • It does have a DHCP reservation. It is in “Assign static IP address automatically”. There is no WOL command in that list.

    The WOL command is in the “Not Connected” list. I would expect that if a device was in the DHCP reservation list, it should be excluded from dropping off that list.

    I agree that if nothing timed out the list would be very unmanageable… very…

    Despite this, I think that the Internet-Box 3 is an excellent router. The features list is very good. I wish I could achieve the same with a UK based Telco - in particular, the VOIP side.

    Thanks

    Graham

  • It did occur to me, but in today’s energy world, I would feel bad about leaving it on. It is only a few watts, but…

    Graham

  • The Internet-Box holds a mapping of MAC to IP reservations for DHCP. This is persistent.

    The only place where the WOL command appears on the Internet-Box (as far as I am aware) is in the “Not Connected” list. This list is not persistent, with entries ageing and disappearing over time. It would be convenient if those entries which had a reserved IP did not “age”. I think this is a new problem that I did not have in previous version of the software/hardware.

    I do have a back door VPN which is functional, but messy - the VPN is L3 and WOL is L2…

    I have found Swisscom’s Customer Service to be excellent in the past, so I am sure that when I contact them next month, I will get an excellent response. I wish other Telco’s were half as good.

    Thank you for all the useful comments.

    Graham

  • Thanks Chris

    I think that the issue is really an Internet-Box software issue rather than anything to do with WOL and IP/Ethernet. The Internet-Box knocks anything that BT produces into a cocked hat - particularly their VOIP offerings.

    I think that I’ll bother Swisscom when I am back in the country.

    Graham

  • It does have a reservation. 192.168.1.4.

  • Hi Chris,

    WOL works fine from the Internet-box. It is just that the Internet-Box “forgets” the NAS after a few week’s of inactivity and it disappears from the “not connected” list along with its WOL command.

    I used to program the NAS to start up automatically for a hour a week, but that was messy.

    i would just like ensure the Internet-Box did not lose the entry for NAS even though it has a static IP.

  • WOL works fine until the Internet-Box drops the NAS from the list of “Not Connected” devices. (4 weeks?) Then there is no way send the WOL command to the NAS.

    I can get it back with another VPN device, but I’d like to use the Internet Box as it is simpler (if it works…)

  • Static addressed devices disappear from not connected list

    I have a NAS server with a static address on an Internet-Box 3. If the NAS is powered down for a time, the entry disappears from the Network->Device List->Not connected list.

    This is a problem as the Wake-on LAN option disappears with it and I cannot power the NAS on using the VPN. As I am 1,500kms from the NAS this is not very convenient when it happens.

    If this issue has been addressed before, I have failed to find it.

    Graham

  • @MichelB

    Thank you that makes complete sense.

    I was simply confused as my definition of Internal was different! The functionality is not an issue.

  • I have done that, but without the expected result.

    The OCD part of me just likes to get things to work the way I think that they should. I think I’ll give up on it.

    The Davos is a very nice phone.

    Thank you for your help.

  • It certainly seems like it is not available.

    The firmware is all up to date on both, although the Swisscom website suggests that the latest firmware for the phone is vH032 (2019) which is strange. I have a thing about keeping software up to date.

    It is not really important and I can live without having Alphorns for internal calls:-).

    Thank you for your help.

  • I have extensions 203,203, 220 & 221. I would have thought that calls between them were “Internal”, but that does not activate the internal ring tone.

  • Thank you.

    I think I understand the instructions.

    HD Davos number is 203

    External Calls Ringtone: Little Bells

    Internal Calls Ringtone: Classic Phone

    Call from Fixnet: Little Bells.

    Call from another DECT phone on InternetBox (204): Little Bells!

    I would have expected Classic Phone.

    What does Internal mean?

    The Davos is has FW VH034.

    It is not important, but I’d just like to know where I have got it wrong.

    Graham

  • HD DAVOS - No Internal Ringtone

  • I have an HD Davos connected to an InternetBox 3. The HD Davos is on 203. There is a non Swisscom DECT phone on 204. There is an IP phone on 221.

    On the HD Davos, there is the facility to have different ringtones for Internal and External. From both 204 and 221, I get the External ringtone despite having set a different one for Internal.

    It is not a great problem, but am I missing something?

    Graham

    • @Graham

      The HD-Phone only considers a call as internal when it’s triggered from another HD-Phone using the Menu function.

      Using the short number like “203” is considered an external call since it’s on the SIP and not the DECT level. Also calls from SIP phones or analoge phones are considered external.

      Thus, the experience you have is expected. I agree that it’s not the optimal user experience but it’s a limitation from the architecture.