Koozali.org: home of the SME Server

Billion PCI BRI (Cologne Chip)

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Billion PCI BRI (Cologne Chip)
« Reply #15 on: July 21, 2007, 05:48:49 PM »
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

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #16 on: July 21, 2007, 09:55:58 PM »
Hello,

How should I proceed?
Should I remove the previous version first?
Should I use yum or rpm to do it?

Thx.

JM

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Billion PCI BRI (Cologne Chip)
« Reply #17 on: July 22, 2007, 11:24:16 AM »
Yum or rpm is fine.  No need to remove existing.

Best

S

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #18 on: July 23, 2007, 11:54:37 AM »
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

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Billion PCI BRI (Cologne Chip)
« Reply #19 on: July 23, 2007, 05:46:56 PM »
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

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #20 on: July 23, 2007, 08:19:46 PM »
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

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Billion PCI BRI (Cologne Chip)
« Reply #21 on: July 25, 2007, 01:42:13 PM »
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

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #22 on: July 25, 2007, 02:08:01 PM »
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

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Billion PCI BRI (Cologne Chip)
« Reply #23 on: July 25, 2007, 07:29:33 PM »
Quote
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

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #24 on: July 25, 2007, 07:42:25 PM »
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

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Billion PCI BRI (Cologne Chip)
« Reply #25 on: July 25, 2007, 08:12:15 PM »
Quote
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).  

Quote
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

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #26 on: July 25, 2007, 08:54:53 PM »
Hello,

OK. Thanks.

JM

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #27 on: August 04, 2007, 11:54:43 PM »
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

jmatos

Billion PCI BRI (Cologne Chip)
« Reply #28 on: August 05, 2007, 12:12:22 AM »
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

Offline hervep

  • ***
  • 70
  • +0/-0
Billion PCI BRI (Cologne Chip)
« Reply #29 on: August 05, 2007, 06:57:37 AM »
Quote from: "jmatos"
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é