Jump to content
Vodia PBX forum

bencrosby

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bencrosby

  • Rank
    Member
  1. Extensions to Auto Provisioning ?

    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 !
  2. 5.4.0

    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
  3. 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
  4. Mini (Beaglebone) Problem

    Thanks, That was perfect, all restored.
  5. Mini (Beaglebone) Problem

    Yup, I have backed up the working directory. I guess I can just reinstall angstrom and put back the pbx directory. Is there any documentation for startup / shutdown scripts etc anywhere ? Thanks !
  6. Mini (Beaglebone) Problem

    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:~#
  7. Adding D765 to Auto-provisioning and PnP

    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. 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 ? 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. Yup, that would work fine. Thanks
  8. Adding D765 to Auto-provisioning and PnP

    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 !
  9. Adding D765 to Auto-provisioning and PnP

    You're right. I didn't. My bad. Thanks for the clarification. Sadly creating the /pbx/html directory and putting the files there didn't work either. Thanks for the advice though.
  10. Adding D765 to Auto-provisioning and PnP

    Thanks, installing it now. Ben
  11. Adding D765 to Auto-provisioning and PnP

    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.
  12. 5.3 - license is not working anymore?

    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.
  13. Adding D765 to Auto-provisioning and PnP

    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.
  14. Adding D765 to Auto-provisioning and PnP

    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.
  15. Adding D765 to Auto-provisioning and PnP

    I'm running 5.3.0 on a Vodia Mini - if you have a 5.3.0a available, please could you post a link to it ? Thanks
×