Jump to content

bencrosby

Members
 View Profile  See their activity

  • Posts

    20

  • Joined

  • Last visited

 Content Type 

Posts posted by bencrosby

  1. -bash: ./pbxctrl: cannot execute: required file not found

    in Linux-related Topics

    Posted

    On 3/5/2024 at 12:09 PM, Vodia PBX said:

    Do you see the file pbxctrl and pbxctrl.dat in the /pbx directory? What if you 

    mkdir /pbx
cd /pbx
./install-mini3.sh

     

    Yes. They are in the directory.
      

    024-03-29 13:43:34 (2.65 MB/s) - ‘pbxctrl-69.2.3.dat’ saved [4526265/4526265]

Starting PBX daemon./pbx: line 29: /pbx/pbxctrl: cannot execute: required file not found

pbx@pbx:/pbx$ ls -la
total 14024
drwxr-xr-x  4 pbx  root    4096 Mar 29 13:43 .
drwxr-xr-x 19 root root    4096 Mar 29 13:35 ..
drwxr-xr-x  2 root root   20480 Mar 29 13:43 audio_en
drwxr-xr-x  2 root root    4096 Mar 29 13:43 audio_moh
-rwxr-xr-x  1 pbx  pbx     3702 Mar 16 06:36 install-mini3.sh
-rwxr-xr-x  1 root root 9793532 Mar 16 01:54 pbxctrl
-rw-r--r--  1 root root 4526265 Mar 16 01:36 pbxctrl.dat
pbx@pbx:/pbx$

    I am *guessing* that you've supplied a dynamically linked binary, which needs ld-linux-armhf.so.3
    On the Pi5 Raspbian OS, are expecting binaries to link to /lib/ld-linux-aarch64.so.1
     

  2. -bash: ./pbxctrl: cannot execute: required file not found

    in Linux-related Topics

    Posted

    Hi team,

    I'm just attempting a clean install on a new Raspberry Pi 5.

    It's a current, clean, Raspbian 64bit lite install (Debian Bookworm), patched and upgraded to current (apt update; apt upgrade)

    Then followed https://doc.vodia.com/docs/installlinux and the Raspberry Pi specific section.

    Upon completing, I can't run pbxctrl. I'm wondering if on Pi 5 I am better using the debian installer, or is there something else obvious to check. Unfortunately the error doesn't tell me which required file can't be found.

     

    Cheers

      

    admin@pbx:/tmp$ sudo ./install-mini3.sh 
