Ticket #3519 (closed Feature Requests: fixed)

Opened 3 years ago

Last modified 2 years ago

SIP Option vmexten per Device

Reported by: pwalker Assigned to: p_lindheimer
Priority: minor Milestone: 2.8
Component: Core - Users/Devices Version:
Keywords: Cc:
Confirmation: Need Feedback SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

For some cases (more than one user using a shared vm box) it would be nice to be able to set the "vmexten" per Device not only globally as since FreePBX 2.4.

Since FreePBX 2.4, vmexten is added to sip_general_additional.conf, but both Tickets #1048 and #1819 requested it per (SIP) device, i.e. it should be added in each device's section in sip_addional.conf. The default for the field could still be what is configured in

Change History

02/05/09 03:01:46 changed by pwalker

[sorry, unintantionally hit "Submit" too soon...] The default for the field could still be what is configured in the featurepanel (and maybe, the option in the device's section in sip_addional.conf could only be set if it's different from the default. I will try to create a patch for this for the most recent FreePBX version.

02/05/09 07:23:57 changed by p_lindheimer

  • confirmation changed from Unreviewed to Need Feedback.
  • type changed from Bugs to Feature Requests.

could you clarify why you need it different per device. Is there a reason you are having to call something other than the default voicemail access code as set in the featurecodes panel?

(follow-up: ↓ 7 ) 02/05/09 07:57:54 changed by pwalker

Scenario/Configuration (as per customer request):

  • Departement with 3 Extensions:
    • 120 Main (departement) number
    • 121 Alice
    • 122 Bob
  • 121 (Alice) and 122 (Bob), have a Follow Me configured which goes to vmu120 if no answer, both have no (personal) vm configured. So they both want to hear 120's VoiceMails? when they press the vm / mwi button on their phone. (You can configure the phones to subscribe that vm by setting "mailbox = 120@default".)

If I configure vmexten to *97 (globally, which is correct for other extensions/departements which do have a personal vm), Asterisk always will send the global vmexten ("Message-Account: sip:*97@server-ip") in the MWI SIP NOTIFY message ("Event: message-summary") This is a problem e.g. with snom phones using the configuration described above because the snoms will dial the "Message-Account" they got with the MWI message when you want to hear your vm. For Alice and Bob, this will lead to the vm asking for the extension of their vm.

Additionally, both Tickets mentioned above were requesting the same - vmexten to be set individually for each SIP Extension / device - but were closed after implementing it as a global / general setting.

02/05/09 14:27:19 changed by wiseoldowl

For a possible short term resolution to this problem, see http://www.freepbx.org/support/documentation/howtos/how-to-make-multiple-extensions-use-a-common-voicemail-box (note to p_lindheimer - that page is not accessible to me at the moment, otherwise I might clean up the formatting a bit). However, I will agree that FreePBX could possibly offer a bit better support for sharing a single voicemail box among a group of extensions.

02/05/09 19:29:11 changed by pwalker

The patch in Ticket #1819 should actually work, but I'd say that vmexten shouldn't be added for zap and iax(2) devices, cause as far as I know that'll only work for SIP.

02/05/09 21:58:48 changed by p_lindheimer

pwalker,

if I understand correctly then, you want to put something like *98120 into both Alice and Bob's vmexten setting so that they dial a specific box, is that correct?

(in reply to: ↑ 3 ; follow-up: ↓ 8 ) 02/05/09 22:11:42 changed by p_lindheimer

Replying to pwalker:

Additionally, both Tickets mentioned above were requesting the same - vmexten to be set individually for each SIP Extension / device - but were closed after implementing it as a global / general setting.

btw - in response to this, both were closed because they indicated (or appeared to indicate) they wanted to pass the vm access code in vmexten which the current system does (and meets meets the needs of the '99%' case), vs. indicating a need to pass something that may be different on different extensions - thus the reason to get this clarified.

Also - as an interim, you can add the following to sip_custom_post.conf if the above is what you are trying to accomplish:

[121](+)
vmexten=*98120

[122](+)
vmexten=*98120

(in reply to: ↑ 7 ) 02/06/09 03:49:21 changed by pwalker

Replying to p_lindheimer:

(and meets meets the needs of the '99%' case)

Totally agree with this.

Also - as an interim, you can add the following to sip_custom_post.conf if the above is what you are trying to accomplish:

Big Oooops! I didn't know the sip_custom_post.conf file and "(+)" syntax. My fault, sorry. This solution is okay for me, at least as an interim. But anyway, it would be nice to have vmexten in the GUI as we also have the mailbox option which (I would say) is also not needed set to be something other than the default in 99% of the cases.

08/18/09 17:20:34 changed by p_lindheimer

  • version deleted.
  • milestone changed from 2.6 to 2.7.

02/28/10 09:57:48 changed by p_lindheimer

  • milestone changed from Cut Line to 2.8.

05/20/10 14:13:31 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

(In [9657]) closes #3519 add optional vmexten field per device/extension