[Asterisk-Users] Call Manager & Asterisk for VM - MWI not working

[info at beprojects.com]

Like some other people on here, I am trying to integrate Asterisk for VM 
with CCM version 3.x.  I've got gnugk and Asterisk running, I've got CCM 
registering with the GK, I've got the voicemail pilot and profiles 
setup.  A call comes into a CCM phone, it rings, rolls to the correct VM 
on ASterisk and asterisk emails the voicemail and I can check the 
voicemail, but I cannot get MWI to work at all.  I'm using Shaun's 
script below:

root at Claven /etc/asterisk# more vm.sh
if [ $3 -gt 0 ]; then
# TURN LITE ON
CALLFILE=$(cat <<-EOF1
Channel: Local/11$2
MaxRetries: 1
# Retry in 2 min
RetryTime: 120
WaitTime: 45
Context: default
Extension: s
Priority: 1
EOF1)
echo "$CALLFILE" >> "/var/spool/asterisk/outgoing"/$(date +%Y%mNaVI%M%S)-$1

else
# TURN LITE OFF
CALLFILE=$(cat <<-EOF1
Channel: Local/00$2
MaxRetries: 1
# Retry in 2 min
RetryTime: 120
WaitTime: 45
Context: default
Extension: s
Priority: 1
EOF1)
echo "$CALLFILE" >> "/var/spool/asterisk/outgoing"/$(date +%Y%mNaVI%M%S)-$1
fi


I changed it to 11EXT and 00EXT because it made more sense to use 11 to 
turn on MWI and 00 to turn it off.  Within extensions.conf, I have:

exten => _00XXXX,1,SetCallerID(${EXTEN:2})
exten => _00XXXX,2,Dial(H323/8999 at 10.50.1.10)
exten => _00XXXX,3,Answer
exten => _00XXXX,4,Wait,1
exten => _00XXXX,5,Hangup

exten => _11XXXX,1,SetCallerID(${EXTEN:2})
exten => _11XXXX,2,Dial(H323/8998 at 10.50.1.10)
exten => _11XXXX,3,Answer
exten => _11XXXX,4,Wait,1
exten => _11XXXX,5,Hangup

8998 and 8999 are the MWI on and off #'s.  10.50.1.10 is the Gatekeeper. 
  I'm kind of at a loss of what to try next.  Here is what I get with a 
h.323 debug and the * logs:

     -- User hung up
   == Spawn extension (default, 6088, 3) exited non-zero on 
'H323/ip$10.50.1.10:39817/11'
     -- Attempting call on Local/117757 at default for s at default:1 (Retry 1)
     -- Executing SetCallerID("Local/117757 at default-12a6,2", "7757") in 
new stack
     -- Executing Dial("Local/117757 at default-12a6,2", 
"H323/8998 at 10.50.1.10") in new stack
     -- Called 8998 at 10.50.1.10
Claven*C-- Received SETUP message
     -- Setting up Call
     --     Call token:  [ip$10.50.1.10:39823/7924]
     -- C   Calling party name:  []
     -- C   Calling party number:  [7757]
     --     Called  party name:  [8998]
     --     Called  party number:  [8998]
   == Starting H323/ip$10.50.1.10:39823/7924 at default,8998,1 failed so 
falling back to exten 's'
   == Starting H323/ip$10.50.1.10:39823/7924 at default,s,1 still failed 
so falling back to context 'default'
Jun  2 12:55:45 WARNING[1268]: pbx.c:1889 ast_pbx_run: Channel 
'H323/ip$10.50.1.10:39823/7924' sent into invalid extension 's' in 
context 'default', but no invalid handler
   == No one is available to answer at this time
     -- Executing Answer("Local/117757 at default-12a6,2", "") in new stack
     -- Executing Wait("Local/117757 at default-12a6,2", "1") in new stack
        > Channel Local/117757 at default-12a6,1 was answered.
   == Starting Local/117757 at default-12a6,1 at default,s,1 failed so 
falling back to exten 's'
   == Starting Local/117757 at default-12a6,1 at default,s,1 still failed 
so falling back to context 'default'
Jun  2 12:55:45 WARNING[1264]: pbx.c:1889 ast_pbx_run: Channel 
'Local/117757 at default-12a6,1' sent into invalid extension 's' in context 
'default', but no invalid handler
   == Spawn extension (default, 117757, 4) exited non-zero on 
'Local/117757 at default-12a6,2'
Jun  2 12:55:45 NOTICE[1264]: pbx_spool.c:242 attempt_thread: Call 
completed to Local/117757 at default


I am calling 7757.  The call works, it plays vm, I record the message 
and then hang up and I get the info above.  I see extension s in the 
script and it's referenced above, but I am not sure how extension s 
should be setup, or if it's even necessary.  I understand the theory of 
the script, but not the details of what exactly it is trying to do, so 
maybe that's my issue.  Note that Asterisk is NOT sending anything out 
"on the wire".  Packet captures show that it is not even trying to send 
out a call to lite the MWI.

Any thoughts or pointers?  Thanks.

Peder