./install-mini3.sh: 38: [: Illegal number: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  libcamera0.1
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  ntpsec python3-ntp
Suggested packages:
  certbot ntpsec-doc ntpsec-ntpviz
The following packages will be REMOVED:
  systemd-timesyncd
The following NEW packages will be installed:
  ntp ntpsec python3-ntp
0 upgraded, 3 newly installed, 1 to remove and 0 not upgraded.
Need to get 446 kB of archives.
After this operation, 1,291 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.debian.org/debian bookworm/main arm64 python3-ntp arm64 1.2.2+dfsg1-1+deb12u1 [94.0 kB]
Get:2 http://deb.debian.org/debian bookworm/main arm64 ntpsec arm64 1.2.2+dfsg1-1+deb12u1 [330 kB]
Get:3 http://deb.debian.org/debian bookworm/main arm64 ntp all 1:4.2.8p15+dfsg-2~1.2.2+dfsg1-1+deb12u1 [22.0 kB]
Fetched 446 kB in 0s (3,437 kB/s)
(Reading database ... 74410 files and directories currently installed.)
Removing systemd-timesyncd (252.22-1~deb12u1) ...
Selecting previously unselected package python3-ntp.
(Reading database ... 74394 files and directories currently installed.)
Preparing to unpack .../python3-ntp_1.2.2+dfsg1-1+deb12u1_arm64.deb ...
Unpacking python3-ntp (1.2.2+dfsg1-1+deb12u1) ...
Selecting previously unselected package ntpsec.
Preparing to unpack .../ntpsec_1.2.2+dfsg1-1+deb12u1_arm64.deb ...
Unpacking ntpsec (1.2.2+dfsg1-1+deb12u1) ...
Selecting previously unselected package ntp.
Preparing to unpack .../ntp_1%3a4.2.8p15+dfsg-2~1.2.2+dfsg1-1+deb12u1_all.deb ...
Unpacking ntp (1:4.2.8p15+dfsg-2~1.2.2+dfsg1-1+deb12u1) ...
Setting up python3-ntp (1.2.2+dfsg1-1+deb12u1) ...
Setting up ntpsec (1.2.2+dfsg1-1+deb12u1) ...
Created symlink /etc/systemd/system/timers.target.wants/ntpsec-rotate-stats.timer → /lib/systemd/system/ntpsec-rotate-stats.timer.
Created symlink /etc/systemd/system/network-pre.target.wants/ntpsec-systemd-netif.path → /lib/systemd/system/ntpsec-systemd-netif.path.
Created symlink /etc/systemd/system/ntp.service → /lib/systemd/system/ntpsec.service.
Created symlink /etc/systemd/system/ntpd.service → /lib/systemd/system/ntpsec.service.
Created symlink /etc/systemd/system/multi-user.target.wants/ntpsec.service → /lib/systemd/system/ntpsec.service.
Setting up ntp (1:4.2.8p15+dfsg-2~1.2.2+dfsg1-1+deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'nodejs' is not installed, so not removed
The following package was automatically installed and is no longer required:
  libcamera0.1
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'apache2' is not installed, so not removed
The following package was automatically installed and is no longer required:
  libcamera0.1
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  libcamera0.1
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 2,045 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 74469 files and directories currently installed.)
Removing libcamera0.1:arm64 (0.1.0+rpt20231122-1) ...
Processing triggers for libc-bin (2.36-9+rpt2+deb12u4) ...
--2024-03-04 13:10:44--  https://portal.vodia.com/downloads/pbx/audio/audio_en.zip
Resolving portal.vodia.com (portal.vodia.com)... 54.175.147.78
Connecting to portal.vodia.com (portal.vodia.com)|54.175.147.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10389084 (9.9M) [application/zip]
Saving to: ‘audio_en.zip’

audio_en.zip        100%[===================>]   9.91M  3.94MB/s    in 2.5s    

2024-03-04 13:10:47 (3.94 MB/s) - ‘audio_en.zip’ saved [10389084/10389084]

Archive:  audio_en.zip
  inflating: audio_en/aa_accounting.wav  
  inflating: ...  
 <truncated>  
  inflating: audio_en/wk_welcome.wav  
--2024-03-04 13:10:47--  https://portal.vodia.com/downloads/pbx/audio/audio_moh.zip
Resolving portal.vodia.com (portal.vodia.com)... 54.175.147.78
Connecting to portal.vodia.com (portal.vodia.com)|54.175.147.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 856238 (836K) [application/zip]
Saving to: ‘audio_moh.zip’

audio_moh.zip       100%[===================>] 836.17K   680KB/s    in 1.2s    

2024-03-04 13:10:49 (680 KB/s) - ‘audio_moh.zip’ saved [856238/856238]

Archive:  audio_moh.zip
  inflating: audio_moh/bi_ced.wav    
  inflating: ... 
   <truncated>   
  inflating: audio_moh/page_end.wav  
--2024-03-04 13:10:49--  https://portal.vodia.com/downloads/pbx/mini3/pbxctrl-mini3-69.2.1
Resolving portal.vodia.com (portal.vodia.com)... 54.175.147.78
Connecting to portal.vodia.com (portal.vodia.com)|54.175.147.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9756640 (9.3M)
Saving to: ‘pbxctrl-mini3-69.2.1’

pbxctrl-mini3-69.2. 100%[===================>]   9.30M  4.11MB/s    in 2.3s    

2024-03-04 13:10:52 (4.11 MB/s) - ‘pbxctrl-mini3-69.2.1’ saved [9756640/9756640]

--2024-03-04 13:10:52--  https://portal.vodia.com/downloads/pbx/dat/pbxctrl-69.2.1.dat
Resolving portal.vodia.com (portal.vodia.com)... 54.175.147.78
Connecting to portal.vodia.com (portal.vodia.com)|54.175.147.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4523967 (4.3M)
Saving to: ‘pbxctrl-69.2.1.dat’

pbxctrl-69.2.1.dat  100%[===================>]   4.31M  2.61MB/s    in 1.7s    

2024-03-04 13:10:55 (2.61 MB/s) - ‘pbxctrl-69.2.1.dat’ saved [4523967/4523967]

Starting PBX daemon./pbx: line 29: /pbx/pbxctrl: cannot execute: required file not found

admin@pbx:/tmp$

     

  3. Extensions to Auto Provisioning ?

    in General Setup

    Posted

    I have had some more time to think about this.

     

    1) I agree, this sounds like a workable solution.

     

    In essence the phones need to trust the PBX. This would work fine as a private CA. If every PBX CA is a sub-CA of the Vodia Root CA, that's in theory fine, but I'm not sure it is necessary. Completely agree that people don't want to purchase certs every year, especially not for each phone.

     

    I do think there is some potential magic with a new phone and various auto discovery services - both polycom and snom to my knowledge allow an internet based lookup to find their provisioning server. It would be cool to be able to provision certs and then bring up SSL based signalling, allowing a new phone to be internet provisioned for remote offices.

     

    2) In my specific scenario, I have had to modify each phone_xml file to add these:

      <ethernet_detect perm="RO">off</ethernet_detect>
  <wifi_auth_mode perm="RO">WPA2PSK</wifi_auth_mode>
  <wifi_essid perm="RO">WifiNetName</wifi_essid>
  <wifi_wpapsk perm="RO">1234567890123456</wifi_wpapsk>
  <logon_wizard perm="RW">off</logon_wizard>
  <wifi_wpa_encryptype perm="RO">AES</wifi_wpa_encryptype>

    I would rather have this contained in a single file that is pushed to the phones, like wifi.xml and then link to the main files somehow with:

    <setting-files>
  <file url="{https-url}/snom_wifi.xml" />
