(RADIATOR) Cisco AS5300 / Voip / h323-credit-time
We're trying to get Radiator to send back the h323-credit-time pulled from a MySQL database. It does, but it sends back a pair of replies which look like this: cisco-h323-credit-time = 10 cisco-h323-credit-time = h323-credit-time=10 The second line is what is required by Cisco. The first line is also sent back by Radiator, and it breaks the Cisco. Apparently, the StripFromReply verb will strip BOTH out. Can't find a way to AddToReply AFTER stripping the offending line out. Is ANYONE out there doing Cisco AS5300, VoIP and MySQL (or any database) and Radiator? Please help. Thanks. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Cisco AS5300 / Voip / h323-credit-time
Hello - On Thu, 13 Dec 2001 13:16, Office Staff wrote: We're trying to get Radiator to send back the h323-credit-time pulled from a MySQL database. It does, but it sends back a pair of replies which look like this: cisco-h323-credit-time = 10 cisco-h323-credit-time = h323-credit-time=10 The second line is what is required by Cisco. The first line is also sent back by Radiator, and it breaks the Cisco. Apparently, the StripFromReply verb will strip BOTH out. Can't find a way to AddToReply AFTER stripping the offending line out. Is ANYONE out there doing Cisco AS5300, VoIP and MySQL (or any database) and Radiator? I will need to see a copy of the configuration file (no secrets), but you should know that the AddToReply happens *after* the StripFromReply. regards Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Cisco AS5300 VoIP / Radiator
...One interesting thing to
note is that the AS5300 seems to be sending a null User-Name
("") when they use account/PIN.
That seems odd to me. After the initial "pre-authentication", as the
documents suggest, ours prompts for an Account Number and PIN, and the
Gateway plugs them into the RADIUS Username and Password attributes,
respectively.
However, you can probably get this behavior to be anything you want based on
what IVR script you select in the Gateway...
Dave
===
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.
(RADIATOR) Cisco AS5300 VoIP / Radiator
Hi,
We're trying to setup Radiator to work with our Cisco AS5300 to do Voice over IP.
We have things (basically) working, it will authenticate off of caller ID, etc. But,
there are a few extras we'd like to do and need some advice on.
First, has anyone used Simultaneous-Use with the AS5300 using account numbers and
PINs? For example, Joe User dials in, enters an account number, a PIN, and makes a
call. Let's say his wife picks up the phone at some other location, dials in, and
enters the same account number and PIN. It shouldn't let her use it if he's already
on. One interesting thing to note is that the AS5300 seems to be sending a null
User-Name ("") when they use account/PIN.
Second, whenever multiple users are dialed into the unit, only one user is
showing up in the online user database. I have the radwho.cgi setup to work with it,
and it only shows one entry in the database. We are just using a standard DBM
database file for now, until we get things working, at which point we'll migrate it to
something better.
If anyone has any ideas that may help, it would be appreciated.
Thanks. :)
Jeremy
===
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.
(RADIATOR) Cisco AS5300 ISDN Ports
Has anyone ever had any luck getting Radiator to talk SNMP with an AS5300 with ISDN, that gives high port numbers (200xx) for the NAS-Port? The normal MIB (.1.3.6.1.4.1.9.2.9.2.1.18) works fine for analog (Async) calls, but when an ISDN call comes in and arrives on a high port number, the SNMP get fails and all heck breaks loose. Anyone else had this problem? - D [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) Cisco AS5300 ISDN Ports
Hello David - On Tue, 17 Oct 2000, David Lloyd wrote: Has anyone ever had any luck getting Radiator to talk SNMP with an AS5300 with ISDN, that gives high port numbers (200xx) for the NAS-Port? The normal MIB (.1.3.6.1.4.1.9.2.9.2.1.18) works fine for analog (Async) calls, but when an ISDN call comes in and arrives on a high port number, the SNMP get fails and all heck breaks loose. You might want to check the archive mentioned below. regards Hugh === 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. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. Available on Unix, Linux, FreeBSD, Windows 95/98/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.
Re: (RADIATOR) Cisco AS5300 authen OK autho FAIL
Hello, This is probably due to your user definition above, which for a Cisco should include a Service-Type = Framed-User reply item. Cisco's are very picky about this. There have been several discussions about this on the list and you should be able to find the references on the archive site. Eeks sorry, i had been browsing around the last three months of archive, but hadn't found anything pointing to that. (and i had the idea that i put that statement in the default reply items) It actually doesn't complain about the appropriate type anymore, but now it whines about this : --snip-- 4d21h: Se0:0 AAA/AUTHOR/LCP: Processing AV interface-config=ip address 192.168.121.133 255.255.255.224 --snip-- 4d21h: Vi1 AAA/AUTHOR/FSM: (0): LCP succeeds trivially --snip-- 4d21h: Vi1 AAA/AUTHOR/FSM (2029435040): Method=radius (radius) 4d21h: RADIUS: cisco AVPair "lcp:interface-config=ip address 192.168.121.133 255.255.255.224" not applied for ip 4d21h: Vi1 AAA/AUTHOR (2029435040): Post authorization status = PASS_REPL 4d21h: Vi1 AAA/AUTHOR/FSM: We can start IPCP 4d21h: Vi1 AAA/AUTHOR/IPCP: Start. Her address 192.168.240.22, we want 0.0.0.0 --snip-- "not applied for ip".. i'm digging into that rightnow.. Greets, Nils Swart - [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.
(RADIATOR) Cisco AS5300 authen OK autho FAIL
Hi! (Short summary: normal dialin works fine, avpair statements get rejected by the AS5300 due to 'no appropriate authorization type for user' error) Our setup is an AS5300 together with Radiator 2.16alpha (maybe the version numer is the problem, but hey, living on the edge rules right ? :) I try to dial in with a single ISDN channel, which works out fine. Until i try to add authorization parameters (avpairs) The radiator config is more then standard, and it does everything the AS5300 asks for, but for some odd reason the AS5300 isn't happy with the AVPair statements: user1 User-Password="blerk" Framed-Protocol = PPP, Framed-Netmask = "255.255.255.255", cisco-avpair = "lcp:interface-config:ip address 192.168.121.133 255.255.255.224" The cisco has (among other aaa stuff, but these apply): aaa authentication ppp use-radius if-needed local group radius aaa authorization network default group radius Which gives me: ---snip(begin of authentication sequence)--- 4d00h: Attribute 18 45 2757656C 4d00h: RADIUS: saved authorization data for user 61BF1698 at 61C0713C 4d00h: AAA/AUTHEN (327552900): status = PASS 4d00h: Se0:0 AAA/AUTHOR/LCP: Authorize LCP 4d00h: Se0:0 AAA/AUTHOR/LCP (2298034002): Port='Serial0:0' list='' service=NET 4d00h: AAA/AUTHOR/LCP: Se0:0 (2298034002) user='user1' 4d00h: Se0:0 AAA/AUTHOR/LCP (2298034002): send AV service=ppp 4d00h: Se0:0 AAA/AUTHOR/LCP (2298034002): send AV protocol=lcp 4d00h: Se0:0 AAA/AUTHOR/LCP (2298034002): found list "default" 4d00h: Se0:0 AAA/AUTHOR/LCP (2298034002): Method=radius (radius) 4d00h: RADIUS: cisco AVPair "lcp:interface-config=ip address 192.168.121.133 255.255.255.224" 4d00h: RADIUS: no appropriate authorization type for user. 4d00h: Se0:0 AAA/AUTHOR (2298034002): Post authorization status = FAIL 4d00h: Se0:0 AAA/AUTHOR/LCP: Denied 4d00h: AAA/MEMORY: free_user (0x61BF1698) user='user1' ruser='' port='Serial0:0' rem_addr='102889955/102450977' authen_type=PAP service=PPP priv=1 4d00h: Se0:0 AAA/AUTHOR/FSM: (0): LCP succeeds trivially ---snip--- Ofcourse Radiator gives it's OK to the question of the NAS about the authorization stuff, but why is the NAS rejecting it nevertheless with 'no appropriate authorization type' ??? Anyone ? Thanks in advance ! Greets, Nils Swart - [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) Cisco As5300 and VOIP and Debit card
On Tue, 7 Mar 2000, Mark Jenks wrote: Has anyone used Radiator to send back the credit amount and credit time and return code in vsa's for the Cisco debit card platform ? We use an As5300 and are currently authing using radiator 2.15. The Cisco radius debug says the pair is an invalid format for type 26, 26 referring to vendor specof attribute I presume. We send and have defined in our dictionary : vendorattr 9 Credit_Amount 101 string Radius handles it OK, the AS5300 does not. Help dictionary # Cisco Voice Extensions # NAS to RAS VENDORATTR 9Cisco-Voice-RemoteGatewayID 23 string VENDORATTR 9Cisco-Voice-ConnectionID24 string VENDORATTR 9Cisco-Voice-SetupTime 25 string VENDORATTR 9Cisco-Voice-CallDirection 26 string VENDORATTR 9Cisco-Voice-CallType27 string VENDORATTR 9Cisco-Voice-ConnectTime 28 string VENDORATTR 9Cisco-Voice-DisconnectTime 29 string VENDORATTR 9Cisco-Voice-DisconnectCause 30 string VENDORATTR 9Cisco-Voice-VoiceQuality31 string VENDORATTR 9Cisco-Voice-IVROutAVpair32 string VENDORATTR 9Cisco-Voice-GatewayName 33 string VENDORATTR 9Cisco-Voice-CallTreatment 34 string # RAS to NAS VENDORATTR 9Cisco-Voice-IVRInAVpair 100 string VENDORATTR 9Cisco-Voice-CreditAmount101 string VENDORATTR 9Cisco-Voice-CreditTime 102 string VENDORATTR 9Cisco-Voice-ReturnCode 103 string VENDORATTR 9Cisco-Voice-PromptID104 string VENDORATTR 9Cisco-Voice-TimeOfDay 105 string VENDORATTR 9Cisco-Voice-RedirectNumber 106 string VENDORATTR 9Cisco-Voice-PreferredLanguage 107 string VENDORATTR 9Cisco-Voice-RedirectIPAddress 108 string VENDORATTR 9Cisco-Voice-BillingMode 109 string VENDORATTR 9Cisco-Voice-CurrencyType110 string users - 1122334455Password = "6677" Service-Type= Login, Cisco-Voice-CreditAmount= "h323-credit-amount=10.00", Cisco-Voice-CreditTime = "h323-credit-time=600" - Best Regards Archer === Archive at http://www.starport.net/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Fwd: Re: (RADIATOR) Cisco As5300 and VOIP and Debit card (fwd)
Hello all - Here are some useful Cisco attributes for VOIP. cheers Hugh -- Forwarded Message -- Subject: Re: (RADIATOR) Cisco As5300 and VOIP and Debit card (fwd) Date: Tue, 7 Mar 2000 09:59:46 +0100 (CET) From: Rustam Povarov [EMAIL PROTECTED] Hello! I post this to list, but can't see result. Repost this please, if my message not delivered. Sorry for my english. Best regards, Rustam Povarov -- Forwarded message -- Date: Tue, 7 Mar 2000 09:36:15 +0100 (CET) From: Rustam Povarov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: (RADIATOR) Cisco As5300 and VOIP and Debit card On Tue, 7 Mar 2000, Mark Jenks wrote: Has anyone used Radiator to send back the credit amount and credit time and return code in vsa's for the Cisco debit card platform ? We use an As5300 and are currently authing using radiator 2.15. The Cisco radius debug says the pair is an invalid format for type 26, 26 referring to vendor specof attribute I presume. We send and have defined in our dictionary : vendorattr 9 Credit_Amount 101 string Radius handles it OK, the AS5300 does not. Help dictionary # Cisco Voice Extensions # NAS to RAS VENDORATTR 9Cisco-Voice-RemoteGatewayID 23 string VENDORATTR 9Cisco-Voice-ConnectionID24 string VENDORATTR 9Cisco-Voice-SetupTime 25 string VENDORATTR 9Cisco-Voice-CallDirection 26 string VENDORATTR 9Cisco-Voice-CallType27 string VENDORATTR 9Cisco-Voice-ConnectTime 28 string VENDORATTR 9Cisco-Voice-DisconnectTime 29 string VENDORATTR 9Cisco-Voice-DisconnectCause 30 string VENDORATTR 9Cisco-Voice-VoiceQuality31 string VENDORATTR 9Cisco-Voice-IVROutAVpair32 string VENDORATTR 9Cisco-Voice-GatewayName 33 string VENDORATTR 9Cisco-Voice-CallTreatment 34 string # RAS to NAS VENDORATTR 9Cisco-Voice-IVRInAVpair 100 string VENDORATTR 9Cisco-Voice-CreditAmount101 string VENDORATTR 9Cisco-Voice-CreditTime 102 string VENDORATTR 9Cisco-Voice-ReturnCode 103 string VENDORATTR 9Cisco-Voice-PromptID104 string VENDORATTR 9Cisco-Voice-TimeOfDay 105 string VENDORATTR 9Cisco-Voice-RedirectNumber 106 string VENDORATTR 9Cisco-Voice-PreferredLanguage 107 string VENDORATTR 9Cisco-Voice-RedirectIPAddress 108 string VENDORATTR 9Cisco-Voice-BillingMode 109 string VENDORATTR 9Cisco-Voice-CurrencyType110 string users - 1122334455Password = "6677" Service-Type= Login, Cisco-Voice-CreditAmount= "h323-credit-amount=10.00", Cisco-Voice-CreditTime = "h323-credit-time=600" - Best Regards Archer --- -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X. === Archive at http://www.starport.net/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Cisco As5300 and VOIP and Debit card
Mark, Make sure these are in your dictionary VENDORATTR 9 cisco-h323-remote-address 23 string VENDORATTR 9 cisco-h323-conf-id 24 string VENDORATTR 9 cisco-h323-setup-time 25 string VENDORATTR 9 cisco-h323-call-origin 26 string VENDORATTR 9 cisco-h323-call-type27 string VENDORATTR 9 cisco-h323-connect-time 28 string VENDORATTR 9 cisco-h323-disconnect-time 29 string VENDORATTR 9 cisco-h323-disconnect-cause 30 string VENDORATTR 9 cisco-h323-voice-quality31 string VENDORATTR 9 cisco-h323-ivr-out 32 string VENDORATTR 9 cisco-h323-gw-id33 string VENDORATTR 9 cisco-h323-call-treatment 34 string VENDORATTR 9 cisco-h323-ivr-in 100 string VENDORATTR 9 cisco-h323-credit-amount101 string VENDORATTR 9 cisco-h323-credit-time 102 string VENDORATTR 9 cisco-h323-return-code 103 string VENDORATTR 9 cisco-h323-prompt-id104 string VENDORATTR 9 cisco-h323-time-and-day 105 string VENDORATTR 9 cisco-h323-redirect-number 106 string VENDORATTR 9 cisco-h323-preferred-lang 107 string VENDORATTR 9 cisco-h323-redirect-ip-addr 108 string VENDORATTR 9 cisco-h323-billing-model109 string VENDORATTR 9 cisco-h323-currency-type110 string Regards, Matt At 03:43 PM 7/03/00 +1300, you wrote: Has anyone used Radiator to send back the credit amount and credit time and return code in vsa's for the Cisco debit card platform ? We use an As5300 and are currently authing using radiator 2.15. The Cisco radius debug says the pair is an invalid format for type 26, 26 referring to vendor specof attribute I presume. We send and have defined in our dictionary : vendorattr 9 Credit_Amount 101 string Radius handles it OK, the AS5300 does not. Help === Archive at http://www.starport.net/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. --- Matthew Nichols - Network/Systems Engineer CCNA HunterLink Pty Ltd Newcastle NSW Australia Phone: +61 2 4969 0122 Fax: +61 2 4969 0133 PGP Public Key: http://moonah.hunterlink.net.au/~matt/pgp/pgpkey.html HunterLink Web Site: http://www.hunterlink.net.au === Archive at http://www.starport.net/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Cisco As5300 and VOIP and Debit card
Hi All,
I got this to work yesterday and have shared it with Mark and he seems to
have gotten it to work too, so I thought to share it with you all. I know
for a fact that the handling of h323 VSAs for the Cisco access servers is
not supported by many Radius servers, including Livingston and CAR (Cisco
!), so this maybe a good feature for Radiator developers to look into. Cisco
says Merit already supports it.
Anyway, aside from the dictionary, you will have to tweak the h323 AV pair
you gave the Cisco VoIP server. As an example, if you define a user in a
flat file the reply items should look like this:
1234User-Password = "567899"
h323-credit-amount = "h323-credit-amount=123.45"
h323-credit-time = "h323-credit-time=900"
basically the ascii value that you send back has to be prepended with the
attribute so in the perspective of radiator it sends back attribute =
"attribute=value". but the 5300 will be able to recognize this...as long as
it's the correct h323 attribute prepended.
so far this is the only value the Router/IVR will recognize. And according
to Cisco it isnt going to change soon ("It's a feature, not a bug"). In any
case it worked and the IVR was able to break down those values into
appropriate audio prompts...
Hope this helps some of you in you IVR implementations...
Vincent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Matthew Nichols
Sent: Tuesday, March 07, 2000 5:24 AM
To: [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Cisco As5300 and VOIP and Debit card
Mark,
Make sure these are in your dictionary
VENDORATTR 9 cisco-h323-remote-address 23
string
VENDORATTR 9 cisco-h323-conf-id 24 string
VENDORATTR 9 cisco-h323-setup-time 25 string
VENDORATTR 9 cisco-h323-call-origin 26 string
VENDORATTR 9 cisco-h323-call-type27 string
VENDORATTR 9 cisco-h323-connect-time 28 string
VENDORATTR 9 cisco-h323-disconnect-time 29
string
VENDORATTR 9 cisco-h323-disconnect-cause 30
string
VENDORATTR 9 cisco-h323-voice-quality31
string
VENDORATTR 9 cisco-h323-ivr-out 32 string
VENDORATTR 9 cisco-h323-gw-id33 string
VENDORATTR 9 cisco-h323-call-treatment 34
string
VENDORATTR 9 cisco-h323-ivr-in 100 string
VENDORATTR 9 cisco-h323-credit-amount101
string
VENDORATTR 9 cisco-h323-credit-time 102 string
VENDORATTR 9 cisco-h323-return-code 103 string
VENDORATTR 9 cisco-h323-prompt-id104 string
VENDORATTR 9 cisco-h323-time-and-day 105 string
VENDORATTR 9 cisco-h323-redirect-number 106
string
VENDORATTR 9 cisco-h323-preferred-lang 107
string
VENDORATTR 9 cisco-h323-redirect-ip-addr 108
string
VENDORATTR 9 cisco-h323-billing-model109
string
VENDORATTR 9 cisco-h323-currency-type110
string
Regards,
Matt
At 03:43 PM 7/03/00 +1300, you wrote:
Has anyone used Radiator to send back the credit amount and credit time and
return code in vsa's for the Cisco debit card platform ? We use an As5300
and are currently authing using radiator 2.15. The Cisco radius debug says
the pair is an invalid format for type 26, 26 referring to vendor specof
attribute I presume.
We send and have defined in our dictionary :
vendorattr 9 Credit_Amount 101 string
Radius handles it OK, the AS5300 does not.
Help
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
---
Matthew Nichols - Network/Systems Engineer
CCNA
HunterLink Pty Ltd
Newcastle NSW Australia
Phone: +61 2 4969 0122 Fax: +61 2 4969 0133
PGP Public Key: http://moonah.hunterlink.net.au/~matt/pgp/pgpkey.html
HunterLink Web Site: http://www.hunterlink.net.au
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Cisco As5300 and VOIP and Debit card
Thank you Vincent for the information.
We have made a new dictionary including the h3232 attributes available in the
2.15 patches area, and added an entry to the FAQ.
Thanks again for that.
Cheers.
On Mar 7, 10:11am, Vincent Torres wrote:
Subject: RE: (RADIATOR) Cisco As5300 and VOIP and Debit card
Hi All,
I got this to work yesterday and have shared it with Mark and he seems to
have gotten it to work too, so I thought to share it with you all. I know
for a fact that the handling of h323 VSAs for the Cisco access servers is
not supported by many Radius servers, including Livingston and CAR (Cisco
!), so this maybe a good feature for Radiator developers to look into. Cisco
says Merit already supports it.
Anyway, aside from the dictionary, you will have to tweak the h323 AV pair
you gave the Cisco VoIP server. As an example, if you define a user in a
flat file the reply items should look like this:
1234 User-Password = "567899"
h323-credit-amount = "h323-credit-amount=123.45"
h323-credit-time = "h323-credit-time=900"
basically the ascii value that you send back has to be prepended with the
attribute so in the perspective of radiator it sends back attribute =
"attribute=value". but the 5300 will be able to recognize this...as long as
it's the correct h323 attribute prepended.
so far this is the only value the Router/IVR will recognize. And according
to Cisco it isnt going to change soon ("It's a feature, not a bug"). In any
case it worked and the IVR was able to break down those values into
appropriate audio prompts...
Hope this helps some of you in you IVR implementations...
Vincent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Matthew Nichols
Sent: Tuesday, March 07, 2000 5:24 AM
To: [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Cisco As5300 and VOIP and Debit card
Mark,
Make sure these are in your dictionary
VENDORATTR 9 cisco-h323-remote-address 23
string
VENDORATTR 9 cisco-h323-conf-id 24 string
VENDORATTR 9 cisco-h323-setup-time 25 string
VENDORATTR 9 cisco-h323-call-origin 26 string
VENDORATTR 9 cisco-h323-call-type27 string
VENDORATTR 9 cisco-h323-connect-time 28 string
VENDORATTR 9 cisco-h323-disconnect-time 29
string
VENDORATTR 9 cisco-h323-disconnect-cause 30
string
VENDORATTR 9 cisco-h323-voice-quality31
string
VENDORATTR 9 cisco-h323-ivr-out 32 string
VENDORATTR 9 cisco-h323-gw-id33 string
VENDORATTR 9 cisco-h323-call-treatment 34
string
VENDORATTR 9 cisco-h323-ivr-in 100 string
VENDORATTR 9 cisco-h323-credit-amount101
string
VENDORATTR 9 cisco-h323-credit-time 102 string
VENDORATTR 9 cisco-h323-return-code 103 string
VENDORATTR 9 cisco-h323-prompt-id104 string
VENDORATTR 9 cisco-h323-time-and-day 105 string
VENDORATTR 9 cisco-h323-redirect-number 106
string
VENDORATTR 9 cisco-h323-preferred-lang 107
string
VENDORATTR 9 cisco-h323-redirect-ip-addr 108
string
VENDORATTR 9 cisco-h323-billing-model109
string
VENDORATTR 9 cisco-h323-currency-type110
string
Regards,
Matt
At 03:43 PM 7/03/00 +1300, you wrote:
Has anyone used Radiator to send back the credit amount and credit time and
return code in vsa's for the Cisco debit card platform ? We use an As5300
and are currently authing using radiator 2.15. The Cisco radius debug says
the pair is an invalid format for type 26, 26 referring to vendor specof
attribute I presume.
We send and have defined in our dictionary :
vendorattr 9 Credit_Amount 101 string
Radius handles it OK, the AS5300 does not.
Help
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
---
Matthew Nichols - Network/Systems Engineer
CCNA
HunterLink Pty Ltd
Newcastle NSW Australia
Phone: +61 2 4969 0122 Fax: +61 2 4969 0133
PGP Public Key: http://moonah.hunterlink.net.au/~matt/pgp/pgpkey.html
HunterLink Web Site: http://www.hunterlink.net.au
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
-- End o
(RADIATOR) Cisco As5300 and VOIP and Debit card
Has anyone used Radiator to send back the credit amount and credit time and return code in vsa's for the Cisco debit card platform ? We use an As5300 and are currently authing using radiator 2.15. The Cisco radius debug says the pair is an invalid format for type 26, 26 referring to vendor specof attribute I presume. We send and have defined in our dictionary : vendorattr 9 Credit_Amount 101 string Radius handles it OK, the AS5300 does not. Help === Archive at http://www.starport.net/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Cisco As5300 and VOIP and Debit card
Hello Mark - On Tue, 07 Mar 2000, Mark Jenks wrote: Has anyone used Radiator to send back the credit amount and credit time and return code in vsa's for the Cisco debit card platform ? We use an As5300 and are currently authing using radiator 2.15. The Cisco radius debug says the pair is an invalid format for type 26, 26 referring to vendor specof attribute I presume. We send and have defined in our dictionary : vendorattr 9 Credit_Amount 101 string Radius handles it OK, the AS5300 does not. You will need to run Radiator at trace level 4 so you can see the packet dumps of what Radiator is sending, and you will also have to run the Cisco with debugging turned on to see what it is doing. On the Cisco you turn on debugging with: "debug ." and you can find out what debug specifically by typing "debug ?" and so on down through the stack (NB - there are *many, many* debug options). We have never seen the attributes that you are describing, so anything you do find out please forward to the list so we can add the information to the FAQ. thanks Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X. === Archive at http://www.starport.net/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Cisco AS5300 Problem
Hello Steve - On Fri, 04 Feb 2000, Steve Suehring wrote: Hello- I'm having the following problem with people dialing in single channel ISDN into Cisco AS5300. The reason I'm posting this to the Radiator list is that the problem only started after we switched from Merit to Radiator. For the past week I've been pursuing it from the Cisco end with no luck. Here are details. When a user dials in with PPP for single-channel isdn, it will not authenticate. The Cisco debug shows that it fails during the Authorization stage. Specifically here is the debug from the cisco: 3w2d: %LINK-3-UPDOWN: Interface Async93, changed state to down 3w2d: %LINK-3-UPDOWN: Interface Serial0:13, changed state to up 3w2d: Se0:13 AAA/AUTHOR/FSM: (0): LCP succeeds trivially 3w2d: Se0:13 AAA/AUTHOR/FSM: (0): LCP succeeds trivially 3w2d: AAA: parse name=Serial0:13 idb type=12 tty=-1 3w2d: AAA: name=Serial0:13 flags=0x51 type=1 shelf=0 slot=0 adapter=0 port=0 cha nnel=13 3w2d: Se0:13 AAA/AUTHOR/LCP: Authorize LCP 3w2d: AAA/AUTHOR/LCP Se0:13 (843752075): Port='Serial0:13' list='' service=NET 3w2d: AAA/AUTHOR/LCP: Se0:13 (843752075) user='vanhalen' 3w2d: AAA/AUTHOR/LCP: Se0:13 (843752075) send AV service=ppp 3w2d: AAA/AUTHOR/LCP: Se0:13 (843752075) send AV protocol=lcp 3w2d: AAA/AUTHOR/LCP (843752075) found list "default" 3w2d: AAA/AUTHOR/LCP: Se0:13 (843752075) Method=RADIUS 3w2d: AAA/AUTHOR (843752075): Post authorization status = PASS_REPL 3w2d: Se0:13 AAA/AUTHOR/LCP: Processing AV service=ppp 3w2d: Se0:13 AAA/AUTHOR/LCP: Processing AV idletime=900 3w2d: Se0:13 AAA/AUTHOR/LCP: idletime failed 3w2d: Se0:13 AAA/AUTHOR/LCP: Denied 3w2d: Se0:13 AAA/AUTHOR: Duplicate per-user event LCP_DOWN ignored 3w2d: %ISDN-6-DISCONNECT: Interface Serial0:13 disconnected from 7153415211 , c all lasted 2 seconds 3w2d: %LINK-3-UPDOWN: Interface Serial0:13, changed state to down Okay, quite obviosly it didn't like the idletime value. The problem is that this idle time value is the same for users dialing in with Multilink as well as users dialing in with regular modems. That's where I'm greatly confused. Why does it work for those others but not single channel ISDN? One angle I've thought of is to strip the idletime value from the reply for ISDN service types, but that doesn't seem to be a _solution_ rather it seems like a band-aid. Is anyone else having any problems like this? If _not_, then could you let me know so we can compare notes on AS5300 radiator config? What dictionary are you using? The standard Radiator dictionary specifies this: ATTRIBUTE Idle-Timeout28 integer And what about Service-Type? Cisco's are very picky about requiring a Service-Type that matches the request in the Access-Accept. If you could send us a trace 4 debug it would help greatly. thanks Hugh -- 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, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
