Jump to content

fonny

Members
  • Posts

    89
  • Joined

  • Last visited

Posts posted by fonny

  1. I have a door-phone configured as extension 600 which calls hunt group 500.

     

    Hunt group 500

    stage 1 calls extension 201

    stage 2 calls extensions 201 202 203 204 205

    final stage calls extension 201

    turn off the cell phone forking is Yes

     

    Extension 201

    has a cell phone number configured.

    When calling the extension in a hunt group: Don't call cellphone

     

    When someone rings the doorbell

    extension 201 rings -> is normal behaviour for stage 1

    all other extensions rings -> normal behaviour for stage 2

    final stage -> extension 201 rings (is OK) but after few seconds also the cellphone !

     

    How come the cellphone rings when not included in hunt group and cellphone forking is disabled?

     

    What is the exact behaviour of the Final Stage?

    What is the meaning of 'Final stage to cellphone' in the documentation? Why the word 'cellphone' here as it can be any number? https://vodia.com/doc/huntgroups

     

     

     

     

     

     

     

  2. Situation: incoming calls go to reception desk, overflow to 3 other employees, after 30s also overflow to 3th employee.

    When all users are out of office during work-hour, possibility to redirect all incoming calls to mobile from one of the employees.
    Solution:
    Defined Agent group (90)
    Logged in Agents: 201 211 204 206
    Agent selection: preference from the agent settings
    All agents for this ACD: 201 211 204 206
    Ring stage: 5s
    Number of agents added per stage: 1
    Caller in queue after hearing ringback for 30s: 203
    For all extensions
    Redirection Cellphone number is filled in.
    Call cell phone: Immediately
    When calling the extension in an agent group: Include cell phone
    For hunt & callback groups: don't call cell phone
    Everything works as expected:
    Incoming call is routed to ACD 90
    Ringing on 201, after 5s on 211, ... after 30s on 203. No cellphones are called.
    Entering Star Code *8090 (set night mode for domain account ACD 90) and 201# will redirect all incoming calls to cell phone of extension 201, entering 204# will redirect all incoming calls to cell phone of extension 204, ... works as expected.
    But when user put extension 201 in DND mode, incoming calls don't go thru. The other agents are not called. This doesn't seem to be normal behaviour.
    I would expect extensions 211, 204, 206 and 203 be called.
    In the log I also get error for No Outbound Dialplan defined for ACD 90.
    In the settings Dialplan is set a domain default.
    -> when I look in the domain settings, I don't see a Dialplan option!
    When I select the Standard Dialplan, and extension 201 has DND active, cellphone of extension 201 is called, after 5s cellphone of extension 211, ...
    This doesn't seem to be normal behaviour either. I can understand it is normal behaviour when a dialplan and call cellphone immediately are selected but I expect the extensions also to ring.
    pbx is Raspberry v56
    Or is there a better solution to solve this setup?
  3. I wish it was true ;(

     

     

    Software-Version: 5.4.1 (Vodia mini PBX) Build Date: Apr 1 2016 18:22:13 License Status: No license License Duration: Permanent Additional license information: Domains: 1/0, Calls: 0/0, Extensions: 5/0, Attendants: 1/0, Callingcards: 0/0, Hunt Groups: 1/0, Paging Groups: 0/0, Service Flags: 5/0, IVR Nodes: 0/0, Agent Groups: 0/0, Conference Rooms: 1/0, CO Lines: 1/0
  4. I couldn't do the software update as the webinterface is stuck after the initial update to 5.4.0

    I needed to brick the beagleboard (couldn't login via ssh), reinstalled Angstrom, got the beagle.sh script (from the other BBB unit I have) and tried reinstalling the pbx.

    This didn't work until I saw a new release was available (v5.4.1). The install went fine with this version.

     

    Except the licence is gone and entering the activation key doesn't work.

    Any clue?

  5. Hi bencrosby,

     

    No I still have this problem.

     

    On one mini I have no problem. On the other I can't get ssh working. And as it works on one and not the other I don't think it has anything to do with ssh client. Both mini's have firmware 5.2.2 builddate april 13 2014 21:09:38

     

    @vodia: any clue how to get this working?

  6. I have 2 mini's which were original at firmware v5.2.0. Had problems with the first one to log in via ssh due to problem with the firmware.

    Updated to v5.2.2, changed password in the web admin from default and after I could login via ssh as root and the new password.

     

    I have a second mini which doesn't allow me via ssh. As said before; this one has firmware v5.2.2, default password set and changed, but still no go.

     

    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?

  7. Tried today to login on another mini via SSH and got these errors. Any idea what's wrong?

     

    Mini has firmware v5.2.2. Admin password has been set & changed. Access enabled for local network.

    Any idea what could be wrong?

     

    ssh root@192.168.6.20 -v
    OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
    debug1: Reading configuration data /etc/ssh_config
    debug1: Connecting to 192.168.6.20 [192.168.6.20] port 22.
    debug1: Connection established.
    debug1: identity file /Users/admin/.ssh/id_rsa type -1
    debug1: identity file /Users/admin/.ssh/id_rsa-cert type -1
    debug1: identity file /Users/admin/.ssh/id_dsa type -1
    debug1: identity file /Users/admin/.ssh/id_dsa-cert type -1
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_6.2
    ssh_exchange_identification: read: Connection reset by peer
  8. Tried with root / root but no go. Updated to v5.2.1 but still nothing. Not with root / root or admin / password.

     

    And I also can't get a config from an existing v5.1.3 uploaded to the mini.

    In fact, there is not much happening on this box

     

    This is the log.

     

    [7] 1:00:08.153 APP: syslog is disabled on the PBX [1] 1:00:08.166 GENE: Starting up version 5.2.1 [7] 1:00:10.241 GENE: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET GMT+2 TUR GMT+3 GMT+4 GMT+6 GMT+7 GMT+8 GMT+9 GMT+10 GMT+11 GMT+12 CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 NZST CHAST MXTC MXTM MXTP GMT [7] 1:00:10.242 GENE: Found Interface lo with IP 127.0.0.1 [7] 1:00:10.244 GENE: Found Interface usb0 with IP 192.168.7.2 [1] 1:00:10.244 GENE: Adding DNS server 127.0.0.1 to the dns server list [8] 1:00:10.456 GENE: Scheduler precision is 0 us [1] 1:00:10.456 GENE: Working Directory is /pbx [5] 1:00:11.681 GENE: Starting threads [7] 1:00:11.683 GENE: UDP(IPv4): Opening socket on 0.0.0.0 [7] 1:00:11.684 GENE: UDP(IPv6): Opening socket on [::] [7] 1:00:11.689 GENE: Found Interface lo with IP 127.0.0.1 [7] 1:00:11.689 GENE: Found Interface eth0 with IP 192.168.120.50 [7] 1:00:11.689 GENE: Found Interface usb0 with IP 192.168.7.2 [8] 1:00:11.689 EMAI: No from address for sending text email [7] 1:00:11.690 GENE: TCP(IPv4): Opening socket on 0.0.0.0:80 [7] 1:00:11.691 GENE: TCP(IPv6): Opening socket on [::]:80 [7] 1:00:11.691 GENE: TCP(IPv4): Opening socket on 0.0.0.0:443 [7] 1:00:11.691 GENE: TCP(IPv6): Opening socket on [::]:443 [7] 1:00:11.691 GENE: TCP(IPv4): Opening socket on 0.0.0.0:2345 [7] 1:00:11.691 GENE: TCP(IPv6): Opening socket on [::]:2345 [7] 1:00:11.692 GENE: TCP(IPv4): Opening socket on 0.0.0.0:2346 [7] 1:00:11.692 GENE: TCP(IPv6): Opening socket on [::]:2346 [7] 1:00:11.692 GENE: UDP(IPv4): Opening socket on 0.0.0.0:161 [7] 1:00:11.692 GENE: UDP(IPv6): Opening socket on [::]:161 [7] 1:00:11.692 GENE: UDP(IPv4): Opening socket on 0.0.0.0:69 [7] 1:00:11.692 GENE: UDP(IPv6): Opening socket on [::]:69 [3] 1:00:11.700 GENE: Done reading large tables [0] 1:00:11.706 GENE: UDP(IPv4): bind() to broadcast port 67 failed [5] 1:00:11.712 GENE: Set scheduling priority to 1 [5] 1:00:11.712 GENE: Set process affinity to 0 [7] 1:00:11.771 GENE: UDP(IPv4): Opening socket on 0.0.0.0:5060 [8] 1:00:11.778 GENE: Joined multicast group 224.0.1.75 [7] 1:00:11.778 GENE: UDP(IPv6): Opening socket on [::]:5060 [7] 1:00:11.778 GENE: TCP(IPv4): Opening socket on 0.0.0.0:5060 [7] 1:00:11.778 GENE: TCP(IPv6): Opening socket on [::]:5060 [7] 1:00:11.779 GENE: TCP(IPv4): Opening socket on 0.0.0.0:5061 [7] 1:00:11.779 GENE: TCP(IPv6): Opening socket on [::]:5061 [7] 1:00:11.779 GENE: UDP(IPv4): Opening socket on 0.0.0.0 [7] 1:00:11.779 GENE: UDP(IPv6): Opening socket on [::] [7] 22:36:15.255 GENE: Found Interface lo with IP 127.0.0.1 [7] 22:36:15.255 GENE: Found Interface eth0 with IP 192.168.120.50 [7] 22:36:15.255 GENE:

    Found Interface usb0 with IP 192.168.7.2

     

  9. Any idea how I can login to the vodia mini ?

     

    I have given a password to the default administrator (security->general>administrator login) but I can't get access via ssh.

     

    I always get Permission denied.

    Any idea what's can be wrong?

     

     

     

×
×
  • Create New...