Re: RadAliasAuth Access Accept not showing extra Attributes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok i fixed the freeradius and now gnugk gets this back(see bottom). so now the question is does gnugk have a attribute dictionary? so type=208 doesnt come up unkown, but cmes up with a valid attrbute name?

what i am hoping to do is this,

have a mysql 5.0(yes its alpha, but i need stored procedures and triggers and clustering) stored procedure create the access-accept attributes LCR1, LCR2, LCR3....LCR7

the value of each attribute will be as follows

1234#4312#01133836991111
|-A-||-B-||C||----D----|

where
A is my gnugk prefix for internal routing, will match to a registered endpoint (this can be removed after routing has taken place with the endpoint=out=1234#= config line.
B is a carrier prefix. if the endpoint in question requires a prefix, the storedproc will pull that info from that database and append here
C if the carrier requires a 011 prepended to the digits
D the actual countrycode+number string

so my stored procedure will determine multiple least cost routes, and provide X many LCRx string back to gnugk in the access-accept packet. and will provide digit manipulation per the endpoints requirements. all i need now if for someone to write the gnugk code to make use of these attributes when placing the 2nd leg of the call, and to write rollover logic to attempt additional routes if preceding routes fail. how does this all sound to you? I like it bc you can customize the database side since the radius sits in the middle. as long as you return these attributes. I am kind of basing this Least cost routing system on my experience in the carrier class minutes game  and the least cost routing engines i have working with.


2004/06/23 11:24:39.416 3           radproto.cxx(1901)  RADIUS  Received PDU from RADIUS server 127.0.0.1 (127.0.0.1:1812) by socket port:30401[0,55-56], PDU: {
          code = 2 (Access-Accept)
          id = 55
          length = 32 octets
          authenticator = 16 octets {
            18 84 85 62 3c d4 4e a0  a4 85 75 12 8f fa e0 7e   ...b<.N...u....~
          }
          attributes = 2 elements {
            [0]= {
              type = 6 (Service-Type)
              length = 6 octets
              value = 4 octets {
                00 00 00 02                                        ....
              }
            }
            [1]= {
              type = 208 (Unknown)
              length = 6 octets
              value = 4 octets {
                64 61 76 65                                        dave
              }
            }
          }
       }



David Winter
Senior Network Engineer
Planet-Telecom, Inc.
Tampa FL
(813)901-5182 Office
(813)864-3162 Direct
(813)817-4204 Mobile
(813)881-9762 Fax
------------------------------------------
AIM:     mobofool
ICQ:      3563403
MSN:    dwinter@xxxxxx
Y!:        vt_fool


Zygmuntowicz Michal wrote:
It's probably a problem with improper use of FreeRadius features. 
Have you defined your DAVE_TEST_VAL in Radius dictionaries?

----- Original Message ----- 
From: "david winter" <dwinter@xxxxxxxxxxxxxxxxxx>
Sent: Wednesday, June 23, 2004 2:32 PM


  
below is the access-request,access-accept, and freeradius reply detail 
files. i am trying to get freeradius to send back extra attributes in 
the access-accept packet (for LCR use). the reply detail log for 
freeradius shows it sent my extra attribute, but it does not show in the 
-ttttt for gnugk. Comes as null there. This might be a freeradius 
problem, but i thought to post it here in case there might be a reason 
gnugk would drop attributes.

2004/06/23 08:25:13.399 3           radproto.cxx(1875)  RADIUS  Sending 
PDU to RADIUS server 127.0.0.1 (127.0.0.1:1812) from 
port:30401[0,52-53], PDU: {
          code = 1 (Access-Request)
          id = 52
          length = 283 octets
          authenticator = 16 octets {
            36 f8 ba b7 13 52 27 f9  0f 06 7a 5d 19 7a 95 8b   
6....R'...z].z..
          }
          attributes = 13 elements {
            [0]= {
              type = 1 (User-Name)
              length = 19 octets
              value = 17 octets {
                54 41 4d 50 41 5f 58 4f  2e 56 4f 49 50 2e 50 4f   
TAMPA_XO.VOIP.PO
                50                                                 P
              }
            }
            [1]= {
              type = 2 (User-Password)
              length = 34 octets
              value = 32 octets {
                ae f5 bb 79 33 62 87 86  18 ab 52 e2 c0 33 2d 3d   
...y3b....R..3-=
                c0 96 c8 db 0b 06 9d 1e  e7 95 d7 d1 47 56 c8 39   
............GV.9
              }
            }
            [2]= {
              type = 4 (NAS-IP-Address)
              length = 6 octets
              value = 4 octets {
                42 ee fb 86                                        B...
              }
            }
            [3]= {
              type = 32 (NAS-Identifier)
              length = 9 octets
              value = 7 octets {
                70 6c 61 6e 65 74 33                               planet3
              }
            }
            [4]= {
              type = 61 (NAS-Port-Type)
              length = 6 octets
              value = 4 octets {
                00 00 00 05                                        ....
              }
            }
            [5]= {
              type = 6 (Service-Type)
              length = 6 octets
              value = 4 octets {
                00 00 00 01                                        ....
              }
            }
            [6]= {
              type = 8 (Framed-IP-Address)
              length = 6 octets
              value = 4 octets {
                41 69 05 f0                                        Ai..
              }
            }
            [7]= {
              type = 31 (Calling-Station-Id)
              length = 19 octets
              value = 17 octets {
                54 41 4d 50 41 5f 58 4f  2e 56 4f 49 50 2e 50 4f   
TAMPA_XO.VOIP.PO
                50                                                 P
              }
            }
            [8]= {
              type = 30 (Called-Station-Id)
              length = 15 octets
              value = 13 octets {
                38 38 31 38 31 33 38 36  34 33 31 36 33            
8818138643163
              }
            }
            [9]= {
              type = 26 (Vendor-Specific)
              length = 56 octets
              vendorId = 9
              vendorValue = 50 octets {
                18 32 68 33 32 33 2d 63  6f 6e 66 2d 69 64 3d 33   
.2h323-conf-id=3
                33 39 33 46 36 45 46 20  43 34 34 37 31 31 44 38   
393F6EF C44711D8
                20 39 35 39 36 38 45 46  37 20 31 42 34 30 45 31    
95968EF7 1B40E1
                36 39                                              69
              }
            }
            [10]= {
              type = 26 (Vendor-Specific)
              length = 34 octets
              vendorId = 9
              vendorValue = 28 octets {
                1a 1c 68 33 32 33 2d 63  61 6c 6c 2d 6f 72 69 67   
..h323-call-orig
                69 6e 3d 6f 72 69 67 69  6e 61 74 65               
in=originate
              }
            }
            [11]= {
              type = 26 (Vendor-Specific)
              length = 27 octets
              vendorId = 9
              vendorValue = 21 octets {
                1b 15 68 33 32 33 2d 63  61 6c 6c 2d 74 79 70 65   
..h323-call-type
                3d 56 6f 49 50                                     =VoIP
              }
            }
            [12]= {
              type = 26 (Vendor-Specific)
              length = 26 octets
              vendorId = 9
              vendorValue = 20 octets {
                21 14 68 33 32 33 2d 67  77 2d 69 64 3d 70 6c 61   
!.h323-gw-id=pla
                6e 65 74 33                                        net3
              }
            }
          }
       }

2004/06/23 08:25:13.418 3           radproto.cxx(1901)  RADIUS  Received 
PDU from RADIUS server 127.0.0.1 (127.0.0.1:1812) by socket 
port:30401[0,52-53], PDU: {
          code = 2 (Access-Accept)
          id = 52
          length = 20 octets
          authenticator = 16 octets {
            5a 4e 4f e8 b3 bc 88 2b  f2 bf 80 51 97 bc d0 4a   
ZNO....+...Q...J
          }
          attributes = <<null>>
       }

FREERADIUS REPLY 
DETAIL--------------------------------------------------------------------------------------------------
[root@planet3 127.0.0.1]# cat reply-detail-20040623
Packet-Type = Access-Accept
Wed Jun 23 08:12:22 2004
        DAVE_TEST_VAL := "dave is real cool"

Packet-Type = Access-Accept
Wed Jun 23 08:14:13 2004
        DAVE_TEST_VAL := "dave is real cool"

Packet-Type = Access-Accept
Wed Jun 23 08:17:37 2004
        DAVE_TEST_VAL := "dave is real cool"

Packet-Type = Access-Accept
Wed Jun 23 08:25:13 2004
        DAVE_TEST_VAL := "dave is real cool"
    



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

_______________________________________________________

List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
  

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux