Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: Franco on May 26, 2009, 02:29:15 AM
-
Yeaiiieee, we finally ordered an E1 trunk. It'll be an R2 signaling (MFC R2).
I took a read at this url (http://www.voip-info.org/wiki/view/Asterisk+MFC+R2), and I have a feeling I won't be able to use SAIL in it's native way.
My card is an TE110P.
Does anyone have any experience with this hardware, this signaling protocol or anything related?
Thanks,
-
Shouldn't be a problem. SAIL (2.1) will, by default, set the card up for E1 Qsig but you can override that in PCI cards panel to set it to whatever you want. Set your card jumpers for E1 and you should be fine.
In 2.3.8(ish) you have even more freedom to change the generated hardware setup. PCI cards panel is completely different in these releases so you may want to check it out.
Best
S
-
Thanks a lot Selintra,
In 2.3.8(ish) you have even more freedom to change the generated hardware setup. PCI cards panel is completely different in these releases so you may want to check it out.
Is that something to come?
I'm running:
[root@servidor ~]# rpm -q sail
sail-2.3.1-4
-
Yes - it's what we are using here on our own PBX at the moment. It'll be a week or so in shakedown but it's definitely getting there.. (sorry - release is 2.3.1.8 )
:)
-
Hi Selintra,
I finally have tried to set up the card, without success at first :(
The system detects the card:
Current Contents of /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Mon Jun 8 23:56:07 2009 -- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER)
span=1,1,0,ccs,hdb3,crc4
# termtype: te
bchan=1-15,17-31
dchan=16
echocanceller=mg2,1-15,17-31
# Global data
loadzone = uk
defaultzone = ukCurrent Contents of /etc/asterisk/dahdi-channels.conf
; Autogenerated by /usr/sbin/dahdi_genconf on Mon Jun 8 23:56:07 2009 -- do not hand edit
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/asterisk/chan_dahdi.conf that will include the global settings
;
; Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER)
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = pri_cpe
channel => 1-15,17-31
context = default
group = 63
But as I read in this chapter (http://sarkpbx.com/twiki/bin/view/Main/DocChapter222a#What_did_the_PCI_routine_do), querying the channels returns nothing:
Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.4.24.1 currently running on asterisk (pid = 7000)
asterisk*CLI> dahdi show channels
No such command 'dahdi show channels' (type 'help dahdi show' for other possible commands)
asterisk*CLI>
And the trunklines:
(http://wiki.contribs.org/images/1/16/Dahdi-chan.gif)
Should I have all the 32 channels listed?
Thanks,
-
Your kernel modules have not been loaded.
The kmdl loader is a separate entity in 2.3. Make sure you start dahdi the first time through, or simply reboot the system. kmdls are loaded by doing /etc/init.d/dahdi start. We noticed this issue for the first time on a fresh install yesterday and we have included a note into the 2.3(dahdi) installation quick notes.
For regular ISDN30e you should only have the Group listed because you can't "fix" or reserve channels (for example for fax or data) in the way you could with DSS, so addressing individual channels is meaningless, it's just a 2Megabit symmetrical pipe (30B+1D@16) with each B-channel running at 64K. Let me know if your E1 R2 signalling is different.
Best
S
-
Very well Selintra, following the above got me the channels listed.
-
Still having problems, the link doesn't get stablished.
The provider is telling me that I'm not passing the necessary signaling, MFC-R2.
-
I'm afraid I can't help you much there because we've never done anything with R2. You will need to set the correct values in /etc/dahdi/system.conf and then reload chan_dahdi, or restart asterisk, each time until you get synch.
Are there no examples on the web?
Best
S
-
Selintra,
They just called me and are saying I need this http://www.libopenr2.org/, and that it's already part of the latest asterisk.
I'm reading all about before I start playing.
Any help is much appreciated.
Thanks,
-
Ok, I finally got it all running.
It was a signalling problem, together with me not knowing how to make a RJ48C cable :grin:
I'll document the entire process and post in the Wiki for those who need.
Thanks a lot!
-
Well done Franco!
I'll look forward to seeing what you;ve done.
Best
S
-
Selintra, I'm still having problems with this :(
Today I'll do a bit different to make my life easier and stop guessing the parameters: I'll install an asterisk distribution that already has support for this signaling protocol, copy all the configurations and try again with SAIL.
I'll keep you posted.
Thanks,
-
OK
Keep us posted
S
-
Bump...
Did you get this running yet?
Best
S
-
Hi S.,
I'm running on a different distribution[1] at the moment, 'cause I couldn't get it to run on SME7.4. I got stuck patching asterisk with libopenr2 [2]. Now, this is what caught me, my problem was that autoconf in SME7.4 is ver 2.59, the document tells me that I need ver 2.60. The distribution that I'm running now have the same version of autoconf as SME and works just fine.
[1] (http://www.elastix.org)
[2] (http://code.google.com/p/openr2/downloads/list)
-
Ok
thanks for the heads up old friend
A lot of these problems should go away when we get to EL5 in SME R8.
Best
S
-
A lot of these problems should go away when we get to EL5 in SME R8.
So this is what I'm gonna do, how's SAIL running on SME8?
Thanks,
-
Why don't I learn to keep my big mouth shut?
:)
2.3.1 svn trunk seems to run OK on SME8 beta 4 with Asterisk 1.6.1 - yes, we've done a little bit of testing (not much). We found a few minor glitches (for example, it won't tell the time when you do *55*), but we've not had the time to give it a proper shakedown.
I tried sail-2.3.1-20 on the same test platform and it seems OK also.
However, SME 8.0B4 uses kernel-2.6.18-128.1.14.el5, which is so recent that no one has any Asterisk 1.4 or 1.6 rpms for it.
so....
You'll need to do what we did and build Asterisk from source.
Let me know if you need help with this.
Best
S
-
:)
I'll try and let you know.
Asterisk 1.6 has already support for this built in, so it'll be easier for sure.
Thanks,