(RADIATOR) RADIATOR with Ericsson J20 GGSN

Surajh Surjoo [ MTN - Innovation Centre ] Surajh.Surjoo at mtn.co.za
Tue Jun 21 01:02:26 CDT 2005


Hi Frank.
Yes, you are exactly correct. I saw the DupInterval command yesterday
and asked the guys to try it out, but they have not as yet. I wonder
whether RADIATOR will still be able to reply each message correctly
though. I will have to test and that means disturbing live traffic.

regards

Surajh Surjoo
Systems Engineer - Data
Mobile: 0832129829
 

MTN. Everywhere You Go.

 You always take your MTN simcard with you!


 

NOTE: This e-mail message is subject to the MTN Group disclaimer see
http://www.mtn.co.za/email_disclaimer.asp


-----Original Message-----
From: Frank Danielson [mailto:fdanielson at csky.com] 
Sent: Monday, 20 June 2005 04:37 PM
To: Surajh Surjoo [ MTN - Innovation Centre ]; radiator at open.com.au
Subject: RE: (RADIATOR) RADIATOR with Ericsson J20 GGSN

Hi Surajh-

The config file and a trace 4 log file of the activity would help a lot.

 If I understand what you are saying, each NAS port has its own id so it
is
possible that Radiator will get an Access-Request with an Id of 1 for
NAS
port 1 and then the next Access-Request could also have an Id of 1 but
for
NAS port2. Then Radiator is detecting the second request as a duplicate
and
discarding it. Is that correct?

 If this is the case the simplest work around is to set the DupInterval
to 0
in the Client definition so that Radiator does not perform duplicate
detection. A more complicated solution would be to set the DupInterval
to 0
and write a hook to perform your own duplicate detection based on the Id
and
port number. 

Of course I may have misunderstood you completely.

Frank Danielson
Infrastructure Architect

ClearSky Mobile Media
56 E. Pine St.
Orlando, FL 32801
USA

fdanielson at csky.com

-----Original Message-----
From: Surajh Surjoo [ MTN - Innovation Centre ]
[mailto:Surajh.Surjoo at mtn.co.za]
Sent: Monday, June 20, 2005 9:24 AM
To: radiator at open.com.au
Subject: (RADIATOR) RADIATOR with Ericsson J20 GGSN
Importance: High


Hi All
Has anyone managed to successfully integrate radiator radius server with
the
Ericsson J20 GGSN R2.5 (GPRS support node) for mobile networks?

We require that radiator reply back to the GGSN to the exact port number
and
message id from which a message was sent. Radiator thus far does not do
this
and sees the multiple requests as duplicate requests rather than from
multiple NAS ports.

The GGSN J20 sends requests from  multiple ports and each port has a
message
id from 0-255. RADIATOR only replies to the message id (0-255) and not
to
the port number as well. Hence the duplicates occur when numerous
requests
per second are being handled.

Please assist.

regards


Surajh Surjoo
Systems Engineer - Data
Mobile: 0832129829
Mobile fax: 083 118 2129829
Office: 011 9123000
Office Fax: 011 9123232
Email: surajh.surjoo at mtn.co.za

Bsc(Honours)Physics; Bsc(Honours)Technology Management; Postgraduate
Diploma
in Engineering(Satellite and Mobile communications); MTN Management
Foundation Programme.
Politics is more difficult than physics 
--Albert Einstein 
NOTE: This e-mail message is subject to the MTN Group disclaimer see
http://www.mtn.co.za/email_disclaimer.asp

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list