[Logo] Forum VOIP - totul despre voice over ip
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Configurare fluxuri E1 Asterisk  XML
Forum Index » Despre Asterisk
Author Message
Nini

[Avatar]

Joined: 21/11/2007 13:54:51
Messages: 90
Offline

Acest topic se doreste o baza de date pentru configurarea fluxurilor E1 oferite de diversi provideri din Romania.

In masura in care vom primi si alte date le vom adauga in primul "post". Ca de obicei, comentariile si sugestiile voastre sunt bine venite.

/etc/zaptel.conf sau /etc/dahdi/system.conf

/etc/asterisk/zapata.conf sau /etc/asterisk/chan_dahdi.conf


Nota: Nu uitati sa mentionati ca fluxul sa fie configurat la provider cu CRC - de obicei aceasta configurare este implicita dar exista cazuri cand providerul "uita" sa mentioneze acest aspect.

Cateva clarificari, bazate pe informatiile obtinute de pe www.voip-info.org:

busydetect: If enabled, Asterisk will analyze the audio coming in on the line during a call or a dial attempt to attempt to recognize busy signals. This is useful on analog trunk interfaces both to detect a busy signal when dialing out, and for detecting when the person has hung up. Be sure that you don't use this on digital interfaces. Otherwise you will run in "broken calls" problems. Default=no.

callprogress: Asterisk can attempt to monitor the state of the call to listen for a ringing tone, busy tone, congestion tone, and sounds indicating that the line has been answered. It appears that this feature is independent of the busydetect feature; it seems that both can run in parallel, and both will independently attempt to recognize a busy tone. The callprogress feature is highly experimental and can easily detect false answers, so don't count on it being very accurate. Also, it is currently configured only for standard U.S. phone tones. Default: no.

overlapdial: Whether Asterisk can dial this switch using overlap digits. Default: no. If you need Direct Dial-in you should change this to yes, then Asterisk will wait after the last digit it receives

resetinterval: Sets the time in seconds between restart of unused channels, defaults to 3600, minimum 60 seconds. Some PBXs don't like channel restarts. so set the interval to a very long interval e.g. 100000000 or 'never' to disable *entirely*.
For example, in Israel, Bezeq doesn't like the B-Channel resets happening on the lines, it is best to set the resetinterval to 'never' when installing a box in Israel. Other ones experience also shows that this parameter may also cause issues on local switches in the UK and China.

pridialplan: Sets an option (outgoing ISDN number plan) required for some (rare) switches that require a dialplan parameter to be passed. This option is ignored by most PRI switches. It may be necessary on a few pieces of hardware. Valid options are: unknown, local, private, national, and international. This option can almost always be left unchanged from the default. Default: national.

prilocaldialplan: Same like pridialplan but is referring to incoming ISDN number plan.

priindication: Tells how Asterisk should indicate Busy() and Congestion() to the switch/user. Default: inband.
Accepted values are:
# inband: Asterisk plays indication tones without answering; not available on all PRI/BRI subscription lines
# outofband: Asterisk disconnects with busy/congestion information code so the switch will play the indication tones to the caller. Busy() will now do same as setting PRI_CAUSE=17 and Hangup().

This message was edited 8 times. Last update was at 24/03/2011 23:29:33

Nini

[Avatar]

Joined: 21/11/2007 13:54:51
Messages: 90
Offline

Mai jos sunt prezentate cateva detalii utile pentru configurarea corecta a dialplan-ului Asterisk.

Situatii in care nu se trimite prima cifra (0) din CallerID pentru apeluri incoming
1. Pentru fluxul Ines pe care-l folosim in biroul din Bucuresti
2. Pentru fluxul Romtelecom folosit de un client in Galati
3. Pentru fluxul Vodafone folosit de un client din Bucuresti

--- Aparent toti providerii trimit callerID-ul fara 0 ---
Aceasta se poate rezolva prin directionare apelurilor catre un context nou, asa cum e mentionat mai jos

"Called number" pentru apeluri incoming
1. Ultimele 6 cifre, pentru fluxul Romtelecom folosit de un client in Galati
2. 10 + ultimele 2 cifre, pentru flxul Vodafone folosit de un client in Bucuresti

Setari CallerID pentru apeluri outgoing
1. Utimele 4 cifre, pentru fluxul Ines pe care-l folosim in biroul din Bucuresti
2. 10 + ultimele 2 cifre, pentru flxul Vodafone folosit de un client in Bucuresti

"Called number" pentru apeluri outgoing
1. Prefix 9 pentru fluxul Vodafone folosit de un client in Bucuresti

This message was edited 2 times. Last update was at 24/03/2011 23:16:15

Marge

[Avatar]

Joined: 09/02/2011 13:14:49
Messages: 5
Location: Timisoara
Offline

Pentru update... Client E1 Vodafone, din Deta, Jud Timis,.
DID-ultimele 9 cifre (deci fara 0).
pridialplan=national
prilocaldialplan=local

This message was edited 2 times. Last update was at 23/02/2013 10:09:31


"Only two things are infinite: the universe and human stupidity; and I'm not sure about the universe." Albert Einstein
[WWW]
 
Forum Index » Despre Asterisk
Go to:   
Proudly promoted by Loudhush and MODULO Consulting