Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: jmatos on July 19, 2007, 07:01:39 PM
-
Hello,
I've bought a Billion BIPAC PCI V3.0 which is a 1397:2bd0 device.
It's Vendor and card ID are listed in http://pci-ids.ucw.cz/iii/?i=1397, but it's subsystem ID isn't (http://pci-ids.ucw.cz/iii/?i=13972bd0).
I added it to the selintra database with the command
db selintra-work set pci:1397:2bd0:1075:c101 sysdev probe zaphfc zzeor EOR
When I probe in SAIL PBX\PCI cards it returns:
Found following card...
00:06.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
Subsystem: Advanced Integrations Research: Unknown device c101
Flags: bus master, medium devsel, latency 16, IRQ 225
I/O ports at e900
Memory at ec124000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
Requesting Load of zaphfc ...
Loaded wctdm...
Zaptel view of card in /proc/zaptel/1
Span 1: ZTDUMMY/1 "ZTDUMMY/1 1"
I commit and it returns:
"There are currently no PCI Telephony cards registered on the system."
My uname -r returns 2.6.9-55.0.2.EL.
I tried the default smp kernel and the uniproc kernel. Same result.
Any ideias?
Thx.
JM
-
What release of SAIL and smeserver-asterisk are you running?
Kind Regards
Selintra
-
Hello,
My SME was installed using smei586.
It's SME 7.1.3 with SAIL is 2.1.15-483.
The RPMs used are:
smeserver-asterisk-1.4.1-8.i686.rpm
smeserver-asterisk-zappri-MPP-1.4.0-5.i686.rpm
Thx.
JM
-
OK you added the wrong kind of record to the database. Not your fault, the mISDN stuff is not really documented yet.
Here's the situation...
You can run Billion (or any HFC card) on 2.1.14 with the anabri-asterisk rpms using Bristuff...
OR
you can run Billion (or any HFC card) on 2.1.15 with asterisk 1.4 using mISDN.
The documentation we have at the moment is the bristuff documentation. You have added a card to the database using the Bristuff format,which is quite different to the mISDN format.
The first thing you need to do is to decide which ISDN driver you want to use...
Either BRistuff (which is what we use in production today) or mISDN, which is still Alpha/Beta due to the status of Asterisk 1.4.
To run bristuff you need to remove SAIL 2.1.15 and the asterisk rpms with rpm -e. You also need to remove any "dangling" misc and extra libs from /lib/modules/{uname-r}/. Then you can install 2.1.14 SAIL and anabri-asterisk.
Alternatively, to carry on with the release you have; you must first remove the bristuff fingerprint record you created.
2.1.15-483 (which you are running) has the billion fingerprint records for mISDN already in its database.
All of our Billion Bipac 3.0v cards (and we use a lot of them) have the following fingerprint... (from lspci -vvn)
00:07.0 Class 0280: 1397:2bd0 (rev 02)
Subsystem: 1397:2bd0
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 16 (4000ns max)
Interrupt: pin A routed to IRQ 217
Region 0: I/O ports at ee00 [disabled] [size=8]
Region 1: Memory at e8124000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
As you can see the system and subsystem IDs are the same, so I'm puzzled as to why yours isn't.
The rows in the database for mISDN cards are called descriptors. Here is the row for the Billion Bipac card.
pci:1397:2bd0:1397:2bd0=descriptor|active|YES|amount|1|defaultmaskset|0xf,|defaultportset|0x22,|misdndata|[default]\ncontext=mainmenu\nlanguage=en\nmusicclass=default\nsenddtmf=yes\nfar_alerting=no\nallowed_bearers=all\nnationalprefix=0\ninternationalprefix=00\nrxgain=0\ntxgain=0\nte_choose_channel=no\npmp_l1_check=no\npp_l2_check=no\nreject_cause=16\nneed_more_infos=no\nnttimeout=no\nmethod=standard\ndialplan=0\nlocaldialplan=0\ncpndialplan=0\nearly_bconnect=yes\nincoming_early_audio=no\n;always_immediate=no\nnodialtone=no\n;immediate=no\n;hold_allowed=yes\n;callgroup=1\n;pickupgroup=1\npresentation=-1\nscreen=-1\nechocancel=yes\nechocancelwhenbridged=yes\nechotraining=no\njitterbuffer=4000\njitterbuffer_upper_threshold=0\nhdlc=no\nmax_incoming=-1\nmax_outgoing=-1\n\n|modtype|hfcpci|name|Single-Bri|ports|1|zzeor|EOR
As you can see, it is quite a lot more involved than the Bristuff entry. However, if your billion card is different to ours you can copy our entry and change it to suit. Once done you can redo your probe and you should see something like this.
Found following card...
00:07.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
Subsystem: Cologne Chip Designs GmbH ISDN Board
Flags: bus master, medium devsel, latency 16, IRQ 217
I/O ports at ee00 [disabled] [size=8]
Memory at e8124000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
... 1 mISDN card(s) of this type found.
Zaptel view of card in /proc/zaptel/1
Span 1: ZTDUMMY/1 "ZTDUMMY/1 1"
Kind Regards
Selintra
-
OK you added the wrong kind of record to the database. Not your fault, the mISDN stuff is not really documented yet.
Here's the situation...
You can run Billion (or any HFC card) on 2.1.14 with the anabri-asterisk rpms using Bristuff...
OR
you can run Billion (or any HFC card) on 2.1.15 with asterisk 1.4 using mISDN.
The documentation we have at the moment is the bristuff documentation. You have added a card to the database using the Bristuff format,which is quite different to the mISDN format.
The first thing you need to do is to decide which ISDN driver you want to use...
Either BRistuff (which is what we use in production today) or mISDN, which is still Alpha/Beta due to the status of Asterisk 1.4.
To run bristuff you need to remove SAIL 2.1.15 and the asterisk rpms with rpm -e. You also need to remove any "dangling" misc and extra libs from /lib/modules/{uname-r}/. Then you can install 2.1.14 SAIL and anabri-asterisk.
Alternatively, to carry on with the release you have; you must first remove the bristuff fingerprint record you created.
2.1.15-483 (which you are running) has the billion fingerprint records for mISDN already in its database.
All of our Billion Bipac 3.0v cards (and we use a lot of them) have the following fingerprint... (from lspci -vvn)
00:07.0 Class 0280: 1397:2bd0 (rev 02)
Subsystem: 1397:2bd0
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 16 (4000ns max)
Interrupt: pin A routed to IRQ 217
Region 0: I/O ports at ee00 [disabled] [size=8]
Region 1: Memory at e8124000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
As you can see the system and subsystem IDs are the same, so I'm puzzled as to why yours isn't.
The rows in the database for mISDN cards are called descriptors. Here is the row for the Billion Bipac card.
pci:1397:2bd0:1397:2bd0=descriptor|active|YES|amount|1|defaultmaskset|0xf,|defaultportset|0x22,|misdndata|[default]\ncontext=mainmenu\nlanguage=en\nmusicclass=default\nsenddtmf=yes\nfar_alerting=no\nallowed_bearers=all\nnationalprefix=0\ninternationalprefix=00\nrxgain=0\ntxgain=0\nte_choose_channel=no\npmp_l1_check=no\npp_l2_check=no\nreject_cause=16\nneed_more_infos=no\nnttimeout=no\nmethod=standard\ndialplan=0\nlocaldialplan=0\ncpndialplan=0\nearly_bconnect=yes\nincoming_early_audio=no\n;always_immediate=no\nnodialtone=no\n;immediate=no\n;hold_allowed=yes\n;callgroup=1\n;pickupgroup=1\npresentation=-1\nscreen=-1\nechocancel=yes\nechocancelwhenbridged=yes\nechotraining=no\njitterbuffer=4000\njitterbuffer_upper_threshold=0\nhdlc=no\nmax_incoming=-1\nmax_outgoing=-1\n\n|modtype|hfcpci|name|Single-Bri|ports|1|zzeor|EOR
As you can see, it is quite a lot more involved than the Bristuff entry. However, if your billion card is different to ours you can copy our entry and change it to suit. Once done you can redo your probe and you should see something like this.
Found following card...
00:07.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
Subsystem: Cologne Chip Designs GmbH ISDN Board
Flags: bus master, medium devsel, latency 16, IRQ 217
I/O ports at ee00 [disabled] [size=8]
Memory at e8124000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
... 1 mISDN card(s) of this type found.
Zaptel view of card in /proc/zaptel/1
Span 1: ZTDUMMY/1 "ZTDUMMY/1 1"
I know this all looks very complex but you are running an alpha release which is not yet fully documented.
Kind Regards
Selintra
-
Hello,
I don't mind... but can you tel me commands to do it?
Thx. JM
-
Just check whether the bilion record is in your database - it should be.
db selintra show pci:1397:2bd0:1397:2bd0
Also check your billion card with lspci -vvn to make sure its the same as ours.
As long as it is then just delete the row you added with
db selintra-work delete pci:1397:2bd0:1075:c101
db selintra delete pci:1397:2bd0:1075:c101
Then go to PCIcards. Press initialise to clearout the old stuff and then redo your probe.
That should be it.
Best
S
-
Hello,
I don't have a Initialize option/button available in PCI Cards, only Probe.
I did that and it returns:
Loaded wctdm...
Zaptel view of card in /proc/zaptel/1
Span 1: ZTDUMMY/1 "ZTDUMMY/1 1"
JM
-
Did you check the billion card records and your billion card like I described?
Best
S
-
Hello,
I did check that the Billion pci:1397:2bd0:1397:2bd0 exists.
I executed the 2 commands to delete my wrong entry.
Then I went to PCI cards and didn't found any initialize option/button, and did the Probe with the results I sent you.
JM
-
What did lspci -nvv tell you about your Billion card?
S
-
Hello,
This is the output from lspci -nvv:
login as: root
root@192.168.253.3's password:
Last login: Thu Jul 19 21:50:46 2007 from pc-00242.mycompany.local
[root@servidor3 ~]# lspci -nvv
00:00.0 Class 0600: 1039:0661 (rev 11)
Subsystem: 1039:0661
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 32
Region 0: Memory at e8000000 (32-bit, non-prefetchable) [size=64M]
Capabilities: [c0] AGP version 3.5
Status: RQ=32 Iso- ArqSz=2 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
00:01.0 Class 0604: 1039:0003
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: ec000000-ec0fffff
Prefetchable memory behind bridge: e0000000-e7ffffff
Secondary status: 66Mhz+ FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B-
00:02.0 Class 0601: 1039:0964 (rev 36)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:02.5 Class 0101: 1039:5513 (rev 01) (prog-if 80 [Master])
Subsystem: 1462:7060
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin ? routed to IRQ 169
Region 0: I/O ports at <unassigned>
Region 1: I/O ports at <unassigned>
Region 2: I/O ports at <unassigned>
Region 3: I/O ports at <unassigned>
Region 4: I/O ports at 4000
Capabilities: [58] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:02.7 Class 0401: 1039:7012 (rev a0)
Subsystem: 1462:b010
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (13000ns min, 2750ns max)
Interrupt: pin C routed to IRQ 177
Region 0: I/O ports at e000 [size=256]
Region 1: I/O ports at e100 [size=128]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:03.0 Class 0c03: 1039:7001 (rev 0f) (prog-if 10)
Subsystem: 1462:7060
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (20000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 185
Region 0: Memory at ec125000 (32-bit, non-prefetchable) [size=4K]
00:03.1 Class 0c03: 1039:7001 (rev 0f) (prog-if 10)
Subsystem: 1462:7060
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (20000ns max), Cache Line Size 08
Interrupt: pin B routed to IRQ 193
Region 0: Memory at ec120000 (32-bit, non-prefetchable) [size=4K]
00:03.2 Class 0c03: 1039:7001 (rev 0f) (prog-if 10)
Subsystem: 1462:7060
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (20000ns max), Cache Line Size 08
Interrupt: pin C routed to IRQ 201
Region 0: Memory at ec121000 (32-bit, non-prefetchable) [size=4K]
00:03.3 Class 0c03: 1039:7002 (prog-if 20)
Subsystem: 1462:5332
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (20000ns max)
Interrupt: pin D routed to IRQ 209
Region 0: Memory at ec122000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:04.0 Class 0200: 1039:0900 (rev 90)
Subsystem: 1462:7060
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (13000ns min, 2750ns max)
Interrupt: pin A routed to IRQ 217
Region 0: I/O ports at e200 [size=256]
Region 1: Memory at ec123000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:05.0 Class 0104: 1039:0180 (rev 01) (prog-if 85)
Subsystem: 1462:7060
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin A routed to IRQ 225
Region 0: I/O ports at e300
Region 1: I/O ports at e400
Region 2: I/O ports at e500
Region 3: I/O ports at e600
Region 4: I/O ports at e700
Region 5: I/O ports at e800 [size=128]
Capabilities: [58] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:06.0 Class 0280: 1397:2bd0 (rev 02)
Subsystem: 1075:c101
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 16 (4000ns max)
Interrupt: pin A routed to IRQ 225
Region 0: I/O ports at e900
Region 1: Memory at ec124000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
01:00.0 Class 0300: 1039:6330
Subsystem: 1462:7060
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 169
BIST result: 00
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at ec000000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at d000 [size=128]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] AGP version 3.0
Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
[root@servidor3 ~]#
My Billion is the one that starts with "00:06.0 Class 0280: 1397:2bd0 (rev 02)".
Thx.
JM
-
Hello,
Any ideias?
Maybe I should go with the production version?
Thx.
JM
-
We have not seen this signature on a Billlion card before. We will incorporate it into the next 1.2 and 1.4 asterisk rpms.
Kind Regards
S
-
Hello,
How can I fix my problem now?
Thx.
JM
-
Try this
ftp://81.149.154.14/Pre-Releases/selintra-sail-2.1.15-502.noarch.rpm
It has been updated to recognise your card.
Kind Regards
S
-
Hello,
How should I proceed?
Should I remove the previous version first?
Should I use yum or rpm to do it?
Thx.
JM
-
Yum or rpm is fine. No need to remove existing.
Best
S
-
Hello,
I will do more testing during this week, but it seems to be working.
Thanks.
Now I would like to add a 2nd card (same model) and connect it to my legacy PBX.
The objective is this:
ISDN network -> SME+SAIL -> Legacy PBX
Can I just add the 2nd one or there will be problems?
If I understood correctly I have to change the mode from TE to NT on the card that connects to the legacy PBX. Is this correct?
How can I configure SAIL to send all calls coming from the ISDN Network (1st card) to the legacy PBX (using the 2nd card)?
Thx.
JM
-
You can add as many cards as you have slots in your PC.
Before you set a card into NT mode read...
http://www.selintra.com/docs/cgi-bin/view/Main/DocChapter224
You need a special cable (ISDN Crossover) and you may need help to set up your routing correctly - i.e. a modified version of SAIL.
Best
S
-
Hello,
I will test incoming calls on the card already installed first and then go attack that new problem (NT mode).
I have 2 new questions:
1.
I'm configuring a route to outgoing calls.
I want the call to go to a VoIP provider 1st and if that doesn't work go through the ISDN lines.
Can I use the mISDN[TEPP] as the 2nd option (without a 3rd) or must I use the individual channels as the 2nd and 3rd options?
2.
I've edited the sip.conf and iax.conf in the Headers because I've assumed that in doing so SAIL would accept the new changes the next time it started. In this specific case I added some codecs (gsm and ilbc) to the list of both protocols because I noticed that when I create a new extension or trunkline it only assumes ulaw and alaw.
Unfortunately it doesn't comply with my changes.
Am I doing something wrong or is it a bug?
Thx.
JM
-
Hi
1. TEPP is fine- it means the same as group in a ZAP dial.
2. Headers (particularly CODEC entries) are overridden by trunk/extension entries. If you want to handle iLBC on a given trunk then change it in the trunk edit window, not in the header.
SAIL does not simply permit ulaw/alaw - read about it here...
http://www.selintra.com/docs/cgi-bin/view/Main/DocChapter06#Optimise_Speech_Compression_for
Kind Regards
S
-
Hello,
I've read the link you sent me, but I'm confused because it states:
"You can override/modify the SAIL strategy by adding CODECs of your own choice in the headers, trunklines and extensions panels."
If I'm understanding correctly this implies that I could change the headers to my choice. But what is the point of changing the headers, if I need to change the trunks and extensions.
I think it would be simpler to replicate the change in the headers to new extensions and/trunks, keeping the old ones like they are.
Thx.
JM
-
I think it would be simpler to replicate the change in the headers to new extensions and/trunks, keeping the old ones like they are.
Won't work. Extensions and trunks override headers. Headers are only there to suggest a default in the case that an extension or trunk specifies nothing.
Best
S
-
Hello,
OK. Understood.
In that case where can I change de default com ulaw, alaw to anything else? In my case is gsm, ilbc, alaw, ulaw.
Where can I find the codecs for g723.1 and g729?
Thx.
JM
-
In that case where can I change de default com ulaw, alaw to anything else? In my case is gsm, ilbc, alaw, ulaw.
Read the section in the docs page again here...
http://www.selintra.com/docs/cgi-bin/view/Main/DocChapter06#Optimise_Speech_Compression_for
You set up CODEC defaults in Globals. We don't actively support iLBC because it gives poor sound quality and uses lots of CPU in transcoding. Neither do we actively support G723 because G729 and gsm do such a good job. However you can still use iLBC/g723 if you wish by specifying them at trunk or extension level provided your VoIP carrier or phones support them (many carriers do not support either, few SIP hard phones support iLBC).
Where can I find the codecs for g723.1 and g729?
Both are proprietary codecs. You need to purchase licences to use them. G729 licences and codec from www.digium.com. Don't know about g723 - we've never used it - suggest you google for it.
Best
S
-
Hello,
OK. Thanks.
JM
-
Hello,
Outgoing calls through the PCI card are working.
Unfortunatelly the incoming ones are not.
If I reconnect the legacy PBX it (legacy PBX) works.
What can I check to find the error?
I created a greeting and configured the default open and closed to the to it (it is called IVR).
I tried the same config to an extension, with the same result.
My trunklines tabel shows:
mISDN1-1, default, ISDN, Layer 2 UP, TE - PTP, mISDN, None, IVR, IVR, plugged icon, ACT OK
mISDN1-2, default, ISDN, Layer 2 UP, TE - PTP, mISDN, None, IVR, IVR, plugged icon, ACT OK
Thx.
JM
-
Hello,
I've found another strange behaviour.
If I remove the ISDN cable, the column "VOIP Host IP
ISDN Data Layer" changes to "Layer 2 DOWN", the column "VOIP Port
ISDN Active Mode" to N/A and the column "State" to a yellow triangle.
If I reconnect the cable, the 1st 2 columns stay the same and only the 3rd changes to the plugged icon.
Th only way I know to change them back, is by rebooting the server.
Is this correct? Shouldn't it change automatically to "Layer 2 UP" and "TE - PTP"?
Thx.
JM
-
Hello,
I've found another strange behaviour.
If I remove the ISDN cable, the column "VOIP Host IP
ISDN Data Layer" changes to "Layer 2 DOWN", the column "VOIP Port
ISDN Active Mode" to N/A and the column "State" to a yellow triangle.
If I reconnect the cable, the 1st 2 columns stay the same and only the 3rd changes to the plugged icon.
Th only way I know to change them back, is by rebooting the server.
Is this correct? Shouldn't it change automatically to "Layer 2 UP" and "TE - PTP"?
Thx.
JM
Hi Jmatos,
The situation you describe only means Layer 1 to be active ( cable detected - connected ) but Layer 2 not active.
Since you are TE, the other end should be 'responsible' to force Layer 2 to come up.
Best,
Hervé
-
Hello,
It is strange, because the legacy PBX works fine if I disconnect the cable and then reconnect.
-
Hello,
It is strange, because the legacy PBX works fine if I disconnect the cable and then reconnect.
Are you sure your 'provider NT' and 'legacy PBX TE' are programmed for point to point (PTP) ISDN ?.
If you don't know for sure, pls ask your provider.
Best ,
Hervé