Search results

  1. D

    CALL PARK NOT WORKING

    theres issues with the valet parking, check out http://www.pbxforums.com/threads/default-call-parking-bridges-calls.832/
  2. D

    Where do we submit bugs found

    I worked out how to fix it (no idea where to send bugs to) See http://www.pbxforums.com/threads/default-call-parking-bridges-calls.832/
  3. D

    Need guidance for an office incoming calls.

    Ive actually been spending a lot of time trying to get the callerid from parking myself. So far no luck though.
  4. D

    Call park oddities

    I spent quite a lot of time fixing up the default call parking config, perhaps it will help you? See http://www.pbxforums.com/threads/default-call-parking-bridges-calls.832/ Im still trying to work out how to get the callee number on the phone of the phone thats bringing a call out of parking.
  5. D

    Call park oddities

    Did you solve this at all?
  6. D

    Call park bridging calls together

    See http://www.pbxforums.com/threads/default-call-parking-bridges-calls.832/
  7. D

    SOLVED Default call parking bridges calls

    the above is what i got working. I found that having * in the ${park_lot} variable broke the regex. for whatever reason \Q${park_lot}\E didnt do what i was hoping - probably the regex is evaluated before the variable is sub'd in... but then the contents of the variable are still considered...
  8. D

    SOLVED Default call parking bridges calls

    From my very recent install, these are the default call parking settings: If im following the logic correctly, in the final stage when $park_in_use == true, the referred_by_user is bridged to the parked caller. if $park_in_use == false, then the transferred caller is placed in to the parking...
  9. D

    Call park bridging calls together

    manually creating the sqlite database, creating its tables and adjusting its permissions to match is neighbors - no data is entered in to it when there is a call parked. something seems quite wrong - i dont know for certain if the default park.lua file is even being used
  10. D

    Call park bridging calls together

    I think that the problem may lie in park.db not being created successfully in /var/lib/freeswitch/db (i.e. database_dir) - this is owned by www-data:www-data which is what freeswitch is running as. The code in my clean install of fusionpbx has sqlite uncommented, but subsequently has code that...
  11. D

    CallerID on active call vs Snom 710/720 phones

    Ok great at least we're seeing the same behavior. Have you modified the out of the box parking configuration of fusionpbx at all? Also, if you're happy for me to pick your brain further - are you using ORBIT+PARK in button config or BLF? I ask because the PARK+ORBIT button will park the call...
  12. D

    CallerID on active call vs Snom 710/720 phones

    This sentence isnt clear to me sorry. Just to confirm, that the callerid is lost when a parked call is retrieved? SO you can see it, you park it, and when it comes back from park its lost?
  13. D

    CallerID on active call vs Snom 710/720 phones

    Heres with the newer version of the firmware, where its working AOK INVITE sip:545@172.29.0.87:5060;line=hgdvc3nm SIP/2.0 Via: SIP/2.0/UDP 192.168.1.249;rport;branch=z9hG4bKU7g7jcDKB04Up Route: <sip:545@172.29.0.87:5060>;line=hgdvc3nm Max-Forwards: 67 From: "04xxxxxxx74"...
  14. D

    CallerID on active call vs Snom 710/720 phones

    I would guess that the 8.9.3.x family are fixed. Might I ask if you're using valet parking? And if so do the caller ID's get correctly shown when your retrieve a parked caller?
  15. D

    CallerID on active call vs Snom 710/720 phones

    Yeah snom requires you to make an account with their forum thingy to be able to read posts. Its not fully public. My question is identical, and their only recommendation so far is to upgrade the firmware from 8.7.5.35 -> 8.7.5.44. However as mentioned that didnt help. I just tried upgrading to...
  16. D

    CallerID on active call vs Snom 710/720 phones

    Hi Team, I have installed FusionPBX 4.2.5 on Debian 8 which brings in FreeSWITCH 1.6.20 (64bit) Everything pretty much "just works" - which is a great result. I am using Snom 710 and 720 handsets with 8.7.5.35 and 8.7.5.44 Supposedly thew firmware solves the problem (according to my post...