<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV> My idea was to implement VoiceMail w/MWI for Third Pty SIP Softswitches (to be able to support MWI for endpoints registered on another SIP Softswitch). Hence I have changed the chan_sip.c (SIP code) to support that. The diff is present in the first email in this thread. I have not explored at the IAX protocol to support the same functionality.</DIV>
<DIV> </DIV>
<DIV> I guess if we implement using SIP, it would be generic and would work for other Asterisks as well. and we dont have to necessarily use IAX to support this...</DIV>
<DIV> </DIV>
<DIV> What does everyone think.....</DIV>
<DIV> </DIV>
<DIV>Thx,</DIV>
<DIV>Jay<BR><BR><B><I>Gil Kloepfer <astr-dev@kloepfer.org></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Well, I got into this discussion a little late (unfortunately, I<BR>don't have a lot of time to read the mailing lists these days)...<BR>but I, too, have an immediate need for being able to get phones<BR>registered on one Asterisk PBX to get MWI from the voicemail system<BR>on another Asterisk PBX.<BR><BR>What I thought would be a good idea would be to somehow extend IAX2<BR>to have a function to check the voicemail status for an extension on<BR>another PBX. Then I saw IAX_COMMAND_MWI in iax2.h and was confused,<BR>because there isn't anything about what it is actually for.<BR><BR>A high-level explanation of an idea I had was as follows:<BR><BR>1. Extend the 'mailbox=' option in all the .conf files to allow<BR>a syntax of IAX2/Path/Extension@Context - with the<BR>IAX2/Path portion optional (just as the @Context is now).<BR>This is easy because I don't think anything really checks
it<BR>at the .conf file parser level.<BR><BR>2. The mailbox= args are already passed verbatum to<BR>ast_app_messagecount and ast_app_has_voicemail in asterisk/app.c.<BR>These functions are already called periodically on a schedule by the<BR>various channel interfaces to light the MWI on the phones.<BR><BR>Modify these two functions to call a function within chan_iax2<BR>when requested through the extended mailbox= syntax to request<BR>a remote mailbox status.<BR><BR>3. The IAX2 remote MWI status request would actually call the<BR>ast_app_messagecount and ast_app_has_voicemail on the system<BR>receiving the request.<BR><BR>Architecturally this would work fine, at least for IAX2. I'm not<BR>sure whether this same idea could work via SIP or any other channel type.<BR>Since SIP is a notify rather than a polled request, this is probably<BR>not really applicable here (although it may be desirable to make it<BR>work).<BR><BR>The only implementation issue I saw was that when coding this
extension,<BR>app.c and chan_iax2.c are not present at the same time in some points<BR>while Asterisk is running (app.c is part of core Asterisk, and<BR>chan_iax2 is a module). My thought would be that app.c would define<BR>some function that would allow "registration" via a persistent (global?)<BR>variable containing the function to call for the IAX2 remote MWI request<BR>that app.c would use. When chan_iax2 loads and registers, one of the<BR>things it would do is register its remote MWI handler function with<BR>app.c (kind of like it does for other parts of Asterisk now).<BR><BR>The reason why I need this feature is because where I work we are<BR>intending to roll-out a large (approx. 1000 phones) implementation of<BR>Asterisk to replace our very old Nortel PBX and Octel Voice Mail system.<BR>We have one remote site and several buildings that we would like to<BR>equip with their own PBX (in the case of our on-campus buildings,<BR>we plan to have about a third of the phones be
analog phones/modems/etc.<BR>on channel banks and we'd rather put the channel banks onto a PBX in<BR>the network closet rather than pull T1 connections all the way back<BR>to a bunch of wct4xxp cards on a single central PBX or use MGCP). I'm<BR>also being asked for a certain level of redunancy (or at least a distributed<BR>system), and the voicemail's MWI is a deal-breaker issue right now.<BR><BR>I am seriously looking into making the changes to get the MWI through<BR>IAX2 to work, but would like to know if (1) someone else is doing this<BR>already, (2) what IAX_COMMAND_MWI is really for, and (3) if this is<BR>really the right way to do it.<BR><BR>The only other way I could see to do this would be to modify the<BR>two routines in app.c to be able to optionally call an external program<BR>and use the manager interface. I feel that's far too heavy-weight and<BR>not particularly scalable. It really looks like it should be part of<BR>an inter-PBX communication protocol, not hacked via
an external<BR>program and second protocol.<BR><BR>---<BR>Gil Kloepfer<BR>home: astr-dev@kloepfer.org / FWD: 413932<BR>work: gil@arlut.utexas.edu / FWD: 395683 (UT Applied Research Laboratories)<BR>_______________________________________________<BR>Asterisk-Dev mailing list<BR>Asterisk-Dev@lists.digium.com<BR>http://lists.digium.com/mailman/listinfo/asterisk-dev<BR>To UNSUBSCRIBE or update options visit:<BR>http://lists.digium.com/mailman/listinfo/asterisk-dev<BR></BLOCKQUOTE><p>__________________________________________________<br>Do You Yahoo!?<br>Tired of spam? Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com