On 2013-08-13 14:12, Frederic Van Espen wrote:
adjpointcode=12248 sigchan=1 #include ss7.timers sigchan=32 #include ss7.timers adjpointcode=12198 sigchan=63 #include ss7.timers sigchan=94 #include ss7.timers
you don't need multiple includes for the timers - just one per linkset ... the last one should be enough
for pointcode 12198, the state seems to remain DOWN indefinitely. I'm not sure however if this is due to our setup or due to a misconfiguration on the other side. I'm also constantly receiving REL messages on the link to pointcode 12198. These result in errors in the asterisk logs: [Aug 13 13:07:07] ERROR[28543] chan_dahdi.c: [1] Got ISUP message on link while MTP3 state is not UP! [Aug 13 13:07:07] ERROR[28543] chan_dahdi.c: [1] Got ISUP message on link while MTP3 state is not UP! [Aug 13 13:07:07] ERROR[28543] chan_dahdi.c: [1] Got ISUP message on link while MTP3 state is not UP! [Aug 13 13:07:07] ERROR[28543] chan_dahdi.c: [1] Got ISUP message on link while MTP3 state is not UP! [Aug 13 13:07:07] ERROR[28543] chan_dahdi.c: [1] Got ISUP message on link while MTP3 state is not UP! [Aug 13 13:07:07] ERROR[28543] chan_dahdi.c: [1] Got ISUP message on link while MTP3 state is not UP! [Aug 13 13:07:07] ERROR[28543] chan_dahdi.c: [1] Got ISUP message on link while MTP3 state is not UP!
As Attila Domjan pointed in his email you may reduce the mtp3_timer.t21 value or just leave it to the default 63sec and 12198 should became UP after that timeout
Thanks, Frederic -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-ss7 mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-ss7
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-ss7 mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-ss7
