[Asterisk-Users] Dedicated * voicemail server

[Richard Alexander]

> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com [mailto:asterisk-users-
> admin at lists.digium.com] On Behalf Of Low, Adam
> Sent: Tuesday, December 02, 2003 9:47 AM
> To: 'asterisk-users at lists.digium.com'
> Subject: RE: [Asterisk-Users] Dedicated * voicemail server
> 
> > You could add an initial digit based on whether it was a busy or no
> > answer forward, use the extra digit to determine the message played
on
> > the VM server and just strip it back off to get the mailbox number.
> 
> > Email me direct if that isn't clear enough.
> 
> This is actually what I have at the moment, the prepend was an issue
> because I've tried to make the platform non-national specific so every
> mailbox has its full telephone number including country code. Instead
I am
> prepending but this makes things dirty and complicated. I was hoping
for
> some magical SIP option or something but I guess I'll proceed with the
> current setup.
> 
> 
> ********* DISCLAIMER *********
> 
> This message and any attachment are confidential and may be privileged
or
> otherwise protected from disclosure and may include proprietary
> information. If you are not the intended recipient, please telephone
or
> email the sender and delete this message and any attachment from your
> system. If you are not the intended recipient you must not copy this
> message or attachment or disclose the contents to any other person
> 
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users


If you always add the same number of digits and subtract the same number
of digits then there is no reason why the mailboxes can't have the E164
number associated with them. 

e.g. add #1 for Busy, #2 for No Reply and always strip 2 leading digits
at the receiving context after or at the routing decision. 

An alternative would be to use to different dial paths to the VM server.
Each path arrives in a different context. Each receiving context handles
a different forward scenario.