Ticket #436 (assigned Feature Requests: None)

Opened 6 years ago

Last modified 3 years ago

personalize hints for custom devices

Reported by: vregnard Assigned to: nobody (accepted)
Priority: minor Milestone: Undetermined
Component: Core - Users/Devices Version:
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description (Last modified by p_lindheimer)

When defining some custom devices, freepbx
automatically associate a hint for the extension. This
causes some trouble when we use these custom device to
reach some remote phones like mobile phones or remote
collaborators with a local user extension.

Exemple:
I define a device extension for a mobile phone, in the
GUI (admin/setup/device/custom), I associate the device
to a user extension (let say 804) and I define de dial
extension in the dial field: "IAX2/TRUNKNAME/PHONENUMBER".

I then automatically have a hint wich maps the given
dial  extension in the [ext-local] context
(extensions_additional)

exten => 804,1,Macro(exten-vm,novm,804)
exten => 804,hint,IAX2/TRUNKNAME/PHONENUMBER

But in this particular case, it is really cumbersome,
and does not work. Extension is always unavailable. I
would prefer to have something like that:

exten => 804,1,Macro(exten-vm,novm,804)
exten => 804,hint,IAX2/TRUNKNAME

to associate the availability of the user to the trunk
availability itself. Modifying it by hand works great
actually. But at this stage there is no way to override
the default config from the GUI (which is restored
after every reloadconfig). That would be a very nice
feature to have it permanently ? We could imagine a
field in the device configuration page to allow to
specify the hint for every device and default to the
present behaviour.

Another interesting possibility to avoid the rewrite of
the custom modifications is to put the hint config for
device extensions in the SQL DB.

Thanks for your comments

Change History

04/06/06 12:40:51 changed by stevenberkholz

I think I have found the workarround for this.

just leave the line as IAX2/TRUNKNAME in the dial field.

I was troubleshooting the same issue for a bunch of extensions on a legacy PBX over a PRI.

It looks like the extension portion is taken care of my the macro, and does not need to be hardcoded onto the dial field in the gui.

Actually, this only works for me because I have the same extension number in asterisk and the legacy PBX. (I just reread your post)

Hopefully this info helps someone, if not you.

07/24/08 16:06:02 changed by p_lindheimer

  • confirmation set to Confirmed.
  • description changed.
  • component changed from Web interface to Core - Users/Devices.
  • engine_version changed.
  • svn_rev changed.
  • version deleted.
  • milestone set to 3.0.

probably a good candidate to evaluate when looking at revamping devices/users stuff.

08/22/09 19:12:09 changed by p_lindheimer

  • milestone changed from 2.6 to 2.7.