> -----Original Message----- > From: Matthew Boehm [mailto:mboehm@cytelcom.com] > Sent: Monday, October 18, 2004 12:11 PM > To: karlp@fortephones.com; Asterisk Users Mailing List - > Non-Commercial Discussion > Subject: Re: [Asterisk-Users] New Realtime config and MWI > > > Ah, yes. That function is supported in RealTime. In RealTime, > the database table contains 1 column for each possible > sip.conf configuration option. > > So yes, mailbox=333@context will be supported in RealTime SIP. > > MatthewI could be offbase here, but my understanding is that with Realtime you can set the mailbox variable by adding a column in the table. The problem comes from chan_sip if you take a look at the do_monitor method, which is the method that checks each peer and sends the mwi, it is only sending the MWI to peers listed in the in memory linked list peer1.peers. I do not see the code where the realtime config adds its peers to that linked list, if it did then the "realtime" data would be cached and not actually looked up as needed. I actually made a patch to ast_data a while back to add just this Functionality. Basically, it selected the records periodically (I think it was every 360 seconds) and added them to the linked list which made the mwi work. Just my $.02 worth, Robert Jackson
Hi all, I'm trying to put together a list of gear w/prices to implement an asterisk system. Does anyone know a good place to buy polycom phones? Their website isn't much help. Specifically looking for IP500 and IP600 phones. Thanks again! Sincerely, Jonathan Miller ACCS.net
Are you using chan_sip v1.538? Matthew ----- Original Message ----- From: "Robert Jackson" <RobertJ@promedicalinc.com> To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users@lists.digium.com> Sent: Monday, October 18, 2004 11:25 AM Subject: RE: [Asterisk-Users] New Realtime config and MWI> -----Original Message----- > From: Matthew Boehm [mailto:mboehm@cytelcom.com] > Sent: Monday, October 18, 2004 12:11 PM > To: karlp@fortephones.com; Asterisk Users Mailing List - > Non-Commercial Discussion > Subject: Re: [Asterisk-Users] New Realtime config and MWI > > > Ah, yes. That function is supported in RealTime. In RealTime, > the database table contains 1 column for each possible > sip.conf configuration option. > > So yes, mailbox=333@context will be supported in RealTime SIP. > > MatthewI could be offbase here, but my understanding is that with Realtime you can set the mailbox variable by adding a column in the table. The problem comes from chan_sip if you take a look at the do_monitor method, which is the method that checks each peer and sends the mwi, it is only sending the MWI to peers listed in the in memory linked list peer1.peers. I do not see the code where the realtime config adds its peers to that linked list, if it did then the "realtime" data would be cached and not actually looked up as needed. I actually made a patch to ast_data a while back to add just this Functionality. Basically, it selected the records periodically (I think it was every 360 seconds) and added them to the linked list which made the mwi work. Just my $.02 worth, Robert Jackson _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
> -----Original Message----- > From: Matthew Boehm [mailto:mboehm@cytelcom.com] > Sent: Monday, October 18, 2004 12:52 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] New Realtime config and MWI > > > Are you using chan_sip v1.538? >Only on my test/development machine, but I do not think that this issue has been addressed. Again, I could be way off, but I just don't see where the in memory linked list is updated with the realtime peer. I can only think of two methods for MWI to work in it's current structure you would need to either add the peers to the memory linked list or select all records from the ODBC source each time you evaluate whether or not to send a MWI notification. At one time I looked at changing the structure a bit and using the builtin astdb to store some of the peer data in regards to the last notification sent and whatnot so that the main info could be added to the db when a lookup is done and the MWI's could be generated from that, but I didn't have the time to really look into it fully. I am sure that there are better ways around this, but these are just the ones that I came up with. Robert Jackson