Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: kb-ohnemus on April 10, 2007, 11:16:18 PM
-
Hi,
I've set up Sail with one HFC-Card. I could initialize the card as PCI-1 and two trunks Zap1-1 and Zap2-1 were created. But the state of these two trunks is marked with a red cross, and clicking on the cross gives "Peer Line1 not found" or "Peer Line2 not found". Setting up a route and trying to dial out says: Please hang up and try again.
I've changed nothing else in the trunkline-definitions.
My zapata.conf:
[channels]
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
relaxdtmf=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
faxdetect=incoming
context=mainmenu
resetinterval=never
immediate=no
switchtype=euroisdn
signalling=bri_cpe
pridialplan=dynamic
prilocaldialplan=local
nationalprefix=0
internationalprefix=00
usecallingpres=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=100
group=2
channel=1-2
My zaptel.conf:
loadzone=de
defaultzone=de
span=1,1,3,ccs,ami
bchan=1-2
dchan=3
So, I have no real idea where to look.
-
Hi,
Which versions are you using ?
anabri-asterisk-florz-1.2.10-7.i686.rpm
anabri-asterisk-zappri-florz-1.2.6-6.i686.rpm
selintra-sail-2.1.14-438.noarch.rpm
Which kind of ISDN 'NT' do you have ?
HFC card is 'TE', point to point ISDN.
Btw, don't look at the red cross ... I don't think the status of the lines to be monitored.
Rgds,
Herve
-
I have selintra-sail-2.1.14-434.noarch.rpm and thought this was the latest?
I'm running kernel 2.6.9-42.0.3.EL
I've connected the HFC-card to an old ISDN-telephone-system (look here http://www.spieleronline.de/home120.htm).
So I think this should be point-to-multipoint, signalling=bri_cpe_ptmp. But that doesn' do anything either.
This was working with trixbox and misdn in point-to-multipoint-mode.
-
Hi,
... 2.1.14-434 should not make any difference.
... Yes looks to be PMP ISDN that is needed.
Since it's a pbx, I assume it's 'TE' side, means 'Sail' needs to be 'NT' side.
Maybe you can try 'bri_net_ptmp' instead of 'bri_cpe_ptmp'.
server 'reboot' might also be needed to initialise the card properly.
Not sure it can work, basically 'Sail' works as TE/P2P.
Best,
Herve
-
Ok, made it to work. I found out the following (mostly interesting for german users):
First of all, I had to change:
/sbin/e-smith/db selintra-work setprop zaphfc status YES
/sbin/e-smith/db selintra-work setprop ztdummy status NO
otherwise /etc/init.d/asterisk start would not load the zaphfc-module and then I can't probe the card.
Then I changed signalling=bri_cpe to signalling=bri_cpe_ptmp
because my old PBX the HFC is connected to uses point to multipoint on the internal S0-bus.
If I would connect the card directly to the ISDN-Net I had to use signalling=bri_cpe, because I have numbers reaching from -0 to -99. This is pont to point (in german Anlagenanschluss).
If I had three different ISDN-numbers like the "cheap" ISDN-lines this would be point to multipoint again (in german "Mehrgeräteanschluss").
bri_net seems only to be needed if I want to have an internal S0-bus in the SME-server and connect other ISDN-hardware to that. This doesn't seem to be supported by sail.
Correct me if I made mistakes.
Manuel
-
First of all, I had to change:
/sbin/e-smith/db selintra-work setprop zaphfc status YES
/sbin/e-smith/db selintra-work setprop ztdummy status NO
otherwise /etc/init.d/asterisk start would not load the zaphfc-module and then I can't probe the card.
Sounds strange ... normally, by 'probing' the card using 'PCI Card' panel, the zaphfc status is changed automatically to 'YES'.
Of course your card needs to be known by the system : http://www.selintra.com/docs/cgi-bin/view/Main/DocChapter258
You should have something like
pci:????:????:????:????=sysdev|probe|zaphfc|zzeor|EOR|
in the database, where ????:????:????:???? meets your card PCI ID.
Best,
Hervé
-
The docs are not available at the moment, but I found a pdf and tried from the start. I added the card PCI ID, but anyway I had to do /sbin/e-smith/db selintra-work setprop zaphfc status YES
Doesn't matter I hope.
-
Hi guys,
Impressive work to get your ISDN card working without any docs KB.
The docs site is back up now.
Herve,
I'll try to get the mISDN AGI updates done later this week. I've asked them to do it when they retrofit the Flash and memory management code to 2.1.15/1.4. It's a biggish fit so it might be a couple of days yet.
Best
J
-
The docs are not available at the moment, but I found a pdf and tried from the start. I added the card PCI ID, but anyway I had to do /sbin/e-smith/db selintra-work setprop zaphfc status YES
Doesn't matter I hope.
Hi,
No ... does not matter if it works ... but, as a result, your trunk lines are most probably not created automatically as they should.
Best,
Hervé
-
Herve,
I'll try to get the mISDN AGI updates done later this week. I've asked them to do it when they retrofit the Flash and memory management code to 2.1.15/1.4. It's a biggish fit so it might be a couple of days yet.
Best
J
Hi Jeff,
Thanks ... keep your time !.
When AGI ready, will start testing autodetection & trunk generation TE/PP as a first step. Still work arround extension.conf templating depending on how the AGI reacts.
Best,
Herve
-
Hey, I'm quite an idiot, I did:
/sbin/e-smith/db selintra-work setprop pci:1397:2bd0:1075:c101 probe wctdm zzeor EOR instead of zaphf. A little too much copy and paste.
Now the card is found automatically and the zap-trunks work fine except for one thing:
I've set up some DID-trunkline-numbers like 961238-0, 961238-11, 961238-12 and so on and attached them to some softphone-extensions so dialing in works fine to them. Dialing out also works but on the foreign Phone only the number 961238-0 appears. It would be nice if the softphone which belongs to 961238-11 would also show that number on the foreign phone.
I think this is the same problem like http://forums.contribs.org/index.php?topic=3660.0 and therefore this is not possible?
-
Well, I've found out for myself. I just wrote callerid="" <96123811> at the corresponding extensions.