Jump to content

skyplonk

Members
  • Posts

    24
  • Joined

  • Last visited

Everything posted by skyplonk

  1. Happy to give it a try in our test environment (WIN64).. do you have a change log to go with this?
  2. Great! Upgrading our development CloudPBX servers now. Almost ready to finish that project too, BTW.
  3. Right! That explains a few random shutdowns then!
  4. Ok, cool. Guess I better update our 4.5 build customers
  5. Hi There, I notice the fix is a 4.5 build. Was the bug only in 4.5 builds or earlier builds also? Cheers
  6. Have just logged a fault with Snom. We have the same issue.
  7. Hi Guys, What is the tie-up/changes I see on the SnomONE site with Vodia Networks? Who are they? There does not seem to be a lot about them online. The new licensing changes vs. SnomONE Yellow and Blue seem strange. What happens to current users running SnomONE Yellow or Blue and want to upgrade? What happens to PBXnSIP customers that want to/need to/can upgrade to SnomONE Version 5? Cheers
  8. Hi Everyone, We have this on the older 4.3 builds and the new 4.5 builds. Only happens for us a few times a month at our bust site (so hard to capture/reproduce) but is embarrassing! One company is a medical center and getting 2 patients talking together is not a good look. I have tried to re-create it hundreds of times, and cant. Bu it happens. Any ideas?
  9. It means Do Not Disturb is active on that extension Cheers
  10. We have this intermittently as well. have not been able to get enough diag info to log a fault. When it happens to us, the buttons are still "mapped" on the phone (GUI) as well as the SnonONE GUI, but presing the button does nothing at all. Stop and start of the SnomONE (or PBXnSIP service)or update of the buttons on the SnomONE GUI.. I updated a site to Version: 4.5.0.1090 Epsilon Geminids (Win64) 2 weeks ago and they had it yesterday.
  11. We get this a lot now. Used to get it all the time in early version 4 builds, Went away for a long time, but seems to be happening again. Might be just coincident. If we hard code to a proxy with its IP it is never an issue, if we have it pointing to the FCDN of the server after the connection is backup it sits on "408 Request timed out - Retry in 60 seconds", but never does. If we hit "Register" it is fine. We don't want to hard code to the IP of the server as we have SRV entries on the Domain Name and some failover/load balancing setup. If we hard code to 1 server we loose redundancy.
  12. Cheers guys. Will give it a go again on Monday.
  13. What a good start! For us here, it seems a bit slow. Browsing the site can take 20 - 30 seconds to bring up a page or an assessment. What is performance like for you guys at Snom?
  14. Good work! we have had customers reporting this off and on for a while now, but I have never been able to recreate the issue. This sounds like it to me. Also seems to have the same issue with a mix of agent groups and hunt groups. The same thing happens if we make call 1 into a agent group..
  15. An answer the the first question would be good tho, how do you do a manual upgrade? We have SOHO's that are on a private tail and the automatic upgrade system is not going to work..
  16. Yes, as I motioned above I have. I can call in, enter my ext number and password, ring external numbers and internal numbers. just NOT service flags. It say I am not allowed to make this call. I have put wild cards in the service flags, I have manually put the ext numbers of the users allowed to change the status.. nothing. Works fine internally, just not via the calling card. We know calling card works as I (our customer) can call any thing once they call in. We know the service flags work and they can be set internally. So something is not right.
  17. Sounds good, but it will not work for what we need. We need to be able to call in from any phone, any number, anywhere in the world to turn service flags off and on. So using PVA will limit how we could use this.
  18. Yup, and it is set to manual and as per my other post we have set (tried wild card and the ext number) "Extensions that may change status" Still does not work.
  19. Yup, can make normal (from PBX) out bound calls fine. Can call into the calling card, authenticate, then call other uses/extensions on the system. I can even call o the outside world. Just not able to turn service flags off and on.
  20. Also, just to add a note to Kelly's config below the service flag has a wild card for "Extensions that may change status" And the calling card is allowed to "Allow calling accounts on the PBX" And it still does not work externally.
  21. Is this not normal PBX behavior?. Every SnomONE/PBXnSIP site we have sold uses BLF key mapping for call pickup. Every other non Snom PBX we have is also the same. Cisco UC520, Epygi Quadro, 3Com and Grandstream all allow you to intercept a watched ringing extension by using the mapped/BLF key. I see where the confusion is tho.. Snom say: Monitor extension: When a call is either coming in on that extension (fast blinking) or is on hold or parked (indicated by slow blinking), you can pick the call up by pressing the button. Calls that are connected have a solid color. And Busy Lamp Field (BLF): This mode shows when the specified extensions are in use. When the extension is connected, the LED will be solid; when the extension is ringing, the light will blink fast; and when the extension is holding a call, the light will blink slowly. This mode is similar to the monitor extension mode; however, it does not support the picking up of calls. When the user presses the button, the phone always dials the programmed. Personally, I have never used "Monitor extension" only BLF. So for me BLF works how I want it to, but not how Snom says it does.
×
×
  • Create New...