Hi!<br>The diameter part of diameter in radiator is to act as a Diameter->Radius gateway.The CER/CEA and DWR/DWA work very well.<br> I changed Radiator to support a very specific 3GPP Gy. <br>Which interface do you want implement ? probably it can be done with little effort.<br clear="all">
<br><br>José Borges Ferreira<br><br><br>Dick Cavett - "If your parents never had children, chances are... neither will you."
<br><br><div class="gmail_quote">On Tue, Mar 3, 2009 at 6:39 PM, German Staltari <span dir="ltr"><<a href="mailto:gstaltari@arnet.net.ar">gstaltari@arnet.net.ar</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi, we were trying to connect an SBC (Acmepacket) with Radiator DIAMETER module, and the peering worked fine, but when the SBC sent the first diameter request, it was an UDR (User-Data Request) and Radiator didn't recognize it (log: Diameter request from x.x.x.x:x was not an AA or ACCOUNTING message. Ignored.). Is there a plan to add support to those requests in Radiator DIAMETER module?<br>
Has anyone any experience to share about SBC's - Radiator connection?<br>
TIA<br>
<br>
German Staltari<br>
Servicios de Internet & Multimedia<br>
Direccion de Tecnologia Informatica<br>
Telecom Argentina SA<br>
<br>
<br>
_______________________________________________<br>
radiator mailing list<br>
<a href="mailto:radiator@open.com.au" target="_blank">radiator@open.com.au</a><br>
<a href="http://www.open.com.au/mailman/listinfo/radiator" target="_blank">http://www.open.com.au/mailman/listinfo/radiator</a><br>
</blockquote></div><br>