BUG 4046

[rheine]

I am getting a bug 4046 off a CS1000 release 5.0. I am not able to find any information on this. Only what the bug code means:

BUG4046
Invalid Facility I.E. information received.

Severity: Minor

I updated the loadware and CP-PM PEP's and that didn't help.

Any ideas..

 

[pcat200]

It is usually associated with information received on the D-channel of the PRI connecting you to your service provider, the CS1K is/is not receiving an Information Element relevant to the call. Information elements (IE)specify further information which is associated to the actual message. An IE contains the IE name (e.g. bearer capability), their length and a variable field of contents. It may be something like the service provider is sending a CLID name and number, but you are only accepting the number. You may be able to determine the problem by turning on the D channel messaging and capturing the mesage.

 

[rheine]

Thanks allot I will turn on the "D" channel monitoring for that channel. The reason why I was looking into this bug code is because the customer had been complaining of misdialing problems dialing out and that is why I had decided to update the CP-PM patches and complete the latest loadware updates to all of the MCG cards. I will let you know what I find out with the "D" channel monitoring.

 

[rheine]

The traffic at that PBX location has slowed way down at this time of day. I have not seen that error for over 30 minutes, the bug 4046. I did look at the history and it is possible that the below error is associated with this bug 4046. The error is PRI210 DCH: 50 0000003

PRI0210
Protocol Error: Wrong coding standard. Output data: DCH: x DATA: y .
Where: x = D-channel number and y = Coding standard.
Contact your technical support group if the problem persists.
Severity: Critical

Not sure what the coding standard of 00000003 is?
Thanks

 

[Firebird Scrambler]

I've found this below?.

This BUG is printed because this node received a FACILITY message on a dch, asking us to perform TAT. But at our node TAT is not configured as an RCAP, therefore we print the bug4046. remove tat from far end dch rcap.

NB: TAT requires an MSDL-based DCH for the feature to work. The NTAK79 PRI card on small systems will not support TAT.

Meridian 1 / CS1000 ISDN PRI TAT feature

The system only supports Trunk Anti-Tromboning on the Multi-purpose Serial Data Link (MSDL) card for D-channel handling.

Note: Small Systems and CS 1000S systems only support the Trunk Anti-Tromboning feature on the NTBK51BA D-Channel Daughterboard for D-channel handling with PRI. The NTAK79 2MB PRI card does not support TAT.
To support the Trunk Anti-Tromboning feature within a dedicated ISL/VNS configuration, an NTAK02 (minimum vintage BB) Serial Data Interface (SDI)/D-channel (DCH) circuit card must be used.

See the ISDN Primary Rate Features NTP for a full description of Trunk Route Optimisation and TAT


All the best

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

http://www.linkedin.com/in/davidbromley

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

 

[rheine]

To understand the latest response to my question I would remove tromboning for the "D" channels route that I am having the issue with? I did noticed that part of the DS0's are in one route with tromboning flagged as yes and the other part of these channels in addition to the other PRI's are assigned a different route and tromboning is flagged as no. I looked in one of my other 1000E locations, release 5.0 and all of the PRI's at that location are in the same route and tromboning is yes and I have never seen this bug 4046 at that site.

Thanks

 

[dmunger]

BUG4046 only means that yuor service provider is sending unknown IE (unsupported feature) on your DCH. TAT is one of many that could be involved. It might also be something unknown in CS1000 world. Look at your DCH RCAP prompt as well.

 

[rheine]

Ok, I better get with the CLEC and find out what they are sending us compared to the other PRI's since it appears that I only see this error from the one DCH. Thanks

 

[PaulOnecomm]

Just a response to this Thread. I am from a telco provider and had a vendor contact me regarding BUG 4046. I was able to find your post in which it said that name could be the issue. I turned off caller ID name on our side (the Provider) and it cleared the bug errors on the D channel.