T3 traces on OXE

Post Reply
kzaman69
Member
Posts: 13
Joined: 19 May 2009 23:38

T3 traces on OXE

Post by kzaman69 » 10 Jul 2009 00:58

Hi Everyone,
I have one problem on the OXE R8.0.1-g1.503-27. It seems the incoming calls for ISDN T2 cannot get through, they ring once and stop. The trace is "IE:[08] CAUSE (l=4) 02 80 e4 1e -> [e4] INVALID INFORMATION ELEMENT CONTENTS". Outgoing calls work fine. Actually the incoming ISDN calls work fine on A4400 R4.2. But once migrated to OXE R8.0.1, we have this problem. Other features work fine on this new release. Hope someone can help. Thank you in advance

Regards,
Kamaruzaman

tincho.rn
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 928
Joined: 30 Jan 2006 09:40
Location: Argentina
Contact:

Re: T3 traces on OXE

Post by tincho.rn » 10 Jul 2009 08:33

Hi. Check under mgr --> system. You have some variables to ingnore Invalid IE. Regards.
ACSE R11
OT R2.0

iourid
Member
Posts: 72
Joined: 12 Nov 2004 15:08
Location: Chicago

Re: T3 traces on OXE

Post by iourid » 10 Jul 2009 17:50

Could be the following:
Check mgr/Trunk Group/ parameter "Overlap dialing=NO". This parameter did not exist in R4.2

Gedeon
Member
Posts: 184
Joined: 17 Sep 2008 15:10

Re: T3 traces on OXE

Post by Gedeon » 13 Jul 2009 05:58

Check the message from the network before the response from OXE with Invalid information.
In the reject cause, you have [e4] information for incorrect Information Element.
Check the value of IE named e4 and adapt the gestion to this value.

G.

kzaman69
Member
Posts: 13
Joined: 19 May 2009 23:38

Re: T3 traces on OXE

Post by kzaman69 » 21 Jul 2009 22:34

It works. Thank you. Settings under sytem to ignore invalid E1 make it works. Thank you once again.
Regards

Post Reply

Return to “Traces”