shigeru
-
Posts
39 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by shigeru
-
-
No the placement seems to be correct.
I am sure you have checked it, but just to be sure, please check if your changes are still there in pnp.xml when you restart the system.
And you do make these changes in the customize page in the domain by selecting the pnp.xml file, changing it, saving it and restarting the pbx in the services?
I just repeated the process and in the browser I get the correct output when I add those lines in the pnp.xml. But if I remove them I get file not found.
In the browser, do you use:
https://[yourdomain]/prov/snom_870_buttons.xml?model=snom870
[yourdomain] of course needs to be replaced by your ip or domain name.
If it asks for certificate, you can add a temporary exception and in login/pass, give the login and pass of your first extension in the domain.
Until it returns the right file here, the phone won't get it either.
For further test, to see if you get any file from the system at all try:
http://[yourdomain]/prov/snom870.htm
It should return the next batch of files the phone should get. You can also copy and paste the buttons entry from here to try in the browser.
I hope this helps.
Thank you.
I have confirmed that the addition is present over reboots. Also when I check the snom870.htm I get the following, which I believe is how it should be including the "snom_870_buttons.xml?model=snom870" portion.;
<?xml version="1.0" encoding="utf-8"?> <setting-files> <file url="http://192.168.x.x:80/prov/snom_3xx_fw.xml?model=snom870" /> <file url="https://192.168.x.x:443/prov/snom_3xx_phone.xml?model=snom870" /> <file url="https://192.168.x.x:443/prov/snom_870_buttons.xml?model=snom870" /> <file url="https://192.168.x.x:443/prov/snom_web_lang.xml?model=snom870" /> <file url="https://192.168.x.x:443/prov/snom_gui_lang.xml?model=snom870" /> </setting-files>
However querying URL https://192.168.x.x:443/prov/snom_870_buttons.xml?model=snom870 continue to yield the following.
<html><head> <title>Error</title> </head><body> <h1>File snom_870_buttons.xml not found</h1> <b></b> <p>Please ask your system administrator to check the log file.</p> </body></html>
Any more suggestion? Thanks.
-
As I have mentioned earlier, I have made configuration according to the WiKi page you have provided, just for the convenience sake to include in this posting system, I have copied the text version, as the snapshots of the web browser rendering will most likely cut the parameter inputs by the size of its text field and also will get messy as I have to cover the privacy related information in the image.
Thanks.
-
I am sorry, there was a slight problem with the 8 series phones. The next version will take care of that.
In the mean time can you add the lines below in the pnp.xml file and save and then restart the pbx.
<file name="snom_870_buttons.xml" encoding="xml">
<pattern>snom_870_buttons.xml</pattern>
<vendor>snom</vendor>
<protocol>https</protocol>
</file>
That should deliver the right file.
Thanks.
I have added to the end of the pnp.xml as shown below, then restarted...
<file name="yealink_common.txt" encoding="ascii"> <pattern>y############.cfg</pattern> <vendor>Yealink</vendor> <model>T28</model> <pnp-vendor>Yealink</pnp-vendor> <pnp-url>{http-url}</pnp-url> <pnp-content-type>application/url</pnp-content-type> <parameter name="protocol_type"> <display>Protocol Type (HTTP, TFTP)</display> <value>HTTP</value> </parameter> <parameter name="yealink_firmware"> <display>Firmware version</display> <value>2.41.0.27.rom</value> </parameter> </file> <file name="yealink_mac.txt" encoding="ascii"> <pattern>0015########.cfg</pattern> <vendor>Yealink</vendor> <model>T28</model> </file> <file name="snom_870_buttons.xml" encoding="xml"> <pattern>snom_870_buttons.xml</pattern> <vendor>snom</vendor> <protocol>https</protocol> </file> </plug-and-play>But it did not produce any new file in the generated folder nor the button settings provisioned as intended.
Also the access to the provision information via browser returned the same response as before, basically the modification to pnp.xml made no change. Did I put those snippets at the wrong place?
-
Before anything else, can you tell me why you don't use the simplified way of just selected the snom870 in domain buttons and make your selections on those buttons so that they are delivered to the snom870? Have I missed something where it is necessary to do it the way you did? The reason I ask is that we have really simplified the process I wanted to know what that process does not cover.
Thanks.
Yes, I did in the way you suggested. But then it is rather troublesome to take a screenshot, modify the image to protect privacy, then attach it to this post. So after I did the setting saved, I switched to the text mode and copied those text into the post and took out the privacy portion. Hope this make sense to you.
Regards,
-
When you access it through the web browser, make sure that you include the /prov behind the server name. Also, and probably much easier, you can just take a look into the "generated" folder what the PBX has generated for the phone without the need to tweak your browser...
I have put the URL (https://xx.xx.xx.xx/prov/snom_870_buttons.xml?model=snom870) as you have suggested and have got this as response. And there is no file named "snom_870_buttons.xml" in generated folder and there was not.
<html><head> <title>Error</title> </head><body> <h1>File snom_870_buttons.xml not found</h1> <b></b> <p>Please ask your system administrator to check the log file.</p> </body></html>
Any suggestions? Thank you.
-
I have setup the snom870 phone button customization for the domain as below;
1;flag;62;24/7 2;speed;*92;Black List 3;url;{https-url tftp}/snom870-cam-frontHD.xml;Front Cam 4;blf;xx;xxxxxxxx 5;blf;xx;xxxxxxxx 6;blf;xx;xxxxxxxx 7;blf;xx;xxxxxxxx 8;blf;xx;xxxxxxxx 9;blf;xx;xxxxxxxx 10;speed;xxxxxxxxxxx;xxxxxxxxxx 11;speed;xxxxxxxxxxx;xxxxxxxxxx 12;speed;xxxxxxxxxxx;xxxxxxxxxx 13;park;66;Orbit 1 14;park;67;Orbit 2 15;url;{https-url tftp}/snom870-cam-frontHD-snap.xml;Pseudo VideoHowever if I access the actual URL for the provision setting XML (https://xx.xx.xx.xx/snom_870_buttons.xml?model=snom870), I get the following;
<?xml version="1.0" encoding="utf-8"?> <functionKeys> <fkey idx="0" context="active" perm="RW">{button 1}</fkey> <fkey idx="1" context="active" perm="RW">{button 2}</fkey> <fkey idx="2" context="active" perm="RW">{button 3}</fkey> <fkey idx="3" context="active" perm="RW">{button 4}</fkey> <fkey idx="4" context="active" perm="RW">{button 5}</fkey> <fkey idx="5" context="active" perm="RW">{button 6}</fkey> <fkey idx="6" context="active" perm="RW">{button 7}</fkey> <fkey idx="7" context="active" perm="RW">{button 8}</fkey> <fkey idx="8" context="active" perm="RW">{button 9}</fkey> <fkey idx="9" context="active" perm="RW">{button 10}</fkey> <fkey idx="10" context="active" perm="RW">{button 11}</fkey> <fkey idx="11" context="active" perm="RW">{button 12}</fkey> <fkey idx="12" context="active" perm="RW">{button 13}</fkey> <fkey idx="13" context="active" perm="RW">{button 14}</fkey> <fkey idx="14" context="active" perm="RW">{button 15}</fkey> <fkey idx="15" context="active" perm="RW">{button 16}</fkey> <fkey idx="16" context="active" perm="RW">{button 17}</fkey> <fkey idx="17" context="active" perm="RW">{button 18}</fkey> <fkey idx="18" context="active" perm="RW">{button 19}</fkey> <fkey idx="19" context="active" perm="RW">{button 20}</fkey> <fkey idx="20" context="active" perm="RW">{button 21}</fkey> <fkey idx="21" context="active" perm="RW">{button 22}</fkey> <fkey idx="22" context="active" perm="RW">{button 23}</fkey> <fkey idx="23" context="active" perm="RW">{button 24}</fkey> <fkey idx="24" context="active" perm="RW">{button 25}</fkey> <fkey idx="25" context="active" perm="RW">{button 26}</fkey> <fkey idx="26" context="active" perm="RW">{button 27}</fkey> <fkey idx="27" context="active" perm="RW">{button 28}</fkey> <fkey idx="28" context="active" perm="RW">{button 29}</fkey> <fkey idx="29" context="active" perm="RW">{button 30}</fkey> <fkey idx="30" context="active" perm="RW">{button 31}</fkey> <fkey idx="31" context="active" perm="RW">{button 32}</fkey> <fkey idx="32" context="active" perm="RW">{button 33}</fkey> <fkey idx="33" context="active" perm="RW">{button 34}</fkey> <fkey idx="34" context="active" perm="RW">{button 35}</fkey> <fkey idx="35" context="active" perm="RW">{button 36}</fkey> <fkey idx="36" context="active" perm="RW">{button 37}</fkey> <fkey idx="37" context="active" perm="RW">{button 38}</fkey> <fkey idx="38" context="active" perm="RW">{button 39}</fkey> <fkey idx="39" context="active" perm="RW">{button 40}</fkey> <fkey idx="40" context="active" perm="RW">{button 41}</fkey> <fkey idx="41" context="active" perm="RW">{button 42}</fkey> <fkey idx="42" context="active" perm="RW">{button 43}</fkey> <fkey idx="43" context="active" perm="RW">{button 44}</fkey> <fkey idx="44" context="active" perm="RW">{button 45}</fkey> <fkey idx="45" context="active" perm="RW">{button 46}</fkey> <fkey idx="46" context="active" perm="RW">{button 47}</fkey> <fkey idx="47" context="active" perm="RW">{button 48}</fkey> <fkey idx="48" context="active" perm="RW">{button 49}</fkey> <fkey idx="49" context="active" perm="RW">{button 50}</fkey> <fkey idx="50" context="active" perm="RW">{button 51}</fkey> <fkey idx="51" context="active" perm="RW">{button 52}</fkey> <fkey idx="52" context="active" perm="RW">{button 53}</fkey> <fkey idx="53" context="active" perm="RW">{button 54}</fkey> <fkey idx="54" context="active" perm="RW">{button 55}</fkey> <fkey idx="55" context="active" perm="RW">{button 56}</fkey> <fkey idx="56" context="active" perm="RW">{button 57}</fkey> <fkey idx="57" context="active" perm="RW">{button 58}</fkey> <fkey idx="58" context="active" perm="RW">{button 59}</fkey> <fkey idx="59" context="active" perm="RW">{button 60}</fkey> <fkey idx="60" context="active" perm="RW">{button 61}</fkey> <fkey idx="61" context="active" perm="RW">{button 62}</fkey> <fkey idx="62" context="active" perm="RW">{button 63}</fkey> <fkey idx="63" context="active" perm="RW">{button 64}</fkey> <fkey idx="64" context="active" perm="RW">{button 65}</fkey> <fkey idx="65" context="active" perm="RW">{button 66}</fkey> <fkey idx="66" context="active" perm="RW">{button 67}</fkey> <fkey idx="67" context="active" perm="RW">{button 68}</fkey> <fkey idx="68" context="active" perm="RW">{button 69}</fkey> <fkey idx="69" context="active" perm="RW">{button 70}</fkey> <fkey idx="70" context="active" perm="RW">{button 71}</fkey> <fkey idx="71" context="active" perm="RW">{button 72}</fkey> <fkey idx="72" context="active" perm="RW">{button 73}</fkey> <fkey idx="73" context="active" perm="RW">{button 74}</fkey> <fkey idx="74" context="active" perm="RW">{button 75}</fkey> <fkey idx="75" context="active" perm="RW">{button 76}</fkey> <fkey idx="76" context="active" perm="RW">{button 77}</fkey> <fkey idx="77" context="active" perm="RW">{button 78}</fkey> <fkey idx="78" context="active" perm="RW">{button 79}</fkey> <fkey idx="79" context="active" perm="RW">{button 80}</fkey> <fkey idx="80" context="active" perm="RW">{button 81}</fkey> <fkey idx="81" context="active" perm="RW">{button 82}</fkey> <fkey idx="82" context="active" perm="RW">{button 83}</fkey> <fkey idx="83" context="active" perm="RW">{button 84}</fkey> <fkey idx="84" context="active" perm="RW">{button 85}</fkey> <fkey idx="85" context="active" perm="RW">{button 86}</fkey> <fkey idx="86" context="active" perm="RW">{button 87}</fkey> <fkey idx="87" context="active" perm="RW">{button 88}</fkey> <fkey idx="88" context="active" perm="RW">{button 89}</fkey> <fkey idx="89" context="active" perm="RW">{button 90}</fkey> <fkey idx="90" context="active" perm="RW">{button 91}</fkey> <fkey idx="91" context="active" perm="RW">{button 92}</fkey> <fkey idx="92" context="active" perm="RW">{button 93}</fkey> <fkey idx="93" context="active" perm="RW">{button 94}</fkey> <fkey idx="94" context="active" perm="RW">{button 95}</fkey> <fkey idx="95" context="active" perm="RW">{button 96}</fkey> <fkey idx="96" context="active" perm="RW">{button 97}</fkey> <fkey idx="97" context="active" perm="RW">{button 98}</fkey> <fkey idx="98" context="active" perm="RW">{button 99}</fkey> <fkey idx="99" context="active" perm="RW">{button 100}</fkey> <fkey idx="100" context="active" perm="RW">{button 101}</fkey> <fkey idx="101" context="active" perm="RW">{button 102}</fkey> <fkey idx="102" context="active" perm="RW">{button 103}</fkey> <fkey idx="103" context="active" perm="RW">{button 104}</fkey> <fkey idx="104" context="active" perm="RW">{button 105}</fkey> <fkey idx="105" context="active" perm="RW">{button 106}</fkey> <fkey idx="106" context="active" perm="RW">{button 107}</fkey> <fkey idx="107" context="active" perm="RW">{button 108}</fkey> <fkey idx="108" context="active" perm="RW">{button 109}</fkey> <fkey idx="109" context="active" perm="RW">{button 110}</fkey> <fkey idx="110" context="active" perm="RW">{button 111}</fkey> <fkey idx="111" context="active" perm="RW">{button 112}</fkey> <fkey idx="112" context="active" perm="RW">{button 113}</fkey> <fkey idx="113" context="active" perm="RW">{button 114}</fkey> <fkey idx="114" context="active" perm="RW">{button 115}</fkey> <fkey idx="115" context="active" perm="RW">{button 116}</fkey> <fkey idx="116" context="active" perm="RW">{button 117}</fkey> <fkey idx="117" context="active" perm="RW">{button 118}</fkey> <fkey idx="118" context="active" perm="RW">{button 119}</fkey> <fkey idx="119" context="active" perm="RW">{button 120}</fkey> <fkey idx="120" context="active" perm="RW">{button 121}</fkey> <fkey idx="121" context="active" perm="RW">{button 122}</fkey> <fkey idx="122" context="active" perm="RW">{button 123}</fkey> <fkey idx="123" context="active" perm="RW">{button 124}</fkey> <fkey idx="124" context="active" perm="RW">{button 125}</fkey> <fkey idx="125" context="active" perm="RW">{button 126}</fkey> <fkey idx="126" context="active" perm="RW">{button 127}</fkey> <fkey idx="127" context="active" perm="RW">{button 128}</fkey> <fkey idx="128" context="active" perm="RW">{button 129}</fkey> <fkey idx="129" context="active" perm="RW">{button 130}</fkey> <fkey idx="130" context="active" perm="RW">{button 131}</fkey> <fkey idx="131" context="active" perm="RW">{button 132}</fkey> <fkey idx="132" context="active" perm="RW">{button 133}</fkey> <fkey idx="133" context="active" perm="RW">{button 134}</fkey> <fkey idx="134" context="active" perm="RW">{button 135}</fkey> <fkey idx="135" context="active" perm="RW">{button 136}</fkey> <fkey idx="136" context="active" perm="RW">{button 137}</fkey> <fkey idx="137" context="active" perm="RW">{button 138}</fkey> </functionKeys>Above customization is done to the Domain wide, though. Any ideas? Thanks.
Version: 5.0.3 (CentOS64) Created on: Dec 14 2012 14:28:41 License Status: snom ONE free
-
There is no "exhaustive" list. It all depends on the port settings in the PBX. But anyway because this is of general interest, here is a summary:
- SIP: Here you may have zero, one or more UDP, zero, one or more TCP or TLS ports. The port numbers are set in the web interface of the PBX. Ports may be bound to IPv4 and IPv6 addresses. By default, they are bound to both. Default is 5060 for UDP, 5060 and 5061 for TCP/TLS.
- HTTP: Here you may have zero, one or more TCP or TLS ports. The port numbers are set in the web interface of the PBX. Ports may be bound to IPv4 and IPv6 addresses. By default, they are bound to both. Default is 80 and 443.
- TFTP: Here you may have zero, one or more UDP ports. The port numbers are set in the web interface of the PBX. The default port is 69 (both for IPv4 and IPv6)
- SNMP: Here you may have zero, one or more UDP ports. The port numbers are set in the web interface of the PBX. The default port is 161 (both for IPv4 and IPv6)
- NTP: Here you may have zero, one or more UDP ports. The port numbers are set in the web interface of the PBX. The default is no port.
- LDAP: Here you may have zero, one or more TCP ports. The port numbers are set in the web interface of the PBX. The default port is 389 (both for IPv4 and IPv6)
- RTP: Here you have to specify a port range. Default is 49152 to 65535. If you want to lower the risk that other (potentially malicious) applications grab traffic from those ports, you should make the port range shorter; but for every call that you want to run on the system you must have at least 4 ports available. For example, if your system should be able to support 10 concurrent calls, you need to have at least 40 ports in that range.
What you just mentioned above is covered by the list of ports I have posted initially, right?
-
There is "agent login/logout" which deals with the availability to receive calls from ACD. If you want a general login/logout, most people just use DND (Do Not Disturb).
Also there is hot desking, where customers can redirect all traffic on an extension to a physical location.
http://wiki.snomone.com/index.php?title=Call_Forwarding
Re-provisioning phones every morning does not sound like a solution to me.
Does this method require to have license for extensions for the total of the addition of the number of phone and number of users?
-
In newer versions of iptables, you can actually use a owner rule: Try "iptables -m owner --help" to see if that is available on your system.
Unfortunately that option only applies to OUTPUT and not INPUT. I do not have any OUTPUT restrictions on my iptables setting for now. Also in order to use this rule for OUTPUT restrictions, I will have to make a dedicated user for snomONE, which is a securer practice than what snomONE installer does. It still does not solve the issue with INPUT.
Do you really not have an actual exhaustive list of the ports used by snomONE?
Thank you.
-
Hello!
I have been checking out the snomONE wiki about a way to setup snom VoIP phones in such a way that when a user comes to the day's desk he/she logs into a phone and get his/her extension assigned to the phone until he/she logs out. Would such a configuration possible. As far as I can figure, it is not an available option in settings.
If not, could you add this feature in the near future?
Thanks.
-
Well, there are server ports and there are client ports. For server ports, having SIP (UDP/TCP/TLS) and HTTP (TCP/TLS), possibly TFTP (UDP) and maybe even SNMP (UDP) should be sufficient. Client ports like the DNS client can actually take random numbers.
RTP is somewhat different first of all because it is a server port and you must specify a port range there. RTP is difficult to track down with netstat, but I don't think that we are trying to hide port numbers here. http://wiki.snomone.com/index.php?title=Ports has some information what the ports are actually doing. OF course the protocols itself are described in the RFC, we don't want to repeat that in the Wiki.
BTW in Windows it seems to be easier to control the firewall, all you need to say there "trust that application". Not sure if there is a equivalent for CentOS/iptables.
Would not the ports I listed in the first post covers all the server ports you mentioned?
I am suspecting that the above listed ports does not cover all the required ports for snomONE to properly operate, as it failed to provide area of snomONE functions especially around PnP provisioning in my case. So once again, I am asking for the exhaustive list of the server ports that snomONE truly requires for its full operation.
Thanks.
-
We had the same problem with out test installation. There is documentation available for CentOS firewall, e.g. http://wiki.centos.org/HowTos/Network/IPTables iptables is very powerful, but could be easier to use...
You can also use netstat to check which port the pbxctrl process has opened. RTP ports are opened on demand, so make sure that you also list them there.
Thank you for pointing to the documents regarding to IPTables, but what I am looking for and the reason I have posted is to know what are the real set of ports snomONE requires. They definitely are more than what snomONE's somewhat outdated and broken WIKI documentation (http://wiki.snomone.com/) has been suggesting.
Do you mean that you are not aware of any other ports used by snomONE other than I have listed? Could you share snomONE's real network requirements specification?
Thanks.
Version: 5.0.3 (CentOS64) Created on: Dec 14 2012 14:28:41 License Status: snom ONE free
-
Hello!
I have installed and trying to setup snomONE 5.0.3 on CentOS 6.3. I have installed CentOS with;
CentOS-6.3-x86_64-netinstall-EFI.isoAfter fully updated the OS, I have installed snomONE as on the http://wiki.snomone.com/index.php?title=Installations
$ wget http://www.snomone.com/downloads/snomONE/install-centos.sh $ chmod a+rx install-centos.sh $ ./install-centos.sh
Then tried to setup a snom870 at hand for PnP Provisioning. My all attempts were failed until I turned the iptables off on CentOS. I have setup the rules according to the snomONE wiki articles;
TCP 80, 161, 389, 443, 5060, 5061UDP 69, 5060, 49152-64512Did I miss any other port to set open? I do not want to leave iptables/firewall down on my snomONE machine. Any ideas?
Thanks.
PnP Buttons not reflected on snom870
in Extension Setup
Posted
This time the behavior has changed a bit. Now when I try to access the URL: https://192.168.x.x/prov/snom_870_buttons.xml?model=snom870, it asks for HTTPs login credentials. What credentials should I give?
May be some hope there?
UPDATE: I went forward resetting the phone and it has got the settings reflected! Super!
Now that the button settings are coming down, I have one more issue. As shown in the initial post of mine about button setting;
3;url;{https-url tftp}/snom870-cam-frontHD.xml;Front CamI realized that the {https-url tftp} part does not get interpreted. Is there any code that interpreted like other settings or just it is a limitation?
Thank you.