Carlos Montemayor
-
Posts
170 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Carlos Montemayor
-
-
Hi,
Following advice, I erased the stun thing and turned offer ICE to off (as was the default) and in the outbound proxy window of the Identity Login section I added the transport=tls and it worked! I had tried that before with no success but now I see that I had the syntax wrong. I was also spelling out the port number but now I see that I should not... <pbx public IP address>; transport=tls instead of <pbx public IP address>:5061; transport=tls
At this time I cannot call other extensions to have a conversation (for a test) but I did made a call and no error message was displayed and I could hear the voice mail message of the extension called (something I could not do before). It seems like the problem has been solved. One weird thing though. If I see the accounts list page on the pbx GUI and check the box for IP address I can see my test phone registered but it says udp:192.168.1.254:1025 and everybody elses is shown as tls:<their local address and port>. Why would that be?
Regarding Plug and Play. That snom mini has version 4.5.1 and I added the following code to the pnp.xml file that is listed on the HTML Templates section of the pbx GUI
<file name="snom_710.xml" encoding="xml">
<pattern>snom710.htm</pattern>
<vendor>snom</vendor>
<anonymous>true</anonymous>
<protocol>tftp,http,https</protocol>
<pnp-vendor>snom</pnp-vendor>
<pnp-model>snom710</pnp-model>
<pnp-version>^[78]</pnp-version>
<pnp-content-type>application/url</pnp-content-type>
<pnp-url>{https-url}/snom710.htm</pnp-url>
</file>
I was able to do plug and play of the 710 phones in the local network using multicast for the first batch of phones that I installed originally over there. I have not been able yet to do it manually for WAN based plug and play for the remote users. I believed that it was because a port forwarding for port 80 is needed in the local router so that the remote phone can find and reach the pbx, but now I wonder if I am missing something else, like another bit of code for the pnp.xml file or some other file. Am I?
Regards
Well if you use STUN then you obviously also use UDP--both a bad idea. Your router probably messes with SIP packets which is causing such hard to track problems. The easiest is to use plug and play, because that will set the phone up to use TLS and also sets also other important parameters so that the number of problems is minimized. If you can't use PnP (4.5 does not support snom 710 yet), then at least use TLS transport layer. This way you don't need STUN (there is a permanent TCP connection anyway) and the router cannot change the packets.
-
Hi
Thaks for answering. I just did a restore to factory defaults and a reboot (just to be dobule sure with that). Problem persists.
Out of desperation, I tried changing the parameters in the NAT region of the phone. I changed to "offer ICE" to on and added a stun server with an interval of 15 seconds and a keep alive of 10 and that did the trick.
I have been reading here in the forum that such a thing is a very last resort kind of option. So, I tried a Manual WAN Plug and Play. Unfortunately that did not work and I assume that such a thing did not work because we need to do first a port forwarding for the http port of the pbx.
I do not have control of the firewall (which is run by a Cyberoam) so I cannot do the port forwarding myself. As soon as the IT guys of the customer give me a green flag, I will attempt the Manual WAN based plug and play again, which hopefuly will be a cleaner and more reliable solution.
In the meantime, is there a guideline regarding how many seconds to use in the STUN interval and the keepalive?
Regards,
-
Hi,
I just came across to a new problem. A remote user is unable to call to other extensions.He can make calls outside the system (trunk calls), he can also receive calls from other extensions, but he cannot call other extensions. The pbx is a snom mini running 4.5.1 and the phone is a snom 710 with the latest firmware(8.7.3.19). Everything else is working fine. The weird thing is that two remote extensions that they have on softphones over iPhones do work properly in every scenario. The error message that thesnom 710 display when dialing an extension is: "Network failure: XXX" (whereXXX is the extension dialed).
I do notknow where to make adjustments. The phone is registered and can do every other thing. Just placing a call to an extension is what it cannot do. Has any one encountered this? What can I do to solve this?
Regards
-
Hi
Mine just arrived and looks exactly as I was anticipating. Sturdy, compact, well ventilated and yet something that could be "presentable". I will start assembly asap. One interesting thing is that it comes with a couple of USB ports that are hiding behind the front cap. This last feature makes me wonder a couple of things. First, if it is posible to make run an appliance without an internal hard disk, just with a USB Flash memory (in other words, if I could make a Linux installation there), and second, if it is technically possible, if it would be reliable enough. I mean, I know how prone to failure are hard disks, I have had my share of problems with them, but I do not have a feeling yet for usb flash memories, I have not used them that much.
Can someone (or snomeone) shed some light on this idea?
Regards,
-
Hi
I did and it looks very promissing. I already installed a group of programs called: "WAMP" that, for what I gather, should work with JSON. The only problema is that all that is just too new for me and I have not been able to make it work yet, but I will not give up.
Regards,
-
Well, the one that seems closer to what I am looking for (so far at least) is called: "Advanced PBX Data Logger". It is collecting data, although I am getting two lines for each call. (as if it were seeing a CR LF where there is none). Also, it seems to be missing some important fields, like trunk number and call direction. I will ask the developer for help, of course (aggsoft). However, if someone has had success with other software, it will be good to know.
Cheers
Hi,
I am having trouble finding a software tool that Works. I am deploying the pbxs in remote locations and it would make sense to collect CDR using the simple TCP connection. Any suggestions as of a software to collect those CDRs?
Regards
-
Hi,
I am having trouble finding a software tool that Works. I am deploying the pbxs in remote locations and it would make sense to collect CDR using the simple TCP connection. Any suggestions as of a software to collect those CDRs?
Regards
-
Hi,
I am glad that you brought out this topic. I have been looking for solutions and have already tried a couple that I can share. I already checked the MB-D38 that appears on the following webpage: http://www.ewayco.com/100-low-cost-pc-products-low-cost-systems-embedded-systems-servers-lcd-pc-panel-pc.html I added a 2.5" 32G SSD and 2G of DDR3 RAMto round it up and it does work. Its pros are: It does work, Debian Linux 64 bits runs there with no problems, its small form factor. Its cons, at least to me are: Coming from China to my country, some 45% of cost is shipping and duties. Although it is Atom based, it does have a couple of small fans which in such a reduced form factor makes the solution a bit noisy, which may not be important in some sites, but it may be a problem in others. Something that I do not know if it is a con or a pro, but that grabbed my attention, is that the chassis appears to be made of thick caliber steel. It would not surprise met hat it could stop a bullet. I also tried assembling a pc myself. All the needed parts are available in my town, exception made of a small good looking chassis and corresponding power supply.The closest chassis that I found was a slim mid tower unit. Not so cool looking, but the unit worked and was affordable. That partial success encouraged me to a next project. Import just the chassis and PSU and find everything else at home. The chassis that I will try next is the M350 http://www.mini-box.com/M350-universal-mini-itx-enclosure I will let you guys know. The chassis is still somewhere on the road.
Cheers!
-
Hi,
Thanks for answering. This setup was not an upgrade. I mean. I have used the SIP provider in a different equipment (a couple of snom minis, versión 4.5.1) and it worked fine, and in a completly new installation, I had this problem using 5.0.6
Because I was rather under preassure, I tried several times and at last I hit success. What I did was to upgrade to versión 5.0.8 and then I rebooted the system. After a while (it took serveral minutes) the trunks started to register, although I was not so sure because I was not able to read the coveted "200 OK" message. What I was able to read was something like "refresh after 1800 seconds" or something like it. Several minutes after that, I was able to read the 200 OK.
One Little mistery remains though . One of the accounts toggles between 603 Decline and 200 OK. Every other account (which have the same configuration) are 200 OK steady. This particular SIP provider does B2B. I will PM you with the details and follow your instructions.
Thanks!
-
Hi,
I used to be able to register trunks with a SIP provider using version 4.5 (snom mini). Now that I am using 5.0 I am not able to register the very same trunk. What could be happening?
-
Hi!
It is good to have friends with different skills and backgrounds. Sombody helped me doing the linux stuff and it worked just fine. I am not sure what do you mean by pushing something into the phone, but I did a power cycle and the phone did not attempt to do the firmware download again. It only did it once, and not again. The only weird message was "Download Language Failed", but that is something that has appeared in other phones and I just disregard it and the phone works fine.
So, go for 4.5.1 It seems to be working fine.
Cheers!
By default the html folder is not created on new installs, you have to create the html directory, the same with the tftp directory.
-
Thanks for the advice. I am attempting to create the file snom_710.xml at this very moment. However, I am not finding the right folder. I was able to get to /usr/local/snomONE/ however, the html folder that should be under snomONE is simply not there, it should be between hoots and hunts and it is just not listed. Is it in a different place in my 4.5.1 verision?
Help is, as always, very appreciate it.
Regards
_
Carlos, you can clear the message and keep on making calls but if you push something to the phone where it needs to reboot then it will also download the 8.7.3.19 firmware again....even if the firmware on the phone is already at 8.7.3.19.
Maybe with your PBX ver 4.5.1 you might not run into this, snomone said with his snom 710 and PBX ver 5 he doesn't get this error message
Let us know if you get that error message on your ver 4.5.1 (that ver was put out by Vodia). I don't think you will get the error message.
-
Thanks for the advice. I am not afraid of work and if the only problem can be a harmless message, I will just disregard it, tell the users not to worry about it either and keep on making calls.
Regards!
-
Hi,
I am about to deploy some 18 snom 710s as extensions of a snom one mini already running version 4.5.1 in a nearby city. Should I attempt to do pnp or should I leave it alone and just point the 710s towards the pbx as if they were a non pnp capable phones?
Regards,
We also saw the message "SW update failed" in version 5. This seems to be some strange bug in the phone. I cannot even guarantee that after you upgrade to V5 this message will disappear. It seems that 7.3.19 is still the latest & greatest version, hopefully those strange messages will disappear in the next version. The phone on my desk (a 710 :-)) made it and the SW update message is not there any more.
-
Hi,
What would be the third party limitation on the snom mini on version 4.5.1? Is it just like the yellow or is it a different number?
regards,
With yellow you can register extensions; we recenty changed the third party registration policy, so you are able to register 20 phones e.g. from Aastra. However these devices are not provisioned automatically by snom ONE, and also the support is limited to the forum. With blue there is no limitation for the number of extensions.
-
New problem. After sucessfully upgrading a few SoHos I found a new roadblock. The last SoHo returned the following error message after tha last step which is restaring
Starting snom ONE daemon./pbxctrl: /usr/lib/libstdc++.so.6: version `CXXABI_ARM_1.3.3' not found (required by ./pbxctrl)
The unit still responds to SSH but not to the GUI
Am I missing a file or what could have gone wrong?
Regards
-
Hi,
Interesting point. Using the DNS of the ISP provider is something that had not occurred to me. Currently the DNS used are the public google ones and it could very well be something giving trouble.
I will take a look on that
Thanks!
One thing to watch out for: I've read on various blogs/forums that some ISPs try to force their customers to use the ISP's DNS servers. AT&T U-verse is apparently notorious for this. While there are workarounds for these situations, LAN problems will arise if the router's connection to the ISP is reset, if great care is not taken when configuring the workaround.
-
Hi,
Well, currently I can connect remotely and manage the system. Unfortunately, I do not have control over the router/firewall, that is under the end customer control who unfortunately does not have a very knowledeble systems guy. Nevertheless, I have just conntacted the vendor that supplyed the UTM (the cyberoam that is the router with firewall) and he offered to help. I am asking him to have a look over that device log.
I will come back with the info.
Thanks and regards
You have a remote connection issue, but you have yet to say anything about your firewall log. Do you see the connection going to the snomONE and then out the snomONE to your remote computer?
Is anything changed from the network point of view in your location?
-
Hi
Thanks for the tip. However, the problem does not seem to come from that angle. Now that I was able to bring the original snom mini home, to my amazement, I was able to see and navigate through the web GUI with no problem. I then made a fast review of its configuration and the one thing that grabbed my attention was its IP address configuration, it was the following:
DHCP: No
IP Address: 192.168.1.253
Net Mask: 255.255.255.0
Gateway: 192.168.1.254
DNS Domain: 192.168.1.254
DNS1: 192.168.1.254
DNS2: 192.168.1.254
DNS3:
I do not know if that configuration can cause problems with some local networks. However, the configuration that I left this saturday on the mini that replaced the original is:
DHCP: No
IP Address: 192.168.1.253
Net Mask 255.255.255.0
Gateway: 192.168.1.254
DNS Domain:
DNS1: 8.8.8.8
DNS2 8.8.4.4
DNS3:
I have dobuts regarding how one should configure this particular settings. However, what does make sense to me, is that if DNS is not set correctly, one should expect trouble having a browser resolve a web page address, in this case, the configuration page of the device. What is the best practice to configure the DNS settings?
Moreover, what puzzles me, is that the file that I used to do a system restore, was no other that the last configuration that I had there that worked. So I do not know why it worked before and then it did not later.
The router over there is a UTM (Unified Threat Management) Cyberoam. It seems to me that such a thing blocked the snom mini GUI as if it were a forbidden web page. Although those things are supposed to block external content, not internal ones and it had been working before. Well, what do I know.
Advice, suggestions, comments are most wellcomed
Regards,
-
Hi,
I just was granted access to the customer premise. Fortunately, I do have access to the device through SSH. It was port 22 the good one. I got confused because when I had received the original device it was port 8722, it must have changed due to a firmware update.
Now then. As per Mr. X recommendation, I reviewed the folders under snomONE and found the following:
accesslist cdre expired-1399.txt orbits schedules
acds cdri expired-779.txt outbounds spool
adrbook cdrt extensions pbxctrl srvflags
attendants certificates generated pbxctrl-old trunks
audio_de clean.sh hoots pbx.xml user_alias
audio_en colines hunts pnp_parms users
audio_moh conferences ivrnodes rates webpages
audio_sp dial_plan login recordings wipers
button_lists dial_plan_entry messages registrations
buttons domain_alias mohs reset-button.sh
callingcards domains mutex.txt restore
I do not see an access folder. The closest in name is accesslist. I entered it and found the following:
1.xml 2.xml 3.xml 4.xml index.txt
That was about it.
As per the behaviour of the device. It has been working. However, some calls are beeing dropped when transfered and there have been some no audio calls (before the incident there was not a single one occurrance).
What could be the next recommendation?
Regards
-
Hi,
I recentlytried to make a backup of a SoHo system using SSH (through putty,
an SSH, Telnet and Rlogin client for windows). I was able to get as far as creating
the file. However, I could not go any further because the new file had used up all
the available free memory that was there in the system.
I understand that this device has little space by nature and that if there is
need or want for call recording or more than a little voice mail, one should
look for a different setup. I, for instance, configure the SoHo systems that I deliver
with short time parameters for call recording, cdr storage and such and I do
not tell the end users that there is call recording capability at all. However,
there are some very basic and crucial maintenance duties that should be
performed, like backing up the system and being able to restore it and those
require memory.So, please,could we get a step by step procedure to perform these needed duties
on a SoHo? By step by step I mean an algorithm or a guide “for the rest of us” (field
people that are not IT guys and much less know anything about Debian Linux).
I know thatwhat I am asking for is going to take effort, but I assure you
that it will save many headaches and will allow us to put more snom products in the field.
In short,the 3 very basic algorithms (or step by step procedures if you like) that I askfor are:
1. Enabling a USB memory stick to makespace available for the SoHo system to use.
2. Making a system backup that woulduse precisely the memory created in the previous procedure.
3. Making a system restore from thebackup stored if, Heavens forbid, a disaster strikes.
I will be much obliged and pledge that if thispetition is granted I will promote snom products in my market.
Thanks in advance.
-
I will go there tomorrow morning to try SSH with port 22. That is certainly a good idea. I am sure I did not changed it and I know that I had been able to enter with 8722. However, several things happened this morning that were not suppoused to like reverting to the default user and password in the GUI after the power cycle. If those things went to default by themselves, that port could have gone to default as well.
Thanks for the advice. I will attempt that tomorrow.
-
That was the port that I had used. That was not the problem.
Thanks for answering.
-
No, I could not use SHH. I got a message "Connection refused". At home, I was working with my desktop pc when all these things developed. Now that I am at the customer premise, I am using my laptop. I could not get access with neither of those and here at the customer premise I tried the SSH with said: "connection refused".
The good thing, is that the users are able to place calls, but I feel "naked" since now I cannot make any adjustments in the system.
:-(
Suitable Hardware
in PBX Lounge
Posted
Hi,
I just built the first unit using the 350 as the chassis, an Atom D2500 as the core. and a small SSD for storage. It is exactly what I was anticipating. Does the job, looks presentable, it is affordable and allows you to say the catchy phrase: All solid state, no moving parts.
Now then. Here at my hometown I could also get (for about the same price) an ECS NM-70 I2 mother board that has a Celeron dual core 847 processor (same form factor). It would be more speed everywhere (processor, RAM and even access to the hard drive). Being price about "equal" the pros and cons I see are the following: In favor of the Atom; 1) Three years warranty as opposed to only one, 2) Fan-less processor (one less thing that could go wrong) and in favor of the Celeron: 1) Raw speed (The processor scores 1042 against 407 on pass-mark benchmark, RAM runs at 1333 MHz as opposed to 1066 and Access to the SSD is at 6 Gb per second instead of only 3)
Being cost practically the same, it is only a thing of valuing reliability against speed. One way of thinking would be that since electronic parts tend to either fail pretty soon or last for years, perhaps I should favor the faster solution and stress test the units before sending them to a final user. The other way of thinking would be to use the Atom for users without plans for growth and the Celeron for the ones that are either large already or have plans for growth. The problem here is that I do not have an idea of how many concurrent calls would each system be able to handle.
I would appreciate your thoughts and insights.