[Yealink external Custom Config File URL]

Ohh man... OK

We will reboot and let you know. Thanks

 

[Yealink external Custom Config File URL]

We have the same header in ours files as well, and other settings relevant to BLF and speedials etc...

What's stranger is that the BLF's were actually removed from the phones, but it did not affect any sidecars with customers that use them. The sidecars remained configured as before.

[Yealink external Custom Config File URL]

@Logicwrath

Thanks for the reply. I had checked the webserver logs and can see 200 OK responses on the GET requests for the files. 

What does your .cfg file look like? I believe mine are OK since I manually upload them via GUI and the BLF keys are updated immediately on the phone.

[Yealink external Custom Config File URL]

Hello,

Anyone using this function? We use it to quickly setup BLF linkeys. However today the phones suddenly stopped using the file.

This morning our Yealink customers reported that their BLF keys disappeared. We have tried many different troubleshooting scenarios but the phones seem to simply ignore the external config file altogether. We have had to manually add the BLF keys to the phones which seems to work.

We have confirmed that file access is working. 

Anyone else experiencing the same issue?

Thanks.

[Polycom VVX series BLF with directed call pickup]

Little update. Looks like I got it working. I had to do make 2 changes, one on the backend, and another in the phones config.

I created a callfow for group_pickup_feature with a regex as follows:

{
  "data": {
    "name": "Directed Call Pickup *7+{ext}",
    "patterns": [
      "^\\*7([0-9]+)$"
    ],
    "flow": {
      "module": "group_pickup_feature",
      "data": {
        "type": "extension"
      }
    }
  }
}

 

I then added call.directedCallPickupString="*7" in the config file for the device.

 

This approach kinda sucks cause it means I need to add the config file URL for each device that needs this feature instead of simply using the "Feature Keys" tab of Advanced Provisioner.

[Polycom VVX series BLF with directed call pickup]

Hey guys, anyone figure out how to get Polycoms to play nice with directed call pickup? When a monitored ext is ringing, pressing the linekey initiates a new call to the user instead of picking up the call.

We are using 2600Hz Advanced Provisioner and have tried linekey settings both "normal" and "automata", neither work.

Anyone got this working?

Thanks.

[obihai 302]

Thanks Plau. We are using the ITSP portal to manage our Obiohai devices. I'll give your instructions a try!

Do you know if the Obihai 302 ATA's can be made to use NAPTR/SRV records?  I have not been able to get a device to register unless we use an A record in the OutboundProxy field.

[account inheritance]

Now it makes a little more sense. Thank you Plau. I will have a look again based on this new understanding and report back any issues.

Have a great one!

[account inheritance]

Hi Plau,

Thanks for taking the time to answer! My case is that of Reseller 1 --> Reseller 2 --> Account(s). Does that mean that NO inheritance takes place? Or that I would have to make changes on Reseller 2 for changes to be made on all sub-accounts?

We have a setup as follows: superDuperAdmin --> Master Reseller --> Reseller 1 --> Account(s)

                                                                                                                       --> Reseller 2 --> Accounts(s)

                                                                                                                       --> Reseller 3 --> Account(s)

and so on......

 

I don't recall WHY we added the Master Reseller in between all actual Resellers, but is that a poor choice in general? Can they all be moved directly underneath superDuperAdmin if needed?

Thanks again!

[account inheritance]

Hey Tim,

We have our own cluster and are using 2600Hz's AP. I would have assumed that provisioner files for our cluster were stored separately from other clusters. If not, I fail to see why we have access to those settings at the top level, since sharing basic config files would not allow for any changes to be made and propagate down to the accounts.

We do in fact use custom config files for Polycom and Yealink devices, however they cannot be applied to an entire account, but rather at the device level only.

It appears as though it's an inheritance issue?

[account inheritance]

Hello,

Does anyone know if Provisioner account inheritance settings supposed to trickle down from a Reseller level? They only seem to take effect at the account level.

For example, at the Reseller level we've set the voicemail code to *98 instead fo the default *97. It does not update all the subaccounts under that Reseller. Setting it at the specific account level does set it for the entire account, but we would like it to be more of a global setting if possible.

We also tried to set it at the master account level, but it does not trickle down. If the field is left blank, we see "Inherits *97 from the Defaults"

Is this intended behavior?

Is there any way to change it globally?

Thanks y'all!

[provisioner timeout]

@esoare

