Jump to content

Baze

Customers
  • Posts

    154
  • Joined

  • Days Won

    9

Posts posted by Baze

  1. Here is a snippet of an aastra 6739i BLF config:

    #BLF Key Settings
    softkey1 type: blfxfer
    softkey1 value: *31
    softkey1 line: 1
    softkey1 label: "Park 1"
    
    softkey2 type: blfxfer
    softkey2 value: *32
    softkey2 line: 1
    softkey2 label: "Park 2"
    
    softkey3 type: blfxfer
    softkey3 value: 5555
    softkey3 line: 1
    softkey3 label: "Pa O"
    
    softkey4 type: blfxfer
    softkey4 value: 544
    softkey4 line: 1
    softkey4 label: "Client conf 1"
  2. Sure, so here is a screenshot:

    image.png.b358be65d59350b99af36369ba0065b1.png

    Here is the associated config file to make the above work:

    linekey.1.label = Brandon B
    linekey.1.type = 16
    linekey.1.value = 1234
    linekey.1.line = 1
    
    linekey.2.label = Jeremy K
    linekey.2.type = 16
    linekey.2.value = 1218
    linekey.2.line = 1
    
    linekey.3.label = Kyle V
    linekey.3.type = 16
    linekey.3.value = 1237
    linekey.3.line = 1
    
    linekey.4.label = David K
    linekey.4.type = 16
    linekey.4.value = 1230
    linekey.4.line = 1
    
    linekey.5.label = Janae S
    linekey.5.type = 16
    linekey.5.value = 1221
    linekey.5.line = 1
    
    linekey.6.label = Bill J
    linekey.6.type = 16
    linekey.6.value = 1224
    linekey.6.line = 1
    
    linekey.7.label=Pramod V
    linekey.7.type = 16
    linekey.7.value = 1236
    linekey.7.line = 1
    
    linekey.8.label = Park 1
    linekey.8.type = 10
    linekey.8.value = *31
    linekey.8.line = 1
    
    linekey.9.label = Park 2
    linekey.9.type = 10
    linekey.9.value = *32
    linekey.9.line = 1
    
    linekey.10.label = Park 3
    linekey.10.type = 10
    linekey.10.value = *33
    linekey.10.line = 1
    
    linekey.11.label = Page All
    linekey.11.type = 13
    linekey.11.value = 2555
    linekey.11.line = 1
    
  3. Is this on your own cluster you set up?  Is the provisioning that you are doing from a server you set up also?  BLF works great on the Yealink, and also does work on Aastra.  Best way we like to do this is to login to the UI on the phones and then set it from the GUI there.  Once that is done and tested, usually there is an option to export the phone config which will give you the exact information you need.  They change from vendor to vendor, and sometimes from firmware to firmware (esp Yealink can) so just keep an eye on that.

  4. 39 minutes ago, Baze said:

    We just put in a commit to allow ring tones to be selected from a callflow, however you might have to remove the internal/external from the device, because that would likely override this.  I'll see if I can track down the commit.

    Here is the commit for the backend.  Looks like we didn't do a PR on the front end; I've asked our team to get that added, so should be merged shortly after that.  https://github.com/2600hz/kazoo/commit/3a75fa9531a721412beb2f78fd75d1f34cc716d8#diff-9dc4e41be30a38fa6bae368a6bc08846

  5. Thanks for getting this all in one place!  We were able to get working other than one piece here.  Has anyone been able to get the correlation between a leg and b leg working?  From your initial screenshots @Anthony Manzella it looks like your call ID has the b2b tag there, but from what we are looking at we don't have any sort of x-cid or other call leg id we can use to correlate the two legs.  @safarov had a bit of a patch/hack but as we'd love to avoid needing to reload this every time: https://github.com/sergey-safarov/kazoo/commit/2478d500e7f108fcba598bc7ca4001285a70dceb.  

    In any case, just looking to see if anyone has that working.  Thanks!

  6. Add another vote for check the box for enable consistent NAT.  From what we noticed, the older (several years that is) versions of the firmware did different things, so that is why sometimes you see conflicting docs.  Other things we do are:
    -change the UDP timeout to 3600 (well, depending on how your phones are config'd)
    -turn OFF sip alg
    -set up bandwidth management and prioritize by IP or another method.

    We've also noticed many times people will turn on QoS settings thinking that will prioritize, but if I recall all that really does is just select to leave existing tags on the packets or manually add 46 and such, but it does NOT do anything in the way of prioritizing.
  7. Hi guys - I just went in and created a JIRA ticket (hopefully correctly!!!) for this.  You never realize how much work goes into a simple request until you have to type out the specs, and I'm sure there are many steps I missed.  ;)  Would be a cool thing, though, and we have had a request or two over the years for it too.  Looks like there are around 794 other tickets, though.  The guys over there look to be pretty slammed!

    https://2600hz.atlassian.net/browse/ABP-27
  8. Hey Rick - I spoke to my guys about this, and definitely interested and would love to contribute back as a PR to master if we came up with something good. We are pretty slammed right now, so probably a few months before we could help. My provisioning guys said they would buy me lunch for a month if we did this for them, so not sure what the value would translate to there. ha!
  9. Hi Everyone - we've had a few requests from clients on this (mainly from old MSFT responsepoint clients or skype for biz) and always thought it was a great idea.  Anyone here done anything like it?  

    Idea is:
    • Call comes in and goes direct to message
    • "Thank you for calling, please tell me who you are trying to reach?"
    • (caller) - "Brandon"
    • "Transferring to Brandon Last Name now"
    Behind the scenes:
    • Message is played to caller
    • goes to a "waiting to record" callflow where we are recording that leg of the call. 
    • the recording is then converted to WAV
    • A directory has already been selected at setup, and the first name / last names are snagged and saved dynamically (so could also add "Sales" , "Support" , etc.) so that the list of potential matches is up to date with smartPBX directory
    • API Call is made to iSpeech 
    • They provide a method to send the API call with a WAV along with a list of names to compare.  Our main issue with iSpeech ASR is it is horrible at 8bit audio, but with a list to compare against and a simple name, we think it should be good.
    • iSpeech returns the name
    • name is matched against directory and a blind transfer is initiated to the user callflow or group.
  10. May be worthwhile to check on the networking side also. #1, do they have the bandwidth, because that is essentially 15 concurrent calls coming through, and #2, is their firewall set to bypass any type of flood control rules or otherwise that may be causing problems. Our next step would be to pcap their router to figure out whether the invites aren't getting to their location, or they are, but they aren't then being passed to the phones.
  11. By intercom you mean 2-way, correct?  Polycom and Yealink can use the paging feature (in advanced callflow) which is 1-way and easy.  To get fancier you'd have to use the multicast paging which allows subscribing, but then can allow for Push to Talk for two way paging.  Another benefit there is in VERY large installations you can do internal paging without sending all of those calls over the WAN.  I can send a dummy config if you'd like.
  12. Wanted to see if anyone else has a good solution here.  In cases where you want the main callflow to go to a forwarded device (say a call center or cell phone in case of power outage), there isn't an easy way to set.  If you use the option to go to a user, it sets the default ring time to 20 seconds, which isn't enough usually.  We were talking about adding a fourth option which is just "call forward" and sets the callflow to a 60 second timeout to the device instead.  Anyone have a better solution? 

    Side note - would be lovely to be able to set the ring time from the incoming call handling page too. 
×
×
  • Create New...