</setting-files>

    This means WiFi credentials are stored only in a single location in the configuration.

     

    3) Okay, I see your point. I wonder if it is possible to configure a key event that clears MW across all extensions. I also think I will explore the message button and missed call notifier LED as seperate items. It may be possible to leave the message key and LED for an individual extension and just do a global clear missed calls.

     

    Thanks !

  4. 5.4.0

    in Announcements

    Posted

    We have made version 5.4.0 for Windows 32/64, CentOS 32/64, Debian 32/64, FreeBSD 64 and the snom mini. Later today we will have also Vodia mini PBX (BeagleBone and Raspberry Pi). MacOS will take a few days longer, as our Mac mini is really really slow these days and needs to be replaced. If you are using CPE licenses, please check at http://vodia.com/en/mplan if this upgrade is covered with your license.

     

    Highlights of this release are:

     

    • It contains an API for voicemail to text, so that your customers can get a text preview of the voicemail (available only for hosted PBX)
    • There was something not working well with Fax-to-email which seems to be working better now
    • The PBX can now write MongoDB CDR records (also only for hosted PBX)
    • We have added some more phone models for automatic provisioning, giving you a better choice of devices that ever

    The release notes are available as usual at http://vodia.com/doc/releasenotes540

     

     

    Hi folks,

    Upon installing this on a mini, I was faced with some very strange behaviour - the web UI didn't have the usual legends (account, password, language etc) it had what looked like variable names instead. I couldn't log in via the web UI. None of the phones re-registered. I have backed out 5.4.0 and gone back to 5.3.2, and everything is fine (ssh in, replace pbxctrl with pbxctrl-old)

     

    I am happy to do a bit more testing if you have some things you want me to try out ?

     

    Thanks

  5. Extensions to Auto Provisioning ?

    in General Setup

    Posted

    Hi,

     

    I would very much like to be able to extent the PnP capabilities of the PBX. In all cases, I am using a mix of Snom 760, D765, D725 and D715. I do understand that some of this is device specific.

     

    I have three scenarios in particular:

     

    1) Automatic installation of certificates to devices:

     

    Connected to a trusted network, and having been provisioned with extension credentials, It would be great to be able to automatically deploy device certificates, loading them into both the phone and the PBX.

     

    2) Wi-Fi and 802.1x credentials - similar to above, I want to move some phones to Wi-Fi. Once the phone has been provisioned over ethernet, it would be cool to be able to load a Wifi-settings.xml or similar file to the phone.

     

    3) Really looking for a great way to cancel the "missed calls" LED across all extensions, and to change the line monitoring LED on a couple. It looks like snom has the options in config, so for me, it would be loading an LED-settings.xml.

     

    I can quietly go off and do most of this. The issue is that I need to be able to insert a line into one of the PBX PnP files to call another file from the PBX. Then I need to add that file to an appropriate place on the PBX so that the phones can request it as part of PnP provisioning.

     

    Are there any thoughts on how this might be done ?

     

    Thanks

    Ben

  8. Mini (Beaglebone) Problem

    in General Setup

    Posted

    Hi, I have had a series of power problems that have resulted in my PBX mini (beagle bone) no longer joining the network.

     

    It boots fine, and is accessible via the serial port on board, but doesn't bring up a network interface.

    There are a few interesting error messages during boot, but I have no idea if they are normal.

     

    Could you provide a link via pm to re-download the image so I can re-flash the mmc ?

     

    Alternatively, if you can see the issue from the log below, please let me know how to resolve.

     

    Thanks

     

     

    Here is the boot log pasted below:

    U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img
 
 
