> With the change in ComOS versions from 3.8.2 we have started noticing our
> PM3 becoming less available over time (maxing out at 42 session instead of
> peaking at 58+). The TELCO techs tell us that the Siemens EWSD switch we
> are connected to (Plain vanilla R2 signalling) is putting more and more
> timeslots on the E1s into a maintance mode over time.
Are you getting busy tones at 42 sessions or is it just the performance
that degrades?
When it starts having problems again, you should send the output following
commands to your local Lucent support person:
version
show line0
show line1
show memory
show isdn
show modems
set debug isdn-max
(then let it run for a few minutes and capture the output)
> The problem creeps up over a several day period so we have resorted to
> rebooting the PM3 and power cycling the E1 LTU every morning :(
I'm not able to run ComOS 3.8.2 for more than a few days before it reboots
itself.
> Any ideas out there?
Could be the E1 RAI sequence timing bug, but you should have seen this
under ComOS 3.8 as the PRI code is the same (I think). How old is your
portmangler?
> I hate to back out of the 3.8.2 upgrade because the modem code is much
> improved.
I did that about a month ago.
-- Richard Morrell richard@ednet.co.uk System Administrator - edNET: Internet Access for Edinburgh - www.ednet.co.uk
- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>