Search results

Just to note: I can factory reset the yealink T29G, then reprovision it and the lights work correctly. When parked the green turns to red. But after a few minutes it stays green and never gives a red blf again, although it does park the call correctly

I noticed my parking lot lights are intermittent. Sometimes they are green, sometimes orange and other times they are green but do not turn red when I park a call. I went to the logs and see this: Is this affecting the issues and if so what would I do to correct 2020-01-17 16:55:11.013327...

Thank you for that link. After reading the link I still can't figure out how to edit the provision templates

Just the Yealinks - no luck on the Fanvil

Is there a way to move a Fusionpbx installation on Centos over to Debian or do I need to build a new instance from scratch on debian?

I noticed my "Provisioning Editor" option is missing under Advanced. How do I edit the templates now?

I did this and it fixed the issue: mkdir -p /var/cache/fusionpbx chown -R freeswitch /var/cache/fusionpbx

Incoming calls on the cli I see this message in red 2020-01-13 14:35:58.942617 [ERR] switch_cpp.cpp:1365 [cache] can not write file `/var/cache/fusionpbx/directory.102@abn2.npusa.us.03d1856c-3612-11ea-99c0-438b2ec4b200.tmp`...

I sure will. Maybe I can make someone elses life a little easier One other thing. Do you know the correct text and where in the config file to place this objective? Yealink T29G Programmable Keys Message Custom value = (whatever string I want) I can manually login after adding this to the...

That fixed it - now it is green when there is not a call on park and it turns red when a call is parked I wish they had put that in the fusionpbx docs. Thank you!

I have abandoned the Fanvil and now I am just trying to get the indicator lights to work properly on the Yealink T29G. I can get call parking to work with no issues - except for the lights. It should blink fast red when there is a call parked. There are NO lights blinking or lit up at all...

On the Fanvil, once you change the Category to LINE it greys out all other fields and won't let you select Call Park. Therefore that solution does not work on either the FAnvil or Yealink. I do appreciate you trying to help.

I have call parking working great on my Fanvil X5s The only issue is the indicator light never comes on . No green, No red. So the other party does not know which parking key to press. Functionality works just fine. It parks and picks up. Just no light. I tried it on my Yealink T29G and...

I apologize - I asked this question last year, and referenced my post from last year and figured it out. Thanks

When callers call in, there is a + sign on the front of the phone number. How do I strip this off so the callerID does not show the + sign?

What I have decided to do is just give my users a user login restricted to call blocking priveleges only and just let them login to Fusion and use the call block module. Yes, it would be easier to just press *32 but I can only get it to work if it direct dials an ext and not a ring group

Here is what I discovered. It work if my DID is pointed directly at an ext. If I point the DID at a ring group with an enterprise strategy, it does not work.

I tried replacing caller_id_number with effective_caller_id_number since that is what I used in the inbound route. That did not work either. Any ideas how to get the caller id number not be nil

I changed my inbound route dial plan to remove the + sign from all incoming calls on caller ID. Is this possibly affecting why the call block *32 is not working?

I feel like we are headed in the right direction. No luck yet but different results on line 188 1 -df52-495b-a283-2ce3b7109360 Dialplan: sofia/internal/2020@fpbx2.npusa.us:5060 Action set(record_in_progress=true) INLINE 2 b6b4cf18-df52-495b-a283-2ce3b7109360 EXECUTE [depth=0]...