Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: (ASCEND) Caller-ID Attribute missing
This is getting wierd...
It seems to be happening on some PRIs but not others. We have 4 Maxen and
16 PRIs (4 in each box). There are two hunt groups, each with 8 PRIs
appiece (one for ISDN users and one for Modem users since we've only got
48 Modems per box).
For the hell of it I saved all the configs and then ran a 'diff' on each
one that didn't come up with anything substantial (although I found out I
forgot to turn off remote management on one, oops!).
It looks like it may be a Bell thing but if I am to give them a call, what
in the world do I ask? Telling them that we get Caller ID on some PRIs
but not on others is likely to be answered with a "must be CPE problem" or
something... I'm usually lucky to get someone at Southwestern Bell that
even knows what a PRI is ("A what?").
============
Here's more:
Looking at syslog, I see sometimes a call comes in with a message like
this:
Jul 19 14:33:13 as325c.access.unicom.net ASCEND: slot 4 port 2, Assigned
to port, 913xxxxxxx
Sometimes, I get:
Jul 19 14:33:23 as325b.access.unicom.net ASCEND: slot 6 port 4, Assigned
to port, MBID 265
What the hell is MBID??
==========
The plot thickens:
Only one of our boxes seem to be getting Caller-ID information. What's
more is that not all of the PRIs on that box get Caller-ID...
As I mentioned earlier a diff on each of the configs against this box
didn't come up with anything config-wise.
==========
Would love to hear what anyone out there has to say about this.
On Thu, 23 Jul 1998, Steve LaDuke wrote:
> I don't have any more ideas... but maybe our comments will
> prompt someone else who does ;-)
>
> Steve.
>
> -----Original Message-----
> From: Rob Myers [mailto:rmyers@unicom.net]
> Sent: Thursday, July 23, 1998 11:11 AM
> To: Steve LaDuke
> Cc: ascend-users@max.bungi.com
> Subject: RE: (ASCEND) Caller-ID Attribute missing
>
>
> In every record? :)
>
> I probably should have been more clear; it is rare to see a Caller-ID
> attribute in any of the logs but they are occasionally there. Get them
> for either Sync or Async calls but never with any amount of consistency.
>
>
> -Rob-
>
> On Thu, 23 Jul 1998, Steve LaDuke wrote:
>
> > The caller may be blocking the number from being sent.
> >
> > -----Original Message-----
> > From: Rob Myers [mailto:rmyers@unicom.net]
> > Sent: Thursday, July 23, 1998 7:40 AM
> > To: ascend-users@max.bungi.com
> > Subject: (ASCEND) Caller-ID Attribute missing
> >
> >
> > Does anyone know why sometimes the "Caller-ID" attribute is viewable
> in
> > a "Stop" record of the RADIUS log and sometimes it isn't?
> >
> > Is there a feature one of our Ascends may have turned on that others
> > might
> > not?
> >
> > We're running 5.0Ap48 on our Maxen and I'm not sure which version of
> > RADIUS.
> >
> > This feature is quite useful and almost always absent on the calls we
> > "want" to have Caller-ID on.
> >
> > Please help!
> >
> > Thanks,
> > Rob
> >
> > ++ Ascend Users Mailing List ++
> > To unsubscribe: send unsubscribe to
> ascend-users-request@bungi.com
> > To get FAQ'd: <http://www.nealis.net/ascend/faq>
> >
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>