SNOM remote subscribe error retry

[mmeier]

Please add this or include options to customize this with the default SNOM config. We're finding in testing that certain situations with the current D7xx firmware will cause BLF subscriptions to fail. The default 600s retry time is far too long.

<retry_after_failed_subscribe perm="">5</retry_after_failed_subscribe>
<retry_after_failed_subscribe idx="1" perm="">5</retry_after_failed_subscribe>

 

[JohnS_3CX]

Hi @mmeier

Can you please elaborate on the situations you mentioned?

 

[mmeier]

Hi @mmeier

Can you please elaborate on the situations you mentioned?

Hi John,

The SNOM D7xx series phones when connected remotely will occasionally lose their BLF subscriptions. Phones are still registered (and ring!), but the BLF keys lose their light and display an X next to the text (normally a phone or other icon).

When I logged into the phone to troubleshoot I saw that the status showed a huge reconnect timer for the keys that failed. Searching SNOM's docs this value defaults to 600s. Setting this to 5s has made the problem go away with no other problems. I'm not sure what causes the subscription to break and have tried various other network settings, and even had a phone registered to FreePBX without the BLF issue. It may be a firmware thing. The 3cx VM is physically located in our Colo next door so it's not an internet problem.

Changing this value to 5s works, but now I have a custom phone template and 3cx is complaining about that. I was hoping this value could either be set in the default template, or made editable through settings.

Thanks,

 

[JohnS_3CX]

When you say connected remotely are we talking STUN specifically?

I think you should read this also and provide us with all the info so we can better understand the situation, before jumping ahead to editing the timers
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/