I think I can give a slightly longer reply now, but the answer is still SMDI
(Station Messaging Desk Interface)

You have identified one of the challenges of interfacing with a proprietary
PBX, namely: how do I know where the call was redirected from? 

The other trick is turning on message waiting lamps.

This is what SMDI was invented for, and Asterisk only just recently has been
provided with an SMDI interface (it was a bounty for several years -
somebody finally wrote something late last year, and if you check it out in
the bug tracker you'll see that there's a fair amount of positive interest
in it).

Your PBX needs to support SMDI, and if it does not (can you say Nortel?),
you'll need a gateway of some sort such as Intel's PIMG or CTLs PBXLink. I
do not think anyone has actually integrated an Asterisk with SMDI yet, so
this is not for the faint of heart. Give us six months (<shameless plug>or
give us a call and we'll help you make it happen</plug>). John Todd and I
have been chatting about this a fair bit recently; this is really exciting
for the legacy telecom folks among us.

If you want to be on the bloody-edge, this is the ticket! SMDI support in
Asterisk is positioned to be a killer app, because a lot of old voicemail
systems are showing signs of impending death, and folks are loath to buy in
to another round of proprietary hell.

Jim.

--
Jim Van Meggelen
[EMAIL PROTECTED]
http://www.oreillynet.com/pub/au/2177

"A child is the ultimate startup, and I have three. This makes me rich."
                    Guy Kawasaki

-- 

> -----Original Message-----
> From: Graham Todd [mailto:[EMAIL PROTECTED] 
> Sent: January 31, 2006 12:16 PM
> To: [email protected]
> Subject: [on-asterisk] Asterisk as answering machine with existing PBX
> 
> == Automatic recognition of call origin and pass thru to a 
> voicemail box ==
> 
> This query has more to do with an issues of "stealth" 
> introduction of */PBX to "complement" an existing system than 
> with a asterisk issue per se ...
> 
> Someone asked me if they could set their phone to forward 
> calls to an Asterisk server plugged into an extension on the 
> existing PBX. Forwarded messages would get recorded/saved on 
> * and then e-mailed to them instead of being saved on the 
> current PBX (which either doesn't have this feature or 
> doesn't have it turned on).
> 
> Can I get Asterisk to automatically recognize incoming calls 
> by their extension number on the foreign PBX and to associate 
> the calls with one of its own voice mailboxes?  Is this easily done?
> 
> Since the forwarded calls would come from another extension 
> on the current PBX, I guess what I want is LookupCIDName() to 
> associate the forwarded call with the extension number that 
> **received** it from the outside; and then to store the 
> message in the Asterisk vmailbox that I would create for each 
> of the foreign PBX extensions. I am having trouble working 
> things out. Perhaps because:
> 
> - when forwarding the existing PBX strips CID info;
> - the CID info comes from the external call and not the 
> foreign PBX extension
> - some other random switch needs to be flipped on the existing PBX
> 
> Are other folks doing this?  Am I on the right track? :)
> 
> Thanks for any ideas.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 267.14.23/243 - Release 
> Date: 27/01/2006
>  
> 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.0/249 - Release Date: 02/02/2006
 

Reply via email to