DNIS not passed was Re: urgent Help

Frank Wanicka ( (no email) )
Thu, 16 Apr 1998 22:48:08 -0400

thanks for all the info. neither piece of info is coming over in the
accounting packet as of now. i'll look further into the provisioning (we
have a DS3, which gets split into the channelzied T1s).
Frank Wanicka

-----Original Message-----
From: Mitchell B. Wagers <mwagers@ocsnet.net>
To: RadiusNT@iea-software.com <RadiusNT@iea-software.com>
Date: Thursday, April 16, 1998 9:13 PM
Subject: Re: urgent Help

>Because of the CAS/CAT factor on channelized services (24 ), you should
>have PRI's running to your boxes as Kevin has stated. Also, why don't you
>try looking at an accounting packet coming in? (radius -x15) Compare that
>with the NAME of the field in the calls table and see if they match WITHOUT
>the "-". Caller-ID doesn't always work as some outer-community switches
>don't support the option, as well as Caller-ID blockers on phones.
>At 07:25 PM 4/16/98 -0500, you wrote:
>>The lines must be PRI for the signaling to be present. IF the telco can
>>pass the CLID signals from thier switch.
>>On the Ascend Max's a special (additional cost) piece of code must be
>>loaded. Call Ascend for information...I'm not sure which code is
>>for that now.
>>Does anyone know why the Caller-ID and Client-DNIS attributes wouldn't be
>>getting passed by either Ascend MAXs or USR TCs to RadiusNT? is it a line
>>provisioning issue? do they automatically get passed over if they exist,
>>is there configuration necessary on each platform for them to get passed
>>the accounting packet?
>>Frank Wanicka