U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53)
 
I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
 
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0 
gpio: pin 53 (gpio 53) value is 1
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
mmc0(part 0) is current device
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
No micro SD card found, setting mmcdev to 1
mmc1(part 0) is current device
mmc_send_cmd : timeout: No status update
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
reading uEnv.txt
26 bytes read in 4 ms (5.9 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
gpio: pin 55 (gpio 55) value is 1
4394080 bytes read in 763 ms (5.5 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24884 bytes read in 47 ms (516.6 KiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Angstrom/3.8.13/beaglebone
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4394016 Bytes = 4.2 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   XIP Kernel Image ... OK
OK
   Using Device Tree in place at 80f80000, end 80f89133
 
Starting kernel ...
 
Uncompressing Linux... done, booting the kernel.
[    0.195888] omap2_mbox_probe: platform not supported
[    0.206562] tps65217-bl tps65217-bl: no platform data provided
[    0.283025] bone-capemgr bone_capemgr.9: slot #0: No cape found
[    0.320132] bone-capemgr bone_capemgr.9: slot #1: No cape found
[    0.357240] bone-capemgr bone_capemgr.9: slot #2: No cape found
[    0.394350] bone-capemgr bone_capemgr.9: slot #3: No cape found
[    0.414181] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[    0.423792] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[    0.444301] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed
[    0.451601] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[    0.519876] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[    0.531613] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[    0.538995] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
systemd-fsck[85]: Angstrom: clean, 41960/112672 files, 359580/449820 blocks
[    4.867688] libphy: PHY 4a101000.mdio:01 not found
[    4.872761] net eth0: phy 4a101000.mdio:01 not found on slave 1
 
.---O---.                                           
|       |                  .-.           o o        
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                -'  |
                '---'
 
The Angstrom Distribution pbx ttyO0
 
Angstrom v2012.12 - Kernel 3.8.13
 
pbx login: root
Password: 
Last login: Sat Jan  1 11:00:30 EST 2000 on ttyO0
root@pbx:~#

  9. Adding D765 to Auto-provisioning and PnP

    in General Setup

    Posted

    2) The codec preference on the phone has only limited impact on what codec is actually selected. The PBX will always use it's own setting to determine the codec in the negotiation process. At the end of the day this helps keeping the SDP attachment shorter, which is important if the phone should use UDP where the MTU is typically 1492 bytes. The phones may propose more codecs, but the PBX does not support them. A side note on G722 and other high quality codecs: The problem is that most of the (important) calls eventually end up in the PSTN, where pcmu and pcma are still the prevalent codecs. When you use a G.722 codec to talk to the PSTN, it will eventually get transcoded down to G.711. Unfortunately every information transformation from one format to another reduces the quality of the call, the codecs can not "invent" information (at least not those codecs we are talking about here), that is why it is better to focus on G.711 as the primary codec and use high compressing codecs when bandwidth is a problem. We experienced this problem first hand when we happily started using G.722 and customers complained about damped call quality, which at first puzzled us but later when you think about it made sense.

     

     

    Yup, I agree in theory. In practice the internal HD option should be negotiated as a priority for internal calls, and g.711 / PCMA should end up being used externally - *unless* you have a SIP trunk provider who is doing G.722 and interconnecting to telcos at G.722. At least in Australia, the national Telco has wideband deployed throughout their network, including AMR-WB / G722.2 for the Cellular network.

     

    Personally, I would cut the codec list down to G722, PCMU and PCMA.

     

    Ps - region codes should select PCMA for EU, Asia and Australia, and PCMU for the USA - that could be done automagically too.... ($0.02)

     

    Interesting debate anyway.

     

     

    4) The tones are those two digits after the "audio_" in the file system. By default it is USA if nothing else was found. Which one is missing?

     

     

    Sorry, I wasn't clear here. I'm not sure if any languages are missing. You appear to be enumerating au=AUS correctly. That setting doesn't make its way into the phone config at;

     

    <tone_scheme perm="RW">{enum domain lang_tones USA au=AUS at=AUT ch=CHN dk=DNK fr=FRA de=GER uk=GBR in=IND it=ITA jp=JPN mx=MEX nl=NLD no=NOR nz=NZL sp=ESP sw=SWE ch=SWI}</tone_scheme>

     

    So my question is what UI setting will result in the correct enum to au=AUS for this part of the configuration? Settings / General / System Administration / General / Default Tone Language only has "English" in my drop down. I assume this is where the tone list should reside ?

     

    5) The problem is that we need to "guess" if users should use 12 or 24 hour format and how they want the date. We could use the country code which works well for the rest of the world, the problem is Canada. Looking at https://en.wikipedia.org/wiki/Date_and_time_notation_in_Canada it seems to be fine to use the same notation like in the US. So:

     

    <time_24_format perm="RW">{enum domain country_code on 1=off}</time_24_format>
    <date_us_format perm="RW">{enum domain country_code off 1=on}</date_us_format>

     

     

    You could add a global 12h / 24h radio button under timezone at Settings / General / System Administration / General /

    Or a domain based 12h / 24h under Domain / Advanced / General Settings / Advanced / just after Timezone

     

    My domain country code is set to 61, so your proposed change would work fine in my environment.

     

    6) That problem is related. I think that <dialnumber_us_format perm="RW">{enum domain country_code off 1=on}</dialnumber_us_format> should properly solve that problem. It assumes that the admin set the country code.

     

    Yup, that would work fine.

     

    Thanks

  10. Adding D765 to Auto-provisioning and PnP

    in General Setup

    Posted

    So 5.3.0a should be available for all minis now.

     

    I confirm the successful provisioning of a D765 on 5.3.0a, same process as 760...

     

    I have a few comments on the build;

     

    IMHO, snom_760_phone.xml contains a few mistakes;

     

    1) template file contains;

     

    <ignore_security_warning perm="RW">on</ignore_security_warning>

    <ignore_security_warning>on</ignore_security_warning>

     

    Both entries in file (redundant)

     

    2) <codec_priority_list idx="{lc}" perm="RW">pcmu,pcma,gsm,g722,g726-32,g729,telephone-event</codec_priority_list>

     

    This doesn't match snom default priority list: g722, pcmu, pcma, gsm, g726-32, aal2-g726-32, amr-0, amrwb-0, g729, telephone-event, and results in the de-prioritisation of g722 wideband codec.

     

    3) Setting under domains / advanced / general settings / emergency numbers is not being carried through to phone parameter <keyboard_lock_emergency perm="RW">VALIDVALUE</keyboard_lock_emergency>

     

    4) <tone_scheme perm="RW">{enum domain lang_tones USA au=AUS at=AUT ch=CHN dk=DNK fr=FRA de=GER uk=GBR in=IND it=ITA jp=JPN mx=MEX nl=NLD no=NOR nz=NZL sp=ESP sw=SWE ch=SWI}</tone_scheme>

     

    This doesn't match domains / advanced / general settings / tone language (only English in list) - Where is the correct tone scheme set in the PBX UI ? e.g. "AU"

     

    5) Similarly, ( sorry, these are my overrides, I can't recall the default) where are these two values set in the UI ? All my languages are English, but that's not enough to turn off US date format and US number format on the phone.

     

    <time_24_format perm="RW">on</time_24_format>

    <date_us_format perm="RW">off</date_us_format>

     

    6) Snom configuration parameter <dialnumber_us_format perm="RW">off</dialnumber_us_format> should be enabled for non-US locations. I have Europe 3-digit extensions set under domain / advanced settings / general / provisioning parameters / default PnP dial plan scheme.

     

    Still playing with the build, will let you know if I find others.

    Thanks !

  13. Adding D765 to Auto-provisioning and PnP

    in General Setup

    Posted

     

    Place the "snom_D765.xml" file in the PBX \ html directory. If the html directory doesn't exist then create it. That's how it was done in the ver 4.5 days, let me know if it works.

     

     

    I think you can upload the snom firmware files to the PBX \ tftp directory, if it doesn't exist then create it.

     

    Thanks. Under V5, there is a /pbx/webpages directory, but files put there are not accessible to the phones via the provisioning - at least as far as I could determine.

     

    And for the firmware, I actually need to put those into the web directory too. The phones all go to snom's website to pull their firmware directly. That means I have 11 phones that all pulled ~30MB for their upgrades, rather than me just doing it once - it's very minor, but annoying in a country where we pay for internet bandwidth.

  14. 5.3 - license is not working anymore?

    in General Setup

    Posted

    Yup, mine worked when I reapplied the license.

     

    I read the following

     

    "Bundles that have been purchased before 30th September 2015 will include a two year maintenance plan. However, there will be no support tickets included."

     

    to mean that any bundles purchased before 30th September 2015 will include software updates until September 2017. After that, a paid support maintenance plan will be required every year. If so, I am quite comfortable with the new licensing model.

  15. Adding D765 to Auto-provisioning and PnP

    in General Setup

    Posted

    Hmm, unfortunately, I have both 760's and 765's. I will hijack one of the other phones I guess. It would still be good to be able to add custom.xml configuration files to the server. I don't see an easy way to do this, short of adding a web server onto the beaglebone on a different port, and referencing files from it's webroot. That seems to be an excessively complex solution.

     

    One other example that came to mind.... rather than sending each phone to snom to get it's new firmware file, I would rather host the file on the PBX and allow the phones to download from the PBX. I have no problem loading the firmware to the PBX using sftp, but then need to present it over https.

  16. Adding D765 to Auto-provisioning and PnP

    in General Setup

    Posted

    I have a mini PBX premium 20. This is the one based on the beaglebone black. Nowhere on the data sheet or website could I find reference to having to buy maintenance plans for this device.

     

    If 5.3.0a will not be available under my current license, then back to my original question. How do I create or add new template files to the server to be served when referenced as I have done above. All existing templates are in a drop down list. How do I add a new one ?

     

    Thank you.

  18. Adding D765 to Auto-provisioning and PnP

    in General Setup

    Posted

    Hi, I have modified the following files;

     

    pnp.xml

     

    added between snom_760 and snom_mp sections:

      <file name="snom_D765.xml" encoding="xml">
    <pattern>snomD765-############.htm</pattern>
    <prefix>true</prefix>
    <macpos>8</macpos>
    <vendor>snom</vendor>
    <anonymous>true</anonymous>
    <protocol>tftp,http,https</protocol>
    <pnp-vendor>snom</pnp-vendor>
    <pnp-model>snomD765</pnp-model>
    <pnp-version>^[78]</pnp-version>
    <pnp-content-type>application/url</pnp-content-type>
    <pnp-url>{https-url}/snomD765-{mac}.htm</pnp-url>
  </file>

    snom_3xx_fs.xml:

    <?xml version="1.0" encoding="utf-8"?>
