(RADIATOR) Reply Items in Access-Reject message?
Hello! How can I add some reply items in Access-Reject message? I need to return h323-return-code=cause to my IVR script, if user not exist in database. Thank you. Best regards, Rustam Povarov === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Reply Items in Access-Reject message?
On Mon, 3 Apr 2000, Richi Plana wrote: |o| How can I add some reply items in Access-Reject message? I need to |o| return h323-return-code=cause to my IVR script, if user not |o| exist in database. This is Cisco's problem: too little documentation. Too bad it's getting to the point where alternatives simply aren't feasible. 1) Make an entry in your dictionary file for the H323-Return-Code VSA attribute (Cisco's vendor code is 9) 2) All H323 VSA's should be return in the format: H323-attrib = "cisco-h323-attrib-id=value" ie. H323-Return-Code = "h323-return-code=0" BTW ... that's how attribs are passed by client to server, too. Thank you, but i know, how to reply Voice VSA'a to cisco :) I want to know, how to say RADIATOR reply this vsa's with Access-Reject message. With Access-Accept it works successfully. Best regards, Rustam Povarov P.S. Sorry for my poor english. === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Reply Items in Access-Reject message?
On Mon, 3 Apr 2000, Rustam Povarov wrote: |o| How can I add some reply items in Access-Reject message? I need to |o| return h323-return-code=cause to my IVR script, if user not |o| exist in database. This is Cisco's problem: too little documentation. Too bad it's getting to the point where alternatives simply aren't feasible. 1) Make an entry in your dictionary file for the H323-Return-Code VSA attribute (Cisco's vendor code is 9) 2) All H323 VSA's should be return in the format: H323-attrib = "cisco-h323-attrib-id=value" ie. H323-Return-Code = "h323-return-code=0" BTW ... that's how attribs are passed by client to server, too. L L Richi Plana 8^) ,-,-. ,-,-. ,-,-. ,-,-. ,- LL LL Systems Administrator / / \ \ / / \ \ / / \ \ / / \ \ / / L Mosaic Communications, Inc. \ \ / / \ \ / / \ \ / / \ \ / / L mailto:[EMAIL PROTECTED] `-'-' `-'-' `-'-' `-'-' === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Reply Items in Access-Reject message?
Hello Rustam, On Apr 3, 4:07pm, Rustam Povarov wrote: Subject: (RADIATOR) Reply Items in Access-Reject message? Hello! How can I add some reply items in Access-Reject message? I need to return h323-return-code=cause to my IVR script, if user not exist in database. Radaitor is not able to do that "out of the box". The only ways I could see of doing that would be: 1. Change the code. In Client.pm at about line 296: $rp-set_code('Access-Reject'); $rp-addAttrByNum($Radius::Radius::REPLY_MESSAGE, 'Request Denied'); $rp-addAttrByNum($Radius::Radius::REPLY_MESSAGE, $reason) if $self-{RejectHasReason}; # add this $rp-add_attr('H323-Return-Code', '"h323-return-code=0"'); $p-{Client}-replyTo($rp, $p); return; 2. Add a PostAuthHook that appends the H323-Return-Code, something like this (untested) PostAuthHooh sub {${$_[1]}-add_attr('H323-Return-Code', '"h323-return-code=0"');} Hope that helps. Cheers. Thank you. Best regards, Rustam Povarov === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- End of excerpt from Rustam Povarov -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, 2000, NT, MacOS X === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.