> > --- Steve Langstaff <[EMAIL PROTECTED]> wrote: > > > I don't know about the 1.4 source, but in 1.2 I > > guess you would have to > > add some more code to > > > > handle_response_peerpoke() > > > > to handle the case where you got a 486 response from > > the peer. > > ok thanks, so that just seems to confirm that Asterisk > 1.2 DND's behavior can't be modified/customized > without patching the source code. I might forward this > issue to asterisk-devel. >
What do you mean modified/customized exactly? If you mean can you know whether a device has DND enabled or not before sending a call then no, even an OPTIONS packet won't tell you that. You send a call, they reject (and sometimes they even use a response code that doesn't indicate it's DND). Same goes for call forwarding. You send a call, they reject saying "go here instead". Joshua Colp Software Developer Digium, Inc. _______________________________________________ Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
