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!

bug098

Status
Not open for further replies.

ftb2112

Technical User
Aug 9, 2013
7
CA
BUG098
BUG098 : 0 770
BUG098 + 106D4EA8 107B8920 1056325A 105627AC 1055FDA6
BUG98 + 1055F59C 21E35FA2 10557B2A 21DBB788 21E34F76
BUG098 + 1054D8F0 21DD5658 1054C394 10EBE694 10EBD1A2
BUG98 + 10EBC278 10EBBA16 10EE40D6 10EE3E0C 10EE3B60
BUG098 + 10EE1B14 10EE1A48 108FC558 108F92E0 108F8EF8
BUG98 + 10F60060 10F598BE

BUG098
BUG098 : 0 770
BUG098 + 106D4EA8 107B8920 105632D4 105627BE 1055FDA6
BUG98 + 1055F59C 21E35FA2 10557B2A 21DBB788 21E34F76
BUG098 + 1054D8F0 21DD5658 1054C394 10EBE694 10EBD1A2
BUG98 + 10EBC278 10EBBA16 10EE40D6 10EE3E0C 10EE3B60
BUG098 + 10EE1B14 10EE1A48 108FC558 108F92E0 108F8EF8
BUG98 + 10F60060 10F598BE
getting these bug messages when calls are terminating on our avst voicemail when callers call a did# other did#s calling avst not generating this bug any ideas???
 
BUG0098 C R The route number (RNO) passed into Procedure $SET_ROUTE_PTRS is out
of range.
C = Customer Number
R = Route Number
Action: Investigate possible data corruption.
Severity: Minor. Critical to Monitor: No. SNMP trap: Yes
 
Did you ever find a solution to this issue?
 
Release 04.50w patch MPLR22427

BUG0098 : C R Messages.

Where C = Customer Number and R = Route Number

Although NTP's state that BUG098 message's relate to customer/route number and could be caused by data corruption, MPLR22427 fixes a problem relating to PLDN's.

BUG0098 : 0 138 messages were being produced on the obseved sytem but it had niether Group Hunt List 138 or Route 138 but MPLR22427 reolved the issue.
----------------------------------------------------------------------------------------------------------------------------------------------

Tittle: GPHT / PLDN (GROUP HUNT) : BUG098 is printed if PLDN with HTYP=RRB configured.

Conditions: Some PLDN with HTYP = 'RRB' is configured for a Group Hunt list.

Actions: An incoming trunk call.

Expected Response: No BUG098.

Actual Response: BUG098 is displayed.

Patch Solution: To correct the usage of global DNPTR pointer.



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
UPDATE

I have proven that these messages are related to the AVST voicemail server and the CS1000 it is connected to.
Each particular Bug098 message indicates a specific directory number that is causing the issue, for example

Bug098 0 770 -- equates to dn xxx, a phantom forwarding to avst

Bug098 0 552 -- equates to dn yyy, a phantom forwarding to avst

Each of the dn's were programmed as phantoms forwarding to the AVST. The solution for my particular situation was to convert these phantoms to acd dn's. The improvement was immediate in so much as so many messages were happening that the cs1000 history file had only 2 hours of history rather than 3 days.

AVST seems to be stumped on this issue but this work-around removes the bombardment of messages on the pbx. Who knows, maybe it is an issue with the interface cards in the v/m server.

This is a work around, not a fix, as I still don't know the root cause.





 
if you use phatoms that point to the AVST Vmail system, how are the ports defined? Are they a Group Hunt list? What is the DCFW on the phantom?

If the DCFW on the phantom is a PLDN in the system (you can check this in LD 57 - FFC and look for PLDNs programmed) then it could be the error and the patch could fix it.

John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile
 
I have 8 digital ports interfaced to the AVST and are configured to hunt to the next port. The 1st port's dn is the prime voicemail dn. Either phantom or ACD dcfw to the prime v/m dn. Call treatment at the end of the hunt chain forwards to phantoms that have cpnd entries reflecting problems - either "all avst ports busy" or "avst not answering".

No PLDN's

After converting the phantom to an acd and a reboot of the avst server not one bug098 message has occurred.

I think that I will just convert all phantoms that point to the AVST to ACD's and be done with it.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top