Jump to content

Randall Garner

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by Randall Garner

  1. Hello, We are trying to update our SNOM ONE BLUE from 4.5.0.1090 to 4.5.1.1107. The upgrade instructions state to check the Base64 license on the website https://snomone.com/upgradev4, which reported "The Upgrade Will Work". However, after performing the update, the PBX is reporting No License on the Status page, as well as logging No License when lines attempt to register. Please advise. Thanks, Randall
  2. We are noticing about a 3 second delay on intermittant inbound calls. We started logging the calls and reported the issue to our SIP Trunk provider. Our Trunk provider, WideOpenWest (WOW) has ran an advanced trace on the calls we experienced the delay and told me the following - "The SNOM SIP device introduces a delay of 100ms between consecutive packets when answering the call, without changing the SSRC, and thereby confuses our DSPs." I've hear our provider refer to their SIP technology as MetaSwitch, but I'm not positive. We are currently on version 4.5.0.1090 Epsilon Geminids (Win64) Our main number goes to a Hunt Group with seven extension all in Stage 1 and Duration set to 15, with the final option going to an Auto Attendant. Any advise on where to go from here? Thanks, Randall
  3. This morning I tried an 866 number two times - one with and one without the "1". Both test calls failed with message on the LCD - "Disconnected: Not Found" followed by the phone number dialed. Attached is both call logs from the test calls. Please advise. Thanks for your help, Randall With_1.txt WithOut_1.txt
  4. Since we upgraded to 4.5.0.1090 Epsilon Geminids last week, we found we are not able to make outbound calls to 800 numbers. When we attempt this, we get a message stating "Disconnected". We could dial the 800 numbers before the upgrade. I've check our Dial Plan and it doesn't appear to have changed. I have attached to this ticket. Please advise, Randall
  5. I updated to the latest version, then applied the custom headers you recommended. I'm pleased to report we can make outbound calls! Thanks for your help, Randall
  6. Thanks to the helpful link provided on the logging settings in my current/old version, the attached log looks much better. Again, this attachment (outbound5.txt) is our current working system test call from same extension to same external phone number. outbound5.txt
  7. I did forget to upload the attachment again...sorry! outbound4.txt
  8. Hello Mr. X, I would be more than happy to provide the requested information and start a support ticket; however, the SIP service we receive from our provider does not have any authentication - it's not hosted or served over the internet. Our provider gave us a direct ethernet cable and IP address to setup our PBX. I don't think this type of service delivery will be able to be tested on your end. Please let me know how you would like me to proceed. Thanks, Randall
  9. I attempted to capture the call log of a test call this morning, but it appears this version of PBX software (2011-4.2.1.4025) is not logging the same level of detail as the newer version log (4.5.0.1090) that I've captured to TXT files and uploaded to this ticket previously. I have uploaded the log file as I see it now (outbound4.txt)...please review and tell me what am I missing? Does the newer version offer better logging detail by default? What do I need to enable on this current version to be able to log the correct information you need?
  10. Attached is the log file as requested. Attempted to place the external call to the same number, from the same VoIP phone, but on the new version of PBX software. Looking forward to hear what you find about the headers. Thanks, Randall outbound3.txt
  11. 24.96.139.170 is the correct IP address for our providers SIP truck proxy. And since they only change today has been the version of PBX software, I don't understand how this would cause network issues suggested. Since we could not make any outbound calls, I've restored the previous version - 2011-4.2.1.4025 (Win64). After the restore, we could immediately place outbound calls again. Now that we are back on the old version, I will gather the SIP log you requested, then perform the upgrade again and capture another SIP log in the new version. To make sure I get you the exact information you need, can you please tell me how to pull the SIP log you requested? Once I received your response, I will schedule to gather these logs first thing the following morning and post here. Thanks for your assistance, Randall
  12. I just performed the update to 1090. Tested outbound calls again, but same result. I noticed on the Calls screen, the outbound calls have a State of "Idle". I've reviewed the links provided about Custom Headers, but this setting appears to be the same as before the upgrade this morning. However, I contacted our SIP provider to verify the correct setting and it appears we are configured correctly. Also while on the phone, we placed a test outbound call and our phone provider stated they never observed the outbound call hit their system. Lastly, I've attched two call logs - the one I forgot to upload earlier (outbound.txt), and a new one after the lastest update (outbound2.txt). We are still without outbound calls. Please advise at your earliest convenience. Thanks, Randall outbound.txt outbound2.txt
  13. We updated to 2011-4.5.0.1050 Coma Berenicids (Win64) this morning, but are not unable to make outbound calls to external numbers. Please advise ASAP. Thanks, Randall
  14. Does anyone know what the Red "X" or Red Circle (depending on your version) next to an Account means? Thanks, Randall
  15. We've figured out our problem. My last post was simply to reply to shopcomputer the additional information we knew and thanking them for help.
  16. Thanks for the post, shopcomputer! I can map network drives with the correct user permissions, however, it is the SYSTEM account creating the CSV which does not have permission on the Active Directory domain (the PBX is not part of the domain). This is why my file isn't getting created. I thought about UNC paths, but it was not documented and not suggested by support, so didn't try them. However, I don't believe this would have made any difference with my issue - the share and NTFS permissions are still applied at the shared folder, which would still not allow the non-AD PBX to write to that location anyway. Again, thanks for taking the time to post! Randall
  17. I do have the error you're looking for - 2012/07/16 14:57:07: Could not open L:\CDRS\20120716-14.csv for writing I believe your theory about the PBX running under SYSTEM account is correct. Can we change the account the PBX runs under?
  18. I understand what it should be doing, but it's not, thus the reason I contacted support. To review what we have confirmed - In the snomPBX, Admin, Settings, Appearance, CDR URL = file:l:/cdrs/$d-$h.csv (settings provided in this post to create the CSV file) In Windows on the PBX, open Windows Explorer, can open the l:\ mapped drive, can open the "cdrs" folder, and can create files and folders in the l:\cdrs folder (this confirms the PBX has rights to create files in this drive/folder. However, there are no CSV files getting created. Are there any other settings to look into? Are there better tests I should perform to verify correct paths and permissions? I hoped this forum would be more helpful than the last post. Thanks again for your help, Randall
  19. Good morning, I have verified the CDRS folder was created on the mapped network drive, and verified the PBX has permissions to create files on the mapped network drive as well. However, we did NOT get any CDRs created all weekend. What other settings in the PBX should we check to get the CDR CSV created? Thanks, Randall
  20. Yesterday I applied the exact command provided, except changed the mapped drive letter to match my setup, but this morning found no file is getting created. What else should I look at to get this feature working? Thanks!
  21. I am attempting to setup creating of CDR to CSV format on a shared network folder. However, I'm not able to get the CDR created at all. I've reviewed the steps found in the manual and online, but still no luck. Can someone please provide me with a summary of steps to create CDR to CSV? We are running 2011-4.2.1.4025 (Win64). Thanks, Randall
  22. No NAT. Trunk is connected directly to PBX on one NIC, and a second NIC connected to the 1GB LAN. No routers in the way and I don't think it's limited bandwidth since the trunk is delivered on a 5MB Syncronous Fiber Circuit. I just confirmed there are no entries in the IP Access Control list. I did create an Allow entry for our LAN subnet. I don't think there are IP conflicts as all phones have been assigned static in a range far away from DHCP scope. How do I setup auto email on registration issues?
  23. We are having issues with various extensions not receiving inbound calls. Inbound calls, either external or internal, are immediately sent to the extensions voicemail. The phones having this issue can make outbounds calls just fine. I've updated the firmware on all of our phones, but this did not resolve the problem. Next, I researched an update for the snomONE PBX software and found we are currently running version 2011-4.2.1.4025 (Win64). When looking at the update website, I found newer version available = 2011-4.5.0.1050. I followed the instructions for the update. Immediately after the update, everything seemed to work fine on the few phones I could get my hands on and reboot - inbound and outbound calls worked. However, after about an hour or two, users reported they could not make any outbound calls, but instead received noise on the line. Shortly after that, we could receive inbound call rings, but tried to pickup the call and could not hear the callers audio. Any advise or ideas how I can handle the original issue and/or complete the PBX update successfully? Thanks for the help in advance, Randall
×
×
  • Create New...