SIP Option vmexten per Device

[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.

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?

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.

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.

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.

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?

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

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.

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