Alignment problem with libss7

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am out of ideas. Can you test with two Asterisk instances, to exclude
hardware problems.

On Mon, 1 Oct 2012 13:32:45 +0200, Victor Neiman
<victor at blacksheepdev.co.za> wrote:
> I have it the other way round, Asterisk is configured as master clock
(also
> in wanpip1.conf file) and so I have span=1,0,0,ccs,hdb3,crc4 there, and
> Mobicents is the slave (TE_CLOCK  = NORMAL in wanpipe1.conf) and so
> span=1,1,0,ccs,hdb3,crc4.
> 
> So the clock comes from the Asterisk side.
> 
> 
> On Mon, Oct 1, 2012 at 11:46 AM, Kaloyan Kovachev
> <kkovachev at varna.net>wrote:
> 
>> Who is providing the clock in your setup?
>>
>> span=1,1,0,ccs,hdb3,crc4 - on Asterisk machine means it expects the
clock
>> from remote, but if Mobicent does not provide clock you need:
>>
>> span=1,0,0,ccs,hdb3,crc4
>>
>> On Mon, 1 Oct 2012 11:29:13 +0200, Victor Neiman
>> <victor at blacksheepdev.co.za> wrote:
>> > HI Mitul,
>> >
>> > thanks for the suggestion, tried it, does not seem to help, in fact
>> getting
>> > an additional error message now in Asterisk:
>> >
>> >
>> > [Oct  1 13:35:52] ERROR[26703]: chan_dahdi.c:13966 dahdi_ss7_error:
[1]
>> >> Received MSU in invalid state 1
>> >>
>> >>
>> > Regards
>> > Vic
>> >
>> > On Mon, Oct 1, 2012 at 11:11 AM, Mitul Limbani <mitul at enterux.com>
>> wrote:
>> >
>> >> You need to run signalling on mobicent side too n not have all
bearer
>> >> channels. bchan=2-31, dchan=1 on Mobicent. Fix that side ... and
>> dchan=1
>> >> instead of mtp2=1 on asterisk, Everything else looks ok on asterisk
>> side.
>> >>
>> >> Mitul
>> >>
>> >> On Mon, Oct 1, 2012 at 12:41 PM, Victor Neiman
>> >> <victor at blacksheepdev.co.za
>> >> > wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I'm trying to get SS7 communication between Asterisk 1.8.16.0 which
>> has
>> >>> libss7 installed and the Mobicents Signalling Gateway , using
Sangoma
>> >>> A101
>> >>> hardware in two boxes.  Both boxes are using wanrouter and dahdi.
One
>> >>> box
>> >>> is running Asterisk, the other Mobicents. I have been corresponding
>> >>> closely
>> >>> with people at Mobicents to get the configuration right for their
>> >>> software
>> >>> and am fairly sure it is correct. The problem is that when I start
up
>> >>> the
>> >>> Mobicents Signalling Gateway, Asterisk on the other side
immediately
>> >>> fills
>> >>> up with these errors:
>> >>>
>> >>> [Oct  1 10:55:46] NOTICE[19825]: chan_dahdi.c:3437
>> >>>> my_handle_link_exception: SS7 got event: HDLC Abort(6) on span 1/0
>> >>>
>> >>>
>> >>>
>> >>> The box that is running the SGW has the following
>> >>> /etc/dahdi/system.conf:
>> >>>
>> >>> #autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
>> >>>> #autogenrated on 2012-09-28
>> >>>> #Dahdi Channels Configurations
>> >>>> #For detailed Dahdi options, view /etc/dahdi/system.conf.bak
>> >>>> loadzone=us
>> >>>> defaultzone=us
>> >>>>
>> >>>> #Sangoma A101 port 1 [slot:4 bus:5 span:1] <wanpipe1>
>> >>>> span=1,1,0,ccs,hdb3,crc4
>> >>>> bchan=1-31
>> >>>>
>> >>>
>> >>> This config comes straight from the guys at Mobicents. All channels
>> are
>> >>> bchan.
>> >>>
>> >>> The Asterisk side looks like this, /etc/dahdi/sysem.conf
>> >>>
>> >>> #autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
>> >>>> #autogenrated on 2012-09-28
>> >>>> #Dahdi Channels Configurations
>> >>>> #For detailed Dahdi options, view /etc/dahdi/system.conf.bak
>> >>>> loadzone=us
>> >>>> defaultzone=us
>> >>>>
>> >>>> #Sangoma A101 port 1 [slot:4 bus:2 span:1] <wanpipe1>
>> >>>> span=1,0,0,ccs,hdb3,crc4
>> >>>> bchan=2-31
>> >>>> mtp2=1
>> >>>>
>> >>>
>> >>>  /etc/asterisk/chan_dahdi,conf looks like this:
>> >>>
>> >>> ;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
>> >>>> ;autogenrated on 2012-09-28
>> >>>> ;Dahdi Channels Configurations
>> >>>> ;For detailed Dahdi options, view
/etc/asterisk/chan_dahdi.conf.bak
>> >>>>
>> >>>> [trunkgroups]
>> >>>>
>> >>>> [channels]
>> >>>> context=default
>> >>>> usecallerid=yes
>> >>>> hidecallerid=no
>> >>>> callwaiting=yes
>> >>>> usecallingpres=yes
>> >>>> callwaitingcallerid=yes
>> >>>> threewaycalling=yes
>> >>>> transfer=yes
>> >>>> canpark=yes
>> >>>> cancallforward=yes
>> >>>> callreturn=yes
>> >>>> echocancel=yes
>> >>>> echocancelwhenbridged=yes
>> >>>> relaxdtmf=yes
>> >>>> rxgain=0.0
>> >>>> txgain=0.0
>> >>>> group=1
>> >>>> callgroup=1
>> >>>> pickupgroup=1
>> >>>> immediate=no
>> >>>>
>> >>>> ;Sangoma A102 port 1 [slot:2 bus:6 span:1] <wanpipe1>
>> >>>> context=from-pstn
>> >>>> group=0
>> >>>> echocancel=no
>> >>>> signaling=ss7 ;this is ss7 signaling
>> >>>> ss7type=itu ;using the ITU variant
>> >>>> ss7_called_nai=dynamic ;NAI for outgoing calls
>> >>>> ss7_calling_nai=dynamic ;NAI for incoming calls
>> >>>> ss7_internationalprefix=00 ;international prefix value for
incoming
>> >>>> calls
>> >>>> ss7_nationalprefix=0 ;national prefix value for incoming calls
>> >>>> ss7_subscriberprefix= ;subscriber prefix value for incoming calls
>> >>>> ss7_unknownprefix= ;unknown prefix value for incoming calls
>> >>>> ss7_explictacm=yes ;ACM is send as soon as call enters the dial
>> >>>> plan...may not accepted yet though
>> >>>> linkset=1 ;arbitrary name for this set of channels
>> >>>> pointcode=1 ;the point code for this system...aka SPC
>> >>>> adjpointcode=2 ;the point code for the system that we are
signaling
>> >>>> to... aka APC
>> >>>> defaultdpc=2 ;the point code for the system that the CICs will be
>> >>>> negotiated with...aka DPC
>> >>>> networkindicator=international ;NI value for MTP3
>> >>>> cicbeginswith=1 ;the starting value of the CICs
>> >>>> channel=2-31 ;the channels that are CICs
>> >>>> sigchan=1 ;the signaling channel
>> >>>>
>> >>>
>> >>> Any help would be appreciated. Feels like I'm missing something in
>> >>> the
>> >>> configs but I just can't seem to pin it down.
>> >>>
>> >>> Regards
>> >>> Victor
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>>
_____________________________________________________________________
>> >>> -- 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
>> >>
>>
>> --
>> _____________________________________________________________________
>> -- 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
>>



[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux