It sounds like chan_zap.so didn't load... You need to look at what happens when you load asterisk, to see why chan_zap.so is not loading. Matthew Fredrickson ----- umar tarar <umar.tarar@xxxxxxxxx> wrote: > Hi Matt. > now i did correct the zapata.conf as; > -------zapata.conf-------- > [channels] > context=zapIncoming > switchtype=5ess > usecallerid=yes > hidecallerid=no > echocancel=yes > echocancelwhenbridged=yes > musiconhold=default > > signalling = ss7 > ss7type = itu > linkset = 1 > > ;pointcode = 0x1680 > pointcode = 5760 > ;djpointcode = 0x168a > djpointcode = 5770 > ;defaultdpc = 0x168a > defaultdpc = 5770 > networkindicator=national > > cicbeginswith = 1 > sigchan = 16 ; First signaling channel > channel=>1-15,17-31 > -------------------------------- > > but still when i run asterisk, just nothing comes onto the CLI with > ss7 E1 link connected...now what could possibly be wrong...plz help , > i've already taken up too much time for it, the team is waitng for me > to proceed > > one more thing that i can't get any zap status on the CLI as when ever > i try to execute any zap command like 'zap show channel' it gives a > bad coomand error & upon executing the commabd 'help zap' simply > nothing happens & the control gets back to the CLI again, the same > happens with 'help ss7', but all other commands like 'sip show > channel' it shows the help string upon executing them but does'nt > actually executes them > > is this the asterisk-trunk prob or what? (i've checked all the three, > zaptel-trunk, libss7, asterisk-trunk) > > waiting for your response > > > On 10/10/06 , Matthew Fredrickson < creslin@xxxxxxxxxx > wrote: Try to > get ahold of me on IRC or on AIM. I will see if I can more > quickly help you get it working. > > Matthew Fredrickson > > On Oct 10, 2006 , at 2:17 AM, Mr.Surender Reddy wrote: > > > HI , > > I tired in many ways to get this working but i dont get this > > working for me at all there is IAM messages or any thing just the > > below message this is the circuit in Bharain.The below Message was > > given once as below > > > > > > [ Oct 8 05:17:07 ] ERROR[16007]: chan_zap.c:8435 ss7_linkset: Alarm > > cleared on link > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 1 > > [ Oct 8 05:17:07 ] ERROR[16007]: chan_zap.c:8711 zt_ss7_error: Don't > > know how to handle state change from 4 to 1 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 2 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 3 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 4 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 5 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 6 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 7 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 8 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 9 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 10 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 11 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 12 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 13 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 14 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 15 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 17 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 18 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 19 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 20 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 21 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 22 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 23 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 24 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 25 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 26 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 27 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 28 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 29 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 30 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 31 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 33 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 34 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 35 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 36 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 37 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 38 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 39 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 40 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 41 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 42 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 43 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 44 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 45 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 46 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 47 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 48 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 49 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 50 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 51 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 52 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 53 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 54 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 55 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 56 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 57 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 58 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 59 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 60 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 61 > > [ Oct 8 05:17:07 ] NOTICE[16008]: chan_zap.c:6940 handle_init_event: > > Alarm cleared on channel 62 > > Huh?! Got FISU in link state 1 > > [ Oct 8 05:17:08 ] ERROR[16007]: chan_zap.c:8711 zt_ss7_error: > Received > > MSU in invalid state 1 > > [ Oct 8 05:17:08 ] WARNING[16001]: chan_mgcp.c:4201 reload_config: > > Unable to get our IP address, MGCP disabled > > ............................................................[ Oct 8 > > 05:17:10] WARNING[16001]: pbx.c:5918 ast_context_verify_includes: > > Context 'ael-local' tries includes nonexistent context > > 'ael-parkedcalls' > > [ Oct 8 05:17:10 ] WARNING[16001]: pbx.c:5918 > > ast_context_verify_includes: Context 'ael-dundi-e164-local' tries > > includes nonexistent context 'ael-dundi-e164-canonical' > > [ Oct 8 05:17:10 ] WARNING[16001]: pbx.c:5918 > > ast_context_verify_includes: Context 'ael-dundi-e164-local' tries > > includes nonexistent context 'ael-dundi-e164-customers' > > [ Oct 8 05:17:10 ] WARNING[16001]: pbx.c:5918 > > ast_context_verify_includes: Context 'ael-dundi-e164-local' tries > > includes nonexistent context 'ael-dundi-e164-via-pstn' > > .[ Oct 8 05:17:10 ] ERROR[16007]: chan_zap.c:8711 zt_ss7_error: > > Received message destined for point code 0x7c but we're 0x0. > Dropping > > [ Oct 8 05:17:10 ] ERROR[16007]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > [ Oct 8 05:17:12 ] WARNING[16001]: pbx_dundi.c:4372 set_config: > Unable > > to look up host 'localhost.localdomain' > > ..... ] > > Asterisk Ready. > > *CLI> [ Oct 8 05:17:21 ] ERROR[16007]: chan_zap.c:8711 zt_ss7_error: > > Received message destined for point code 0x7c but we're 0x0. > Dropping > > [ Oct 8 05:17:21 ] ERROR[16007]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > > > [ Oct 8 05:20:57 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > message destined for point code 0x7c but we're 0x0. Dropping > > [ Oct 8 05:20:57 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > [ Oct 8 05:21:08 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > message destined for point code 0x7c but we're 0x0. Dropping > > [ Oct 8 05:21:08 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > [ Oct 8 05:21:19 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > message destined for point code 0x7c but we're 0x0. Dropping > > [ Oct 8 05:21:19 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > [ Oct 8 05:21:30 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > message destined for point code 0x7c but we're 0x0. Dropping > > [ Oct 8 05:21:30 ] ERROR[16097]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > this message is also given for me when i have confgiured all the > > Channels for my ss7 signaling > > > > [ Oct 7 16:39:03 ] ERROR[32409]: chan_zap.c:8711 zt_ss7_error: !! > > Unable to handle SIG_NET_MNG message with H1 = 1 and H0 = 4 > > [ Oct 7 16:39:03 ] ERROR[32409]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > [ Oct 7 16:39:03 ] ERROR[32410]: chan_zap.c:8711 zt_ss7_error: !! > > Unable to handle SIG_NET_MNG message with H1 = 1 and H0 = 4 > > [ Oct 7 16:39:03 ] ERROR[32410]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > [ Oct 7 16:39:03 ] ERROR[32409]: chan_zap.c:8711 zt_ss7_error: !! > > Unable to handle SIG_NET_MNG message with H1 = 1 and H0 = 4 > > [ Oct 7 16:39:03 ] ERROR[32409]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > --- SS7 Up --- > > [ Oct 7 16:39:03 ] ERROR[32410]: chan_zap.c:8711 zt_ss7_error: -- > > !! Unable to handle SIG_NET_MNG message with H1 = 1 and H0 = 4 > > Resetting CICs 1 to 15 > > [ Oct 7 16:39:03 ] ERROR[32410]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > -- Resetting CICs 17 to 62 > > [ Oct 7 16:39:03 ] ERROR[32410]: chan_zap.c:8711 zt_ss7_error: !! > > Unable to handle SIG_NET_MNG message with H1 = 1 and H0 = 4 > > [ Oct 7 16:39:03 ] ERROR[32410]: chan_zap.c:8711 zt_ss7_error: > Received > > error from mtp3 layer: -1 > > --- SS7 Up --- > > -- Resetting CICs 63 to 77 > > -- Resetting CICs 79 to 124 > > [ Oct 7 16:39:22 ] WARNING[32402]: pbx_dundi.c:4372 set_config: > Unable > > to look up host 'localhost.localdomain' > > ......................[ Oct 7 16:39:22 ] WARNING[32402]: pbx.c:5918 > > ast_context_verify_includes: Context 'ael-local' tries includes > > nonexistent context 'ael-parkedcalls' > > [ Oct 7 16:39:22 ] WARNING[32402]: pbx.c:5918 > > ast_context_verify_includes: Context 'ael-dundi-e164-local' tries > > includes nonexistent context 'ael-dundi-e164-canonical' > > [ Oct 7 16:39:22 ] WARNING[32402]: pbx.c:5918 > > ast_context_verify_includes: Context 'ael-dundi-e164-local' tries > > includes nonexistent context 'ael-dundi-e164-customers' > > [ Oct 7 16:39:22 ] WARNING[32402]: pbx.c:5918 > > ast_context_verify_includes: Context 'ael-dundi-e164-local' tries > > includes nonexistent context 'ael-dundi-e164-via-pstn' > > ............................[ Oct 7 16:39:42 ] WARNING[32402]: > > chan_skinny.c:4444 reload_config: Unable to get our IP address, > Skinny > > disabled > > ........... ] > > Asterisk Ready. > > *CLI> Resetting CIC 1 > > [ Oct 7 16:40:06 ] WARNING[32410]: chan_zap.c:8502 ss7_linkset: RSC > on > > unconfigured CIC 1 > > Resetting CIC 3 > > [ Oct 7 16:40:06 ] WARNING[32410]: chan_zap.c:8502 ss7_linkset: RSC > on > > unconfigured CIC 3 > > Resetting CIC 3 > > Resetting CIC 1 > > Unhandled optional parameter 0x31 'Propagation Delay' > > [0x0 0x0 ] > > Unhandled optional parameter 0x8 'Unknown' > > [0x0 ] > > Unhandled optional parameter 0x39 'Unknown' > > [0x31 0xd4 ] > > > > i really want to make use of it but iam not sucessful.IF any changes > > please let me know . > > > > regards > > surender > > > > > > > > > > > > On 09/10/06 , umar tarar < umar.tarar@xxxxxxxxx > wrote: thanx Matt. > for > > identifying such a blunder that i made, now i'll try it when we'll > go > > to the site > >> > >> > >> On 10/9/06 , Matthew Fredrickson < creslin@xxxxxxxxxx > wrote: > >>> On Oct 9, 2006 , at 11:03 AM, umar tarar wrote: > >>> > >>> > hi Matt.! > >>> > > >>> >making my entry again with a prob, & that is, before connecting > to > >>> > the ss7 E1 link, i re-checked all the three (zaptel-trunk, > libss7 & > >>> > asterisk-trunk) to hav the latest versions, they got compiled > all > >>> > fine, but when i configured and run the asterisk with the ss7 E1 > >>> link > >>> > connected, asterisk ran all ok but nothing ever appears on CLI & > no > >>> > call comes in, my conf is following: > >>> >----zaptel.conf---- > >>> >pan=1,1,0,ccs,hdb3 > >>> >bchan=1-15,17-31 > >>> >dchan=16 > >>> >loadzone=uk > >>> >defaultzone=uk > >>> >----------------------- > >>> > ---zapata.conf--- > >>> >[channels] > >>> >context=zapIncoming > >>> >switchtype=5ess > >>> >;signalling=fxo_ls > >>> >usecallerid=yes > >>> >hidecallerid=no > >>> >echocancel=yes > >>> >echocancelwhenbridged=yes > >>> >musiconhold=default > >>> > > >>> >signalling = ss7 > >>> > > >>> >ss7type = itu > >>> > > >>> >linkset = 1 > >>> > > >>> >;pointcode = 0x1680 > >>> >pointcode = 5760 > >>> > > >>> >;djpointcode = 0x168a > >>> >djpointcode = 5770 > >>> > > >>> >;defaultdpc = 0x168a > >>> >defaultdpc = 5770 > >>> > > >>> >cicbeginswith = 1 > >>> >networkindicator=national > >>> > > >>> >sigchan = 16 > >>> >channel = 1-31 > >>> > >>> You are setting your zap channel that you are using as your > >>> signalling > >>> channel as a bearer channel. > >>> > >>> This should probably be > >>> > >>> cicbeginswith=1 > >>> channel=1-15,17-31 > >>> > >>> or (if you are supposed to leave out a CIC for Zap/16 > >>> > >>> cicbeginswith=1 > >>> channel=1-15 > >>> cicbeginswith=17 > >>> channel=17-31 > >>> > >>> > > >>> >now with this conf, simply nothing happens on the ast CLI, no > >>> calls, > >>> > no errors just nothing.....i believe i m missing somthing > >>> >plz guide me as i feel that i am close to hav my ss7 link up with > >>> my > >>> > asterisk > >>> > >>> If it still doesn't work, you can try using the `ss7 debug linkset > x` > >>> command to see if it gives you more useful output. > >>> > >>> Matthew Fredrickson > >>> > >>> _______________________________________________ > >>> --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 > > > > -- > |__\__/__| /__/ \__\ |__| \__|
|