Rafael Visser wrote: > Hi Everyone > I have an asterisk 1.4 Asterisk SVN-trunk-r97805 with a TE410P, all trunks > connected. > This asterisk stops working with out logging any thing clear.. > > [Apr 15 09:27:44] WARNING[3954] channel.c: Unexpected control subclass '14' > [Apr 15 09:27:49] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:28:29] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:28:35] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:32:33] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:34:36] WARNING[3954] channel.c: Unexpected control subclass '14' > [Apr 15 09:34:38] WARNING[3954] channel.c: Unexpected control subclass '14' > [Apr 15 09:37:53] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:38:14] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:41:10] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:41:12] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:42:17] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:45:55] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:45:57] WARNING[3954] file.c: Unexpected control subclass '14' > [Apr 15 09:46:03] WARNING[3954] file.c: Unexpected control subclass '14' > > Other warnings like the following are logging. > Unhandled optional parameter 0x31 'Propagation Delay Counter' [0x0 0x5a ] > Unhandled optional parameter 0x3a 'Unknown' [0x44 0x5 0x95 0x0 0x0 0x0 ] > Unhandled optional parameter 0x3f 'Location Number' [0x4 0x93 0x95 0x95 0x17 > 0x2 0x0 0x87 ] > Unhandled optional parameter 0x39 'Parameter Compatibility Information' > [0x31 0xd0 0x3a 0xd0 0x3f 0xc0 ] These are harmless, mostly informational for me as a developer. > Asterisk "zap show channles" displays all trunks in services but on the > ericsson switch all the trunks are blocked. > Do you have any idea of what is happening ? > Does someone has the same problem?. Can you give the `ss7 debug linkset x` output of an incoming call in this state? It may be that this is an Asterisk bug. If that is the case, you will need to make sure your Asterisk version and libss7 version is up to date to proceed further. I would also recommend migrating to the Asterisk 1.6.0 branch, since that is going to be the first "stable" branch with libss7 support. -- Matthew Fredrickson Software/Firmware Engineer Digium, Inc.
|