Jump to content

Keith

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Keith

  • Rank
    Member
  1. Hi There, For various reasons, none of which were shortcomings of Snom One, we ended up switching to a hosted PBX. How do I uninstall Snom One server? I know I can turn the service off with the Admin control panel, but I'd rather not have to do that every time the computer starts up. I believe this is the version we were running: pbxctrl-darwin9.0-2011-4.5.0.1050 It's on a Mac Mini running OS X 10.6.8 Thanks in advance for any help! - Keith
  2. Hi There, I've set up Snom One (2011-4.5.0.1050 Coma Berenicids on MacOS) to work with Junction Networks service which is called "PSTN Gateway". I can call into the system and dial an extension and have clear conversations. I can call between LAN extensions and have clear conversations. I cannot however seem to dial out. I get an immediate fast busy on the extension (A Snom 821) and it says "Not Found" and the number I dialed. My provider says that in the "from" header below they need to be seeing <sip: 104@ourusername.onsip.com> as opposed to our IPPBX's local IP address. I've tried everything with the IP Replacement and Routing section but maybe I should be using custom headers to force this? Any help would be greatly appreciated. The following is part of the SIP Trace from the phone itself. Thanks! ________________________ Received from udp:192.168.0.62:5060 at 5/2/2013 17:10:06:509 (529 bytes): SIP/2.0 404 Not Found Via: SIP/2.0/UDP 192.168.0.73:3072;branch=z9hG4bK-6eejbkpmz9tf;rport=3072 From: "Keith Junction" <sip:104@192.168.0.62>;tag=nkzs623qf1 To: <sip:12065265178@192.168.0.62;user=phone>;tag=8eea6f9129 Call-ID: 2f73263cec27-m6y2g2xcx56a CSeq: 2 INVITE Contact: <sip:104@192.168.0.62:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snomONE/4.5.0.1050 Coma Berenicids Content-Length: 0
  3. I've heard similar stories as well! My hope is that we've minimized the problem to an acceptable level. Otherwise we'll have to spend the extra $$ and get a dedicated connection for our phones from a provider specializing in VOIP -- which would defeat the money-saving reason I switched to a SIP trunk. We are moving our office soon within the same building so may explore if there are competing ISP's we could switch to that can manage QoS (and maybe one that offers SIP trunking as well since then there's less finger pointing when there are problems).
  4. Thanks so much for your reply. I did try making entries into the 'SIP IP Replacement List' and was getting frustrated since it didn't seem to make any difference in what was being shown in the Logfile. Then, the system somehow fixed itself in the sense that it went back to using the internal IP address of the computer the PBX runs on (as opposed to the 127.0.0.1). Why, I have no idea -- and that bothered me because I would have to assume it could flip back again at some point. Anyway, today I remembered that you have to restart the PBX in order for those IP Replacements to take hold (Doh!) -- so I made 2 entries there telling the system to replace both the PBX PC local address with our public address as well as the same for 127.0.0.1. Looking at the logfile I can see this is working (our public IP address is now being shown instead of our internal ones) and I feel more secure about things. Thanks!
  5. Thank you so much for the reply and offer and I apologize about my late reply. We did manage to enable QoS for our PBX PC to prioritize VOIP traffic and it seems to have helped a fair bit. We now only rarely get the choppy audio and I'm guessing that's out of our control and being affected once our packets get to the WAN which we can't control (unfortunately our cable ISP, which is Comcast, can't or won't allow prioritizing one type of data over another on their connection). All we can do is make sure the VOIP packets get to the WAN first, as far as I now understand.
  6. Hoping for an easy quick fix to this as our system is currently down and folks are unhappy with me :| Here's our system setup, running on a Mac Mini behind a firewall. We have a fixed public IP and I have opened ports to allow the system and media to come through. system normally runs fine: Version: 2011-4.5.0.1050 Coma Berenicids (MacOS) Created on: Apr 2 2012 12:05:17 License Status: snom ONE free License Duration: Permanent Additional license information: Extensions: 10/10 Accounts: 25/30 Upgrade: 01 01 2013 Working Directory: /Applications/snomONE/conf MAC Addresses: ----- DNS Servers: 192.168.0.2 68.87.69.146 68.87.85.98 CDRs: Duration(4d): trunk = 26, extension = 21, ivr = 27 Calls: Total 5/0, Active 0/0 Calls SIP packet statistics: Tx: 810 Rx: 731 Emails: Successful sent: 1 Unsuccessful attempts: 0 Available file system space: -25% Uptime: 2012/10/3 10:54:41 (uptime: 0 days 00:44:34) (39329 40346-0) WAV cache: 1 Number of HTTP sessions: Sessions: PAC=0, HTTP=1; Threads: SIP=3, HTTP=1 Domain Statistics: Total Domains: 1, Total Accounts: 25 Every so often our AA will not recognize key presses of incoming callers, nor detect a hangup signal either. I spoke with our SIP Trunk provider (Braodvox) and they noticed that in our SIP header the IP address of "127.0.0.1" was showing up (which is the localhost address of the PC that our Snom One is running on). They said it should be actually be our public IP address, which is 74.94.xx.xx. Strange thing is, normally the SIP headers DO reflect our public IP number -- then suddenly it'll start referring to the "127.0.0.1" again which renders the DTMF tones unreadable to the system. Is there any way to force our public IP address to appear in the headers always? I have no idea why it suddenly changes. Here's a portion of a logfile below. Any help appreciated, thanks!! [5] 2012/10/03 10:37:33: SIP Rx udp:208.93.227.215:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-217db88908d0a4f24aaed01ad49ac87e;rport=5060;received=74.94.78.73 From: "2066392700" <sip:2066392700@208.93.227.215>;tag=595505757 To: "2066392700" <sip:2066392700@208.93.227.215>;tag=megFrK331FH4D Call-ID: bca8s0lj@pbx CSeq: 2638 REGISTER Contact: <sip:2066392700@127.0.0.1:5060;transport=udp;line=c81e728d>;+sip.instance="<urn:uuid:dc20d480-3bb1-46b7-a06c-e8f56b912c0e>";expires=30 Date: Wed, 03 Oct 2012 17:37:33 GMT User-Agent: Broadvox Fusion Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY Supported: timer, precondition, path, replaces Content-Length: 0 [5] 2012/10/03 10:37:47: Did not receive ACK, disconnecting call abf9b40b-8823-1230-7794-f04da23d7069
  7. Greetings, We're running Snom One on a MacMini in our small studio in Seattle. I am new to SIP Trunking and the deeper points of telephony, but have managed to get our system with 6 extensions and Auto Attendant doing all the fantastic things we needed like cell phone integration and VM as Email, etc. We are running it over our Comcast Business Class broadband connection (which typically clocks at over 30MBS down and 20MBS upstream and clean for packet loss and jitter). Broadvox is our SP trunk provider. Generally it all works great with the exception of the outbound audio which our callers say is often "choppy" with lots of small intermittent dropouts. Sometimes it's smooth as butter and other times close to untenable. No echo, no distortion -- just stuttered or choppy. Broadvox said they saw some serious RTP packet latency that could be the culprit. It seems to me that with the bandwidth we have and the rather straightforward network, that we should have no trouble sending out audio smoothly. Anyway, I've tried everything I know how to do and can't solve this problem so need someone knowledgeable to take a look I think. Does anyone have any 'AHA' ideas to solve the problem -- or possibly a reference to someone in the greater Seattle area that is good with SIP and Snom? Here's our system profile. (Oh, I also can't seem to figure out why we have "-25% Available File System Space". We've got tons of hard drive space available...) Thanks in advance! Version: 2011-4.5.0.1050 Coma Berenicids (MacOS) Created on: Apr 2 2012 12:05:17 License Status: snom ONE free License Duration: Permanent Additional license information: Extensions: 10/10 Accounts: 25/30 Upgrade: 01 01 2013 Working Directory: /Applications/snomONE/conf MAC Addresses: C42C032AEB58 C8BCC8E0CF02 DNS Servers: 192.168.0.2 68.87.69.146 68.87.85.98 CDRs: Duration(4d): trunk = 57, extension = 52, ivr = 64 Calls: Total 45/5, Active 0/0 Calls SIP packet statistics: Tx: 21195 Rx: 20699 Emails: Successful sent: 10 Unsuccessful attempts: 0 Available file system space: -25% Uptime: 2012/9/25 17:14:08 (uptime: 1 days 03:08:49) (41712 42817-0) WAV cache: 2 Number of HTTP sessions: Sessions: PAC=0, HTTP=1; Threads: SIP=3, HTTP=6 Domain Statistics: Total Domains: 1, Total Accounts: 25
  8. Great, thank you so much for the response. Sounds like I will be giving it a try at least. We're running the free version so I can always just re-download it if I run into any license issues. So I assume the new installation would create a whole new 'blank' directory and I would just trash that folder and replace it with a copy of the working directory we are currently using?
  9. Greetings, We are a small Graphic Design group and we will be upgrading our file server from an old G5 Xserve to a new MacMini running OS X Mountain Lion Server. This computer will typically have less than 5 users connected to it at any given time (using file sharing over AFP). It'll only be running a few services like VPN, AFP, VNC and is used almost solely as a file server with designers accessing files from it but running the applications (Like Photoshop etc) on their client machines. Our phone system consists of 5 Snom 821's. My question is threefold: 1. Is Snom ONE currently compatible with Mountain Lion Server? (We currently run 2011-4.5.0.1050 Coma Berenicids on a Mac Mini running OS 10.6.8) 2. Would there be any problem using our file server to also be the Snom One PBX server? 3. Assuming this will work, what is the easiest way to migrate our setup to the new server? Can I simply copy the whole Snom One directoty to the new machine and change the appropriate IP numbers, or...? I'm currently running Snom One on my desktop MacMini and it seems to do just fine even when I'm doing other tasks on my machine. The CPU usage graphs also seem to indicate that Snom One is using only a tiny bit of CPU horsepower. I'd prefer to have just one office server to manage and to not have to buy a dedicated computer just for the PBX. Thanks and sorry about the multi-faceted question!
  10. Interesting and thank you for the reply! I did end up rebooting all the phones and that seemed (for some reason) to solve the problem for now. I checked the MOS in the call log and we're getting all "41" which I assume really means the "4.1" you were referring to. In the next week or so I'll be upgrading our router to one that has some QoS settings so I can prioritize the SIP traffic -- within our LAN at at least. Hopefully that will help too. As far as the CDR files, in the 3 CDR* folders I can see I have a total of about 60 files in each (180 total) amounting (in total) to less than 1MB so I can't imagine that's an issue.
  11. Hi There, We're running 2011-4.5.0.1050 Coma Berenicids (MacOS) on a MacMini running Snow Leopard. I haven't changed anything in our setup and yet today customers say our phone audio is choppy with lots of dropouts. Incoming audio (while on hold with the airlines for instance) is clear and smooth. I've restarted the computer as well as out router and cable modem (but not the phones yet). Anyone have ideas on what might be causing this? Is restarting the phones a helpful troubleshooting step? One other thing I noticed is that our our system status is indicating: "Available file system space: -18%". Yet we have over 100GB available on the hard drive. I don't recall what the available system space used to indicate previously though so I am not sure if this is relevant or whether it has always been that way. Any help appreciated, thanks! - Keith
  12. That will work just fine as it appears we can still call to those extensions internally and transfer calls to them as well. You just can't reach them from the AA and the AA does not present them as options in the Dial By Name. Thanks!
  13. OK, for the meantime I can just name them something that won't match up with any of our employees. Luckily we're a small firm! Thanks.
  14. Hi All, We've got a few 'generic' extensions on our system, such as a break-room phone, that we'd prefer not appear in the auto attendant Dial By Name function. Is this as simple as not entering a First and Last Name in the extension setup? It would however be nice to have a descriptor (such as 'Breakroom') but I don't want callers who use the Dial By Name function to be able to ring that extension by pressing the letters B R E A, since if we had a Breanna in the office it would get confusing. Hopefully this makes sense...
×
×
  • Create New...