Ok, so I'm brand new to this whole 3CX thing, In fact I'm brand new to the the whole PBX and telephony thing. I'm and IT guy and figured this couldn't be that difficult, boy was I wrong. I started off with incredible pbx, but the whole linux component on top of a complicated phone system was just way over the top so I switch to 3CX, but so far I'm still having a whole host of issues, I'm not even sure where to start. One thing I've learned already is that this whole PBX system, windows or otherwirse, is extremely unforgiving.
Ok, let's start with the my setup. I'm running 3CX as a Virtual machine running Win 10 Pro with the latest uopdates on a dedicated host to which I have full control over. The VM is behind a firewall, however at the moment, to rule out anything more being the issue, I've got a dedicated IP with a 1to1 nat and have windows firewall enabled. This is temporary and since I'm actively working on this server, if by some miracle someone manages to break in, they won't get far. In any case that's my setup. This server is going to be compleatly cloud based. No local provisioning. Ok then, my problems.
1. I've got VOIP.ms as a sip provider and I got it configured in my sip trucks and I have a green light on my registration, as well as Voip.MS website reporting registered, I've got a single outbound rule on my outbound routes that does the clasic 9 prefix and VoiopMS on Route 1. All other routes are blocked. I installed the 3CX app on my phone and registered it, which went smoothly and I attempted to make a call. I get a single simple message stating "server error" and no call. What could be the problem? Where can I see some logs for this?
2. SSL_ERROR_RX_RECORD_TOO_LONG Ok, so I came across this error while attempting to configure this Cisco 7970 ( 7960) phone. Basically, it appears whenever I got to configure this phone on the webpage and re-assign the interface for provisioning from the 10.x.xx.x local ip to the public pbx.mydomain.com address. The web portal has a link to an XML file that I need to download in order to configure this phone and whenever I make that configuration change, I can no longer download the xml and instead get the SSL error.
3. And finally, my last issue, the CISCO 7970G bain of my existance ip phone. I have been trying to get this damn thing to work for weeks now and could really use some help. When I saw that 3CX automatically generaged and XML file when I selected that phone on the list I was so extatic.... but, I guess It's still not going to be that easy after all. I noticed that the 3CX web portal specifically states local registration for this phone, is that the only way this phone will ever work? locally?
Ok, let's start with the my setup. I'm running 3CX as a Virtual machine running Win 10 Pro with the latest uopdates on a dedicated host to which I have full control over. The VM is behind a firewall, however at the moment, to rule out anything more being the issue, I've got a dedicated IP with a 1to1 nat and have windows firewall enabled. This is temporary and since I'm actively working on this server, if by some miracle someone manages to break in, they won't get far. In any case that's my setup. This server is going to be compleatly cloud based. No local provisioning. Ok then, my problems.
1. I've got VOIP.ms as a sip provider and I got it configured in my sip trucks and I have a green light on my registration, as well as Voip.MS website reporting registered, I've got a single outbound rule on my outbound routes that does the clasic 9 prefix and VoiopMS on Route 1. All other routes are blocked. I installed the 3CX app on my phone and registered it, which went smoothly and I attempted to make a call. I get a single simple message stating "server error" and no call. What could be the problem? Where can I see some logs for this?
2. SSL_ERROR_RX_RECORD_TOO_LONG Ok, so I came across this error while attempting to configure this Cisco 7970 ( 7960) phone. Basically, it appears whenever I got to configure this phone on the webpage and re-assign the interface for provisioning from the 10.x.xx.x local ip to the public pbx.mydomain.com address. The web portal has a link to an XML file that I need to download in order to configure this phone and whenever I make that configuration change, I can no longer download the xml and instead get the SSL error.
3. And finally, my last issue, the CISCO 7970G bain of my existance ip phone. I have been trying to get this damn thing to work for weeks now and could really use some help. When I saw that 3CX automatically generaged and XML file when I selected that phone on the list I was so extatic.... but, I guess It's still not going to be that easy after all. I noticed that the 3CX web portal specifically states local registration for this phone, is that the only way this phone will ever work? locally?
