Sorry, I didnot describe it clearly. I run 2 asterisk on the same box, in /etc/asterisk are the config files for 1st asterisk, in the /etc/asterisk2 for the 2nd.
http://home.tvnet.hu/~adomjan/asterisketcs.tar.gz Make a call to asterisk1 from a sip phone, asterisk1 call asterisk2 over ss7 and asterisk2 call asterisk1 over ss7 and so while we have free cics, after terminate the chain by Milliwatt application. ctrl-c, or kill asterisk2 and start again. t5 expired on 1st asterisk: [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=41. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=45. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=45. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=57. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=57. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=47. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=47. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=55. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=55. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=62. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=62. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=60. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=60. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=58. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=58. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=56. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=56. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=54. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=54. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=52. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=52. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=50. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=50. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=48. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=48. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=46. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=46. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=44. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=44. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=42. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=42. [Mar 21 10:52:59] NOTICE[15358]: l4isup.c:768 t1_timeout: T1 timeout (waiting for RLC) CIC=40. [Mar 21 10:52:59] WARNING[15358]: l4isup.c:824 t5_timeout: T5 timeout (No "release complete" from peer) CIC=40. still not work, T17 expired: [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=45. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=57. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=47. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=55. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=62. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=60. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=58. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=56. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=54. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=52. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=50. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=48. [Mar 21 11:02:59] WARNING[15358]: l4isup.c:948 t17_timeout: T17 timeout (No "release complete" from peer) CIC=46. I still cant use all the channels. ss7 show channels report all the channels are idle. Now I started ss7 dump on asterisk2. Asterisk1 sent rsc, asterisk2 sent back rlc, but I still can't use the cics. On Wed, 2007-03-21 at 10:42 +0100, Anders Baekgaard wrote: > chan_ss7 behaves correct in this case: a circuit is not released until RLC is > received from the peer. The CLI command "ss7 show channels" should show all > CICs as busy. If you get congestion while some CICs are shown as idle, like > Anton wrote below, that is clearly a bug in chan_ss7. If somebody knows how > to reproduce that, please let me know. > > Best regards > Anders Baekgaard > > On Wednesday 21 March 2007 10: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 [EMAIL PROTECTED]:1] NoOp("SS7/test/29", "") in new stack > > -- Executing [EMAIL PROTECTED]: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 [EMAIL PROTECTED]:1] NoOp("SS7/test/33", "") in new stack > > -- Executing [EMAIL PROTECTED]: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 [EMAIL PROTECTED]:1] NoOp("SS7/test/35", "") in new stack > > -- Executing [EMAIL PROTECTED]: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 > > > > [EMAIL PROTECTED] 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-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 > > > > > > _______________________________________________ > > > --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
ss7rlc.cap
Description: Binary data
signature.asc
Description: This is a digitally signed message part
_______________________________________________ --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
