We have started seeing BUG 448 on the CS1Km that we have our Call Pilot connected to recently. I saw some old posts on this from several years ago but the one solution referred to a CP HA system. We only run a single server and like before there is still nothing in the Docs about this BUG448. We are also seeing PRI 275 with is related to the virtual trunks on that PBX. Both of these seem to implicate the Call Pilot but there is really no information that I can find on this. Does anyone have any ideas. We have a ticket open with Avaya but no solutions yet. The only positive thing so far is that it doesn't seem to be service affecting or at least no one has complained. PBX is on rel 7.6 and all patches are up to date.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Bug 448
- Thread starter steve64
- Start date
Have you verified the Patch Level against Avaya's website? The MDP list in the PBX as well as the Patch Level on the Linux in the Signal Servers? I have seen countless times where people say their patches are up to date and then come to find out they really aren't.
- Thread starter
- #4
I do all the patching on our systems and they were all updated starting in November to late December with the latest delta deplist from the espl site. Sig servers have SP_7.6_7_1.ntl, Linux base is 7.65.16.23-21, patch web 7.65.16.23-1, Jboss 7.65.16.23-5, and dmweb 7.65.16.23-4. Yes they are P-IV processors. Also yes the patches are correct in the mdp issp. We see PRI242 errors on the PRI trunks on one PBX. Those trunks terminate on the PBX with the BUG448 codes. That PBX also has an ocassional PRI275 which relates to virtual trunks from our session manager. In the PRI242 and 275 the terminating number is our call pilot. We have verified that the mail boxes are present for the calling numbers. All of the inter switch trunking is across customer owner and maintained fiber.
I would agree then, looks the patches are current. I suppose the next step is to wait for a call back from Avaya. The Support site isn't much help on those 2 errors. I suppose it wouldn't hurt to take a look at the patches in the Call Pilot also.
- Thread starter
- #6
Our Call Pilot engineer is looking at that but the system was just recently upgraded several months ago and this issue only started about a week ago. Avaya pulled lots of logs from the 2 system yesterday and is currently going through them, but nothing has jumped out as the problem yet.
StanleySteamer
Technical User
There is a FAQ regarding BUG448 that says it is caused when CallPilot is trying to turn on a message light for a DN at a networked location but that DN also appears at the local CallPilot site.
The fix is to eliminate the duplicated DN.
You can see the FAQ if you have a login to the Avaya support site and search for "CS1000 BUG448". Unfortunately, it won't be found unless you are logged in.
The fix is to eliminate the duplicated DN.
You can see the FAQ if you have a login to the Avaya support site and search for "CS1000 BUG448". Unfortunately, it won't be found unless you are logged in.
- Thread starter
- #8
Found the issue. Calls routed to the Call pilot from one location are routed via Session Manager but the return path for turning on the sets lamp was routed via a PRI to another PBX and then sent through the Session Manager. This "detour" was removed and the return path back to the set was directly from the PBX with the CP to Session Manager the Bug 448 stopped. This little glitch was overlooked when the offending site was changed from a stand alone PBX to an SMG. I'm still not sure why the PBX was "angry" about this but it was. I'm thinking maybe some kind of timing issue.
- Status
Similar threads
