Not properly transferring to voicemail in FOP2
-
I am having an issue with transferring calls to voicemail using FOP2. We are using 4 digit extensions (5558 for example) but when I go to transfer to voicemail, it says "The person at extension 58 is I'm sorry. That is not a valid extension." and then it hangs up. Any assistance with getting this fixed would be appreciated.
-
If you use FreePBX, the extension prefix to transfer to voicemail is derived from MySQL tables set by FreePBX directly. It does not care if you have 4 or 10 digit extensions. Run this:
/usr/local/fop2/autoconfig-buttons.sh
inspect the output from one SIP/xxx extension, you will see a header named "extenvoicemail". consider its value, this is a sample definition:
[fixed][SIP/1604]
type=extension
extension=1604
label=John
mailbox=1604@default
context=from-internal
queuechannel=Local/1604@from-queue/n|Penalty=0|MemberName=John|StateInterface=SIP/1604
customastdb=CF/1604
extenvoicemail=*1604@from-internal
queuecontext=from-queue
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001[/fixed]How does extenvoicemail looks on your own config? Does it look correct? ( a prefix + extension number) ?
-
If you use FreePBX, the extension prefix to transfer to voicemail is derived from MySQL tables set by FreePBX directly. It does not care if you have 4 or 10 digit extensions. Run this:
/usr/local/fop2/autoconfig-buttons.sh
inspect the output from one SIP/xxx extension, you will see a header named "extenvoicemail". consider its value, this is a sample definition:
[fixed][SIP/1604]
type=extension
extension=1604
label=John
mailbox=1604@default
context=from-internal
queuechannel=Local/1604@from-queue/n|Penalty=0|MemberName=John|StateInterface=SIP/1604
customastdb=CF/1604
extenvoicemail=*1604@from-internal
queuecontext=from-queue
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001[/fixed]How does extenvoicemail looks on your own config? Does it look correct? ( a prefix + extension number) ?
-
Admin,
Thank you for your help. When we checked our settings, they were the same as your screenshot. After some further digging, we found that there was a feature code enabled *55 to disable intercom. Our extensions were 5500-5599. When we disabled the *55 feature code, it worked.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login