Fred,
I actually messed up my original post. I stated that I am placing my NOTIFY
messages directly in the ser FIFO. In reality I should have said I'm using
sipsak to send the message to ser just like any normal UA would.
In my asterisk file sip.conf I have the following:
[general]
register => vmserver:number4@sip01.mycompany.com/vmserver
So asterisk is a registered UA with ser. Doing this I assumed I could simply
use sipsak from the asterisk server to send NOTIFY messages to the ser box.
I can infact do this, becuase when I do so the "TO:" SIP UA crashes. That tells
me that everything is working, but my message is not 100% correct.
I also have the user extension configured in ser and asterisk and all is
working because I can leave voice mail and listen to voice mail normally. It's
just the MWI that is giving me grief.
Paul
--- Fred Tips <fred(a)callcarrera.com> wrote:
Do you have mailbox= in * under the sip peer ?
----- Original Message -----
From: "Java Rockx" <javarockx(a)yahoo.com>
To: <serusers(a)lists.iptel.org>
Sent: Friday, September 17, 2004 3:14 PM
Subject: [Serusers] Injecting SIP NOTIFY into ser FIFO
Hello everyone.
Can anyone tell me what I'm doing wrong? I am using Asterisk as a voice
mail
server for my ser SIP proxy. Everything works
fine expect the Message
Waiting
Indicator (MWI). I've read a few articles and
got some good feed back from
this
mailing list but here is my problem.
My NOTIFY message is crashing my SIP phone. Here is my setup. I'm using
"externnotify" in Asterisk to call a /usr/bin/mwi script that I wrote. All
this
script does is create file in /var/spool/mwi that
contains the
externnotify
information.
Then cron periodically processes the messages in /var/spool/mwi. By
process I
mean it will create the SIP NOTIFY messages and
place them directly in to
the
ser FIFO. The problem is when this happens the
SIP phone crashes.
Here is a sample of my NOTIFY message that my Asterisk server cron job is
sending to the ser FIFO. I wish there was a way to just have Asterisk
register
with the ser proxy and handle this
automatically.
Can anyone see a problem?
Regards,
Paul
--------------------------------------------------
NOTIFY sip:1002@sip01.mycompany.com SIP/2.0
Via: SIP/2.0/UDP 4.4.242.201:5060
From: "vmserver" <sip:vmserver@sip01.mycompany.com>
To: <sip:1002@sip01.mycomany.com>
Contact: <sip:vmserver@sip01.mycompany.com>
Call-ID: 5b8be1521efe68b5365a36466ad3b87(a)4.4.242.201
CSeq: 1101 NOTIFY
User-Agent: VoiceMail
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 38
Messages-Waiting: yes
Voicemail: 13/0
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!