<firmware-settings>{if_parm model snom300}
  <firmware perm="RW">http://downloads.snom.com/fw/snom300-8.7.3.25.9-SIP-f.bin</firmware>{fi_parm model snom300}{if_parm model snom320}
  <firmware perm="RW">http://downloads.snom.com/fw/snom320-8.7.3.25.9-SIP-f.bin</firmware>{fi_parm model snom320}{if_parm model snom360}
  <firmware perm="RW">http://downloads.snom.com/fw/snom360-8.7.3.25.9-SIP-f.bin</firmware>{fi_parm model snom360}{if_parm model snom370}
  <firmware perm="RW">http://downloads.snom.com/fw/snom370-8.7.3.25.9-SIP-f.bin</firmware>{fi_parm model snom370}{if_parm model snom820}
  <firmware perm="RW">http://downloads.snom.com/fw/snom820-8.7.3.25.9-SIP-r.bin</firmware>{fi_parm model snom820}{if_parm model snom821}
  <firmware perm="RW">http://downloads.snom.com/fw/snom821-8.7.3.25.9-SIP-r.bin</firmware>{fi_parm model snom821}{if_parm model snom870}
  <firmware perm="RW">http://downloads.snom.com/fw/snom870-8.7.3.25.9-SIP-r.bin</firmware>{fi_parm model snom870}{if_parm model snom710}
  <firmware perm="RW">http://downloads.snom.com/fw/snom710-8.7.3.25.9-SIP-r.bin</firmware>{fi_parm model snom710}{if_parm model snom715}
  <firmware perm="RW">http://downloads.snom.com/fw/snom715-8.7.5.28-SIP-r.bin</firmware>{fi_parm model snom715}{if_parm model snom720}
  <firmware perm="RW">http://downloads.snom.com/fw/snom760-8.7.5.28-SIP-r.bin</firmware>{fi_parm model snom720}{if_parm model snom760}
  <firmware perm="RW">http://downloads.snom.com/fw/snom760-8.7.5.28-SIP-r.bin</firmware>{fi_parm model snom760}{if_parm model snomD765}
  <firmware perm="RW">http://downloads.snom.com/fw/snomD765-8.7.5.28-SIP-r.bin</firmware>{fi_parm model snomD765}{if_parm model snom_mp}
  <firmware perm="RW">http://downloads.snom.com/fw/snomMP-8.7.3.25.9-SIP-r.bin</firmware>{fi_parm model snom_mp}{if_parm model snom_pa}
  <firmware perm="RW">http://downloads.snom.com/fw/snomPA1-8.7.3.25.9-SIP-f.bin</firmware>{fi_parm model snom_pa}
