I've encounter an error during call via sip trunk going to Avaya PABX, Sometimes drop the call or cant call locally to Avaya PABX. During command INCVISU i'va see an error "Minor failure in SIP component". What is the root cause on this? Please help or any suggestion. I've reset is SIP services using command "killall sipmotor" its become ok but sometime the probelm is occur.
CPU type : cpu7
Linux version : 72.3
Delivery software version : j1.410 ;
Patch version : 34 ;
Dynamic patch version : c ;
MAO software version : J1.410.33 ;
Software Version Name : R10.0 ;
System Country : PHILIPPINES (67);
System for Large Config : no;
Node number : 1 ;
Network number : 0 ;
26/01/14 15:08:22 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8129
26/01/14 15:08:31 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
26/01/14 15:09:24 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8129
26/01/14 15:10:39 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:11:37 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8226
26/01/14 15:12:16 000001M|---/--/-/---|=2:2071=Swap partition 57 per cent full.
26/01/14 15:12:45 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:13:55 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:14:23 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:15:31 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 10 29
26/01/14 15:17:03 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:17:03 000001S|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:17:16 000001M|---/--/-/---|=2:2071=Swap partition 57 per cent full.
26/01/14 15:18:58 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:19:11 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:20:01 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:20:34 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:21:02 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:21:38 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9088
26/01/14 15:22:07 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 6875
26/01/14 15:22:17 000001M|---/--/-/---|=2:2071=Swap partition 57 per cent full.
26/01/14 15:22:39 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:22:48 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 6875
26/01/14 15:22:52 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9088
26/01/14 15:23:35 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 6875
26/01/14 15:23:42 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9088
26/01/14 15:23:50 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 6875
26/01/14 15:24:18 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9088
26/01/14 15:24:48 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9088
26/01/14 15:26:42 000001M|---/--/-/---|=0:1721=Phone exc 5, PC 0x08ea3029 neqt 1800
26/01/14 15:27:06 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:27:06 000001S|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:27:17 000001M|---/--/-/---|=2:2071=Swap partition 57 per cent full.
26/01/14 15:28:26 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8129
26/01/14 15:29:47 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:31:24 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:32:01 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 5632
26/01/14 15:32:18 000001M|---/--/-/---|=2:2071=Swap partition 57 per cent full.
26/01/14 15:36:22 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
26/01/14 15:37:14 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:37:14 000001S|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:37:18 000001M|---/--/-/---|=2:2071=Swap partition 57 per cent full.
26/01/14 15:37:20 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:37:38 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:37:39 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 9088
26/01/14 15:37:49 000001M|---/--/-/---|=0:5813=SIP external gateway 0 is out of service
26/01/14 15:37:49 000001M|000/00/-/---|=3:5801=10 SIP trunk group put out of service
26/01/14 15:37:50 000001M|000/00/-/---|=5:5800=10 SIP trunk group put into service
26/01/14 15:37:50 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 15:37:50 000001M|---/--/-/---|=0:5812=SIP external gateway 0 is in service
26/01/14 15:38:09 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 6875
26/01/14 15:39:21 000001M|019/00/0/001|=3:0020=DID fault 0 Eqt 2011
26/01/14 15:42:41 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 62 6
26/01/14 15:42:41 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 62 26164
26/01/14 15:42:41 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 63 4189
26/01/14 15:47:20 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:47:20 000001S|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:49:48 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8129
26/01/14 15:52:04 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8129
26/01/14 15:52:22 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8461
26/01/14 15:55:36 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 10 29
26/01/14 15:57:41 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:57:41 000001S|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 15:59:13 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 4785
26/01/14 15:59:39 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8129
26/01/14 16:01:25 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
26/01/14 16:04:41 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 5219
26/01/14 16:07:48 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 16:07:48 000001S|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/01/14 16:08:46 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 8129
26/01/14 16:09:04 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident 2 7777
26/01/14 16:12:50 000001M|---/--/-/---|=2:0283=ACCOUNTING. Appli CALLHANDLING : feature incident
SIP error "Minor failure in SIP component"
-
Brunno
Re: SIP error "Minor failure in SIP component"
post your sip trunk group configuration here...
Remember using SIP TRUNK type ISDN ALL COUNTRY
ABCF only for GPV, Opentouch, ICS or other OXE.
Remember using SIP TRUNK type ISDN ALL COUNTRY
ABCF only for GPV, Opentouch, ICS or other OXE.
- frank
- Alcatel Unleashed Certified Guru

- Posts: 3390
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: SIP error "Minor failure in SIP component"
"Minor failure in SIP component" is a problem during SIP exchange (Registration, calls, etc..)
Look at the date and time :
26/01/14 16:01:25 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
Then go under /tmpd and open sipalarm files.
To make the link between the incident and sipalarm files, look for the same date and time.
Look at the date and time :
26/01/14 16:01:25 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
Then go under /tmpd and open sipalarm files.
To make the link between the incident and sipalarm files, look for the same date and time.
Code Free Or Die
-
PeEs
Re: SIP error "Minor failure in SIP component"
I got this problem this morning. And guess what?? the problem is not from ALU but from the customer router configuration has been modified. Try to ask them to make static routing to your alu pbx ip address.