Thanks for suggestion buddy. We got it sorted. They unblocked the IP.

I had thought about tethering but we needed the office to have access to provision more phones.

Have a good one!

[provisioner timeout]

Hey,

We had a phone in our office that had messed up firmware so it kept rebooting and trying to provision. Since then we get a timeout when trying to access the provisioner app. 

I heard the 2600hz ban is only for 1 hour, but we still cannot access the provisioner after 24hrs. 

Who do we contact for this issue? We were told that provisioner does not come with support, so we would need to use the forums.

Can someone form 2600hz advise?

Thank you.

[NAPTR/SRV records with AP]

Hello,

While working on proper phone failover using Advanced Provisioner, I stumbled on this thread: https://forums.2600hz.com/forums/topic/1491-please-consider-adding-the-auto-provision-server-url-to-the-provisioner-app/?page=2

We have a cluster with 2 zones (east and central). The issue with the solution in the referenced thread from what I can see is that it assumes the proxy is completely offline. What happens in the event that say rabbit is down in the zone, but the proxy is up? The phone will receive a response from the proxy, but will not be able to register in the current zone. Using only one provisioning URL will likely not result in the phone trying the failover URL even though it is configured in DNS using NAPTR/SRV.

We currently use AP from 2600 but aren't sure how to properly configure our NAPTR/SRV records for failover to the other zone if the phone is only provisioned with one URL, and rabbit goes offline?

This use case also touches on GEO-DNS. how do you configure GEO-DNS with AP? If you set both proxy URLs in AP (one from each zone) then you defeat GEO awareness since this is fixed at the UA or account level.

Any thoughts or suggestions?

[obihai 302]

Hey guys, omitting obi from the provisioning string did not work. We are provisioning them manually for now, but I would love to get this figured out so we don't have as many steps to provision. 

Anyone have any suggestions?

Thanks.

[Custom config for BLF on Yealink T48G]

@esoare

Yup, thats the place.

[Custom config for BLF on Yealink T48G]

Actually you can export .cfg files as well.

I got it working with a .cfg file by upgrading the firmware on the phone oddly enough.

I've tried looking at their .bin files in the past. I was not able to.

[Custom config for BLF on Yealink T48G]

Hey guys,

Anyone know how to use a custom config URL with Yealink phones? We use them with the Polycoms for the sidecars and BLF management, but this doesn't seem to work on the Yealink phones.

We tried with a custom.cfg file.

Thanks for any advice!

[group paging after being provisioned]

Hi Darren,

Thanks for the reply. Nothing wrong with the Advanced Callflows app.

My mistake was creating a regular group within SmartPBX, and expecting to use it as a paging group. Doesn't seem to work well as a page group. It works just fine as a ring group.

 

[group paging after being provisioned]

OK so I answered my own question. I came across an old Admin Guide on Atlassian that explicitly says "You may get unexpected results if you try to intercom a menu or a ring group."

The guide can be found here:  https://2600hz.atlassian.net/wiki/spaces/docs/pages/4194434/Intercom

What I ended up doing was creating a new callflow for a Ring Group, using the callflows app. Works beautifully.

[group paging after being provisioned]

Hey guys,

This may seem a little off topic, but it seems that once we provision Polycom devices (VVX 400 in this case) using AP, we are not able to page a group of phones. Only one of the phones in the group actually picks up the call. We can see the other phones ringing for a split second, but they never answer the call.

We created the group in SmartPBX and added the users to it, and gave it an extension number.

Direct paging (intercom) works fine to any phone.

Anyone else see similar behavior?

Thanks in advance!

 

[Notify When Device Becomes Unregistered]

Hey @SPC-Tim

Thanks for the suggestion. Familiar with that setting. Trying to avoid having to do it per-device.

Thanks buddy.

 

[Notify When Device Becomes Unregistered]

Hey Karl,

Thanks for the tip. We like having that feature on, but I suppose we can disable it during initial provisioning, then RE-enable.

 

[Notify When Device Becomes Unregistered]

Hey guys,

Is there any way of disabling the "Notify when unregistered" option on provisioned devices? This seems to be enabled on ALL phones that are provisioned with AP and I have not found a way to have it disabled for provisioned devices.

It gets really annoying receiving tons of emails as we provision customer devices.

Any suggestions?

Thanks in advance!

Amit

[Cisco SPA 504G provisioner bug?]

Hi Tuly,

Thanks for the confirmation.