[asterisk-ss7] No idle circuit found

[Anton]

Hm, anyone knows how the regular ss7 stack suppose to behave 
if it does not receive RLC?

On 21 March 2007 14:05, Domjan Attila wrote:
> Hi,
> easy to reproduduce the problem:
>
> I started 2 asterisk on the same box, in the box is a
> TE405
>
> asterisk -cvvvp
> asterisk -cvvvp -C /etc/asterisk2/asterisk.conf
>
> connect 1-2 and 3-4 ports crosslink E1 cables
>
> I make a call to box1 (SIP), chain the call between 2
> asterisks (dialplan) using all ss7 circuits, end
> terminate an apllication ag. Milliwatt.
>
> exten => _66XX,1,NoOp
> exten => _66XX,2,Dial(SS7/test/$[${EXTEN} + 1])
>
> exten => 6630,1,NoOP(${EXTEN})
> exten => 6630,2,Milliwatt()
>
>
> Its works fine, everything is ok.
> Now stop the box2 with CTRL-C, start again.
> box1 hangup all the channels, ss7 linestat indicate all
> the channels are idle, but I cant use all the circuits:
>
> [Mar 21 10:02:26] NOTICE[14057]: l4isup.c:2469
> process_iam: IAM (cic=29): ANI=57 DNI=6622 RNI=
> redirect=no/0 complete=1. -- Executing [6622 at from-ss7:1]
> NoOp("SS7/test/29", "") in new stack -- Executing
> [6622 at from-ss7:2] Dial("SS7/test/29", "SS7/test/6623") in
> new stack
>     -- SS7 request (SS7/test/6623) format = 0x8.
>     -- SS7 channel SS7/test/6623 allocated successfully.
>     -- Called test/6623
> [Mar 21 10:02:26] NOTICE[14057]: l4isup.c:2469
> process_iam: IAM (cic=33): ANI=57 DNI=6623 RNI=
> redirect=no/0 complete=1. -- Executing [6623 at from-ss7:1]
> NoOp("SS7/test/33", "") in new stack -- Executing
> [6623 at from-ss7:2] Dial("SS7/test/33", "SS7/test/6624") in
> new stack
>     -- SS7 request (SS7/test/6624) format = 0x8.
>     -- SS7 channel SS7/test/6624 allocated successfully.
>     -- Called test/6624
> [Mar 21 10:02:26] NOTICE[14057]: l4isup.c:2469
> process_iam: IAM (cic=35): ANI=57 DNI=6624 RNI=
> redirect=no/0 complete=1. -- Executing [6624 at from-ss7:1]
> NoOp("SS7/test/35", "") in new stack -- Executing
> [6624 at from-ss7:2] Dial("SS7/test/35", "SS7/test/6625") in
> new stack
>     -- SS7 request (SS7/test/6625) format = 0x8.
> [Mar 21 10:02:26] WARNING[15213]: l4isup.c:391
> cic_hunt_even_mru: No idle circuit found.
> [Mar 21 10:02:26] WARNING[15213]: l4isup.c:656
> ss7_requester: SS7 requester: No idle circuit available.
> [Mar 21 10:02:26] WARNING[15213]: app_dial.c:1090
> dial_exec_full: Unable to create channel of type 'SS7'
> (cause 34 - Circuit/channel congestion)
>
>
> chan_ss7 is writing this notice:
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=61.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=59.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=47.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=45.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=57.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=55.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=46.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=62.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=60.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=54.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=52.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=50.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=48.
> [Mar 21 10:00:31] NOTICE[14057]: l4isup.c:768 t1_timeout:
> T1 timeout (waiting for RLC) CIC=58.
>
> On Sat, 2007-03-17 at 10:01 +0500, Anton wrote:
> > 0.8.4 has the same problem.
> >
> > On 8 March 2007 15:27, Anton wrote:
> > > Just looked through the mailing list - Nico
> > > asterisk at nicox.org reported that a while ago -
> > > Confirming - I met the same situation - chan_ss7 or
> > > asterisk (atleast up to 1.2.12.1) have the channel
> > > allocation problem. Later asterisk versions does not
> > > work with chan_ss7 for me.
> > >
> > > On 8 March 2007 15:19, Anton wrote:
> > > > Does anyone experiencing a situation, when loaded
> > > > chan_ss7 0.9 after a while of operation (for me 2
> > > > days) - stopped accepting calls - while having all
> > > > of the channels free - I'm getting congesion - "no
> > > > idle circuit found"  - asterisk reload cures the
> > > > situation.
> > > > _______________________________________________
> > > > --Bandwidth and Colocation provided by Easynews.com
> > > > --
> > > >
> > > > asterisk-ss7 mailing list
> > > > To UNSUBSCRIBE or update options visit:
> > > >
> > > > http://lists.digium.com/mailman/listinfo/asterisk-s
> > > >s7
> > >
> > > _______________________________________________
> > > --Bandwidth and Colocation provided by Easynews.com
> > > --
> > >
> > > asterisk-ss7 mailing list
> > > To UNSUBSCRIBE or update options visit:
> > >   
> > > http://lists.digium.com/mailman/listinfo/asterisk-ss7
> >
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > asterisk-ss7 mailing list
> > To UNSUBSCRIBE or update options visit:
> >   
> > http://lists.digium.com/mailman/listinfo/asterisk-ss7