</firmware-settings>

    snom_3xx_fw.xml:

    <?xml version="1.0" encoding="utf-8"?>
<phone-settings>{if_parm model snom300}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom300</firmware_status>{fi_parm model snom300}{if_parm model snom320}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom320</firmware_status>{fi_parm model snom320}{if_parm model snom360}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom360</firmware_status>{fi_parm model snom360}{if_parm model snom370}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom370</firmware_status>{fi_parm model snom370}{if_parm model snom820}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom820</firmware_status>{fi_parm model snom820}{if_parm model snom821}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom821</firmware_status>{fi_parm model snom821}{if_parm model snom870}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom870</firmware_status>{fi_parm model snom870}{if_parm model snom710}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom710</firmware_status>{fi_parm model snom710}{if_parm model snom715}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom715</firmware_status>{fi_parm model snom715}{if_parm model snom720}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom720</firmware_status>{fi_parm model snom720}{if_parm model snom760}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom760</firmware_status>{fi_parm model snom760}{if_parm model snomD765}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snomD765</firmware_status>{fi_parm model snomD765}{if_parm model snom_mp}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom_mp</firmware_status>{fi_parm model snom_mp}{if_parm model snom_pa}
  <firmware_status perm="RW">{https-url}/snom_3xx_fs-{mac}.xml?model=snom_pa</firmware_status>{fi_parm model snom_pa}
</phone-settings>

    Now, my questions, how do I create a new template file: "snom_D765.xml" ? There doesn't appear to be a way to add a new configuration template that doesn't exist.

     

    Thanks.

    Ben

  19. ssh login vodia mini

    in General Setup

    Posted

    For that you would have to "nuke" the mini using a SD card and re-install the PBX.

     

    I'm totally happy to try this. Without ssh access, I cannot modify the logging and add some of the customisations I want.

     

    I've started on a rebuilt image that leverages the TI Sitara hardware a bit better - including the built in crypto and I'm chasing down DSP support for echo cancellation and transcoding at the moment.

     

    How do I get the arm PBX distro ? Is there source available for a local compile ?

     

    Thanks!

  20. ssh login vodia mini

    in General Setup

    Posted

    I am connecting from the same client eg Terminal on a MacBook with OS X 10.9.2

    Even forcing v2 in the ssh cmd doesn't help.

     

    Do you have some other ideas what I could do?

    Did you ever manage to get this resolved ?

     

    I'm trying SSH to the pbx mini from a mac also, and the same issue exists. A quick search online shows that perhaps permissions may be wrong within the unix structure of the pbx image...?

     

     

     

    Cheers

×
×
  • Create New...