This post is at: ForumGeneral Questions
7 posts / 0 new
Last post
dbenders
dbenders's picture
Joined: 2007/10/25
Points: 0

Will be nice to have here the current version number, I guess 5.0.43 and also information for the new releases that will come and when.

George
George's picture
Joined: 2007/10/31
Points: 0

we just noticed, not sure if it started with 5.0.43 or the one before it but one of the two versions seem to have broken the feature for Voice Mail settings / Mail box, it used the extension numbers voice mail NOT the one picked from the list..

same for the Voicemail retrieval Extension is also stuck on the default extension

anyone else seeming the same problems..?

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 320

George,

I could not recreate the problem.

Does it happen when User Extension is created, updated, or in both cases?

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

George
George's picture
Joined: 2007/10/31
Points: 0

I have edited the extension, deleted and created with and again with out its own mail box, maes no difference.. sip.conf for ext 801 (test ext)

[801-axint]

qualify=no

nat=yes

pickupgroup=12

callerid=George-Home <801>

context=from-inside-axint

canreinvite=no

vmexten=301

secret=LFWsER

username=801-axint

host=dynamic

subscribecontext=local-extensions-axint

callgroup=12

dtmfmode=rfc2833

type=friend

mailbox=301@default-axint

disallow=all

allow=ulaw

allow=alaw

allow=gsm

as you can see it shoulod be using and again checking 301, when a call it made and it goes to voice mail I see the following..

-- Executing [s@macro-Verizon-Userexten-Base:146] Dial("SIP/901-axint-00863eb0", "SIP/801-axint|20|rtT") in new stack

-- Called 801-axint

-- SIP/801-axint-0094f770 is ringing

-- Nobody picked up in 20000 ms

[Nov 1 00:11:45] NOTICE[16347]: cdr.c:434 ast_cdr_free: CDR on channel 'SIP/801-axint-0094f770' not posted

-- Executing [s@macro-Verizon-Userexten-Base:147] Goto("SIP/901-axint-00863eb0", "s-orig-NOANSWER|1") in new stack

-- Goto (macro-Verizon-Userexten-Base,s-orig-NOANSWER,1)

-- Executing [s-orig-NOANSWER@macro-Verizon-Userexten-Base:1] Goto("SIP/901-axint-00863eb0", "s-NA|1") in new stack

-- Goto (macro-Verizon-Userexten-Base,s-NA,1)

-- Executing [s-NA@macro-Verizon-Userexten-Base:1] GotoIf("SIP/901-axint-00863eb0", "0?s-exit|1") in new stack

-- Executing [s-NA@macro-Verizon-Userexten-Base:2] GotoIf("SIP/901-axint-00863eb0", "1?s-NA-VOICEMAIL|1") in new stack

-- Goto (macro-Verizon-Userexten-Base,s-NA-VOICEMAIL,1)

-- Executing [s-NA-VOICEMAIL@macro-Verizon-Userexten-Base:1] Answer("SIP/901-axint-00863eb0", "") in new stack

-- Executing [s-NA-VOICEMAIL@macro-Verizon-Userexten-Base:2] GotoIf("SIP/901-axint-00863eb0", "0?ringing") in new stack

-- Executing [s-NA-VOICEMAIL@macro-Verizon-Userexten-Base:3] VoiceMail("SIP/901-axint-00863eb0", "u801@default-axint") in new stack

-- Playing '/var/spool/asterisk/voicemail/default-axint/801/unavail' (language 'en')

as you can see 801 unavail was used..

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 320

Until we find a better way to keep everyone informed of changes I will be adding change log for all the releases here.

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 320

George,

This does look like a bug. Since we are allowing mailbox number to be different from the extension we have to make sure that we are not assuming that the mailbox matches an extension in other parts of the system - grr... I wonder if we should just restrict mailbox to be the same as the user extension - always?

Thanks for reporting,

Alex

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

George
George's picture
Joined: 2007/10/31
Points: 0

I'm not sure I'm following you

>> I wonder if we should just restrict mailbox to be the same as the user extension - always?

I work from the office and at home, managing 2 different mail box's is a pain, having 1 used for both extension as its currently designed to do would be best.

since we can't see the code I can't say what happened BUT it did work but seems to have stopped with (I'm guessing here) with updates to the voicemail retrieval extension which is a GREAT feature

Thanks

George