system toolbox » voip

šta je ključna stvar u ovome svemu: mi ne možemo jednostavno locirati kada se isdn kartica "zblazni"

u zadnjih par imamo novi set problema i poruka koje su prijavljene ali je handliranje svih asterisk problema još i jednostavan problem, to uvijek možemo uhvatiti i poduzeti odgovarajuće akcije

međutim, ovo "otkačivanje" zaptel-a od isdn-a je stvar koja je ključni problem

znači ono što me interesuje da li zaptel na bilo koji način može pingati isdn liniju

http://updates.xorcom.com/astribank/bristuff/1.4/INSTALL.html

http://bristuff.org/index.php/Main_Page

AGX's Asterisk Extra AddOns is a collection of external asterisk apps that cannot make it into Asterisk. Work done by Antonio Gallo.

• app_pickup2 - BRIstuff's Pickup, renamed as Pickup2 to avoid collisions.
• app_devstate

asterisk 1.6 ?

koliko sam upratio radi sa bristuff karticama

Early testing of Asterisk 1.6 using hash tables shows a SIP performance increase compared to 1.4 of factor 3 to 4 (seemnigly planned for Asterisk 1.6.1)

http://www.asteriskguru.com/archives/bristuff-users-cause-34-sum-up-vt124168.html
Symptoms
Users cannot issue any outgoing call though Basic Rate Interface lines are not all busy.
Each time this happens, logs show "WARNING²⁶⁰⁸³ app_dial.c: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)" (from /var/log/asterisk/full).

• A m- 1.4.17-BRIstuffed-0.4.0-test6 (olivier)
• B - "last 3 versions of asterisk 1.2 bristuffed" (paco)
• C - 0.3.0-PRE-1y-p or 0.3.0-PRE-1y-k (gunnar)

Frequency
No message during a couple of days then up to 30 messages a day.
Restarting Asterisk (asterisk -rx "restart when convenient") restores outgoing call capability for a new period of time.

Steps to reproduce symptoms:
None identified at the moment

Investigations:
Direction 1 : "Energy saving mode"

This issue might occur because Telco are entering energy-saving mode (Michiel).
Forbidding this energy saving mode fixed this.

We're using the same Telco (France Telecom) in 5 locations.
Problems occur in a single location where brand new BRI lines were provisioned.
Obviously, every morning, lines were inactive for last several hours, so lines should be "asleep".
In spite of that, we had no message for the first call in the morning.

1. Where can you read about energy-saving mode in ISDN BRI access ?
2. How can you check Telco enabled energy-saving mode ?

For me, it is very difficult to any reliable data from Telco on this.
Having a way to check things on my own would be very useful.

3. Beside Michiel, who has ever cured these symptoms after forbidding energy-saving mode ?
4. Why does this occur in 2008 ? Is this a new trend in Telco habbits ? BRI lines are here for years.

Direction 2 : reporting to Software editor

Has someone filed a bug report to Junghanns ?

If positive, is there anything ongoing on this ?

Should this be also handled to Digium ?

Regards

https://www.trixbox.org/forums/trixbox-forums/trunks/nt-or-te-mode-beronet-billion-spain-zaphfc

Hello, grolo. Please, read the following link:http://www.trixbox.org/modules/newbb/viewtopic.php?viewmode=thread&topic_id=5714&forum=2 here. It is a common practice of Telefonica to drop Layer 1 of ISDN Links after 2minutes and 30 seconds to save energy. That setting causes the Beronet Billion to report HDLC empty and HDLC CRC frame errors. After 3 minutes, all circuits (both B channels) are disabled and it is not possible to dial out ("all ciruits are busy now" message). When you receive an incoming call, Layer 1 wakes up again, and it will go down 3 minutes after hangup.
Please, request Telefonica's technical assistance service to change Layer 1 of your ISDN Link to be UP permanently. This issue really drove me crazy during a whole month after successfully compiling BriStuff drivers. A complete nightmare...
Regards,
RHawk1

upravo ovo se dešava kod nas !!

Layer 1 of your ISDN Link to be UP permanently

http://www.ralphb.net/ISDN/proto_l1.html

Each U interface frame is 240 bits long. At the prescribed data rate of 160 kb/s, each frame is therefore 1.5 ms long. Each frame consists of:

• Frame overhead - 16 kb/s
• D channel - 16 kb/s
• 2 B channels at 64 kb/s - 128 kb/s

Sync
18 bits 12 * (B1 + B2 + D)
216 bits Maintenance
6 bits

• The Sync field consists of 9 Quaternaries (2 bits each) in the pattern +3 +3 -3 -3 -3 +3 -3 +3 -3.
• (B1 + B2 + D) is 18 bits of data consisting of 8 bits from the first B channel, 8 bits from the second B channel, and 2 bits of D channel data.
• The Maintenance field contains CRC information, block error detection flags, and "embedded operator commands" used for loopback testing without disrupting user data.

Data is transmitted in a superframe consisting of 8 240-bit frames for a total of 1920 bits (240 octets). The sync field of the first frame in the superframe is inverted (i.e. -3 -3 +3 +3 +3 -3 +3 -3 +3).

root@ifold:~# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)
0 active channels
0 active calls

čim sam pozvao sa svog telefona mobitel

root@ifold:~# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)
Zap/1-1              061141311@bringoutba Dialing AppDial((Outgoing Line))
SIP/20-b5e06ae8      061141311@bringoutba Ring    Dial(zap/g1/061141311| 400| tT
2 active channels
1 active call

čim sam prekinuo

root@ifold:~# asterisk -rx 'core show channels'
Channel              Location             State   Application(Data)
0 active channels
0 active calls

čim sam pozvao mobitel -> 269291

root@ifold:~# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)
Zap/1-1              33269291@bringoutba: Ring    Wait(1)
1 active channel
1 active call

gornje komande "iščupao" od http://zaptel.tzafrir.org.il/README.Astribank.html

vrlo su korisne

ovdje sam pominjao testiranje postojećeg stanja, sa gornjim komandama i ami interfejsom može se većina toga postići

čak sada vidim da se ne mora uspostaviti veza, poenta je da se locira ulazni poziv, i ako je sve uredu odmah se može prekinuti veza, tako da to možemo koristiti kao svojevrstan "high level ping" stanja sistema

šta dobijama kada pozovem echo test sa 60-ke

root@ifold:~# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)
SIP/20-b5e03be0      60@bringoutba:1      Up      Playback(demo-echotest)
1 active channel
1 active call

dobro to je to

stanje kada je vsasa nazvao na jednu a ja na drugu liniju:

root@ifold:~# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)
SIP/31-08251730      (None)               Up      Bridged Call(Zap/2-1)
Zap/2-1              33269291@bringoutba: Up      Dial(sip/20&sip/21&sip/31&sip/
SIP/20-08231d40      (None)               Up      Bridged Call(Zap/1-1)
Zap/1-1              33269291@bringoutba: Up      Dial(sip/20&sip/21&sip/31&sip/
4 active channels
2 active calls

fino vidimo dva aktivna poziva

a vidi sad ovo, pozvaću sam sebe preko 269291

root@ifold:~# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)
SIP/31-0824f8b8      (None)               Up      Bridged Call(Zap/2-1)
Zap/2-1              33269291@bringoutba: Up      Dial(sip/20&sip/21&sip/31&sip/
Zap/1-1              (None)               Up      Bridged Call(SIP/20-b5e02650)
SIP/20-b5e02650      269291@bringoutba:3  Up      Dial(zap/g1/269291|400|tT)
4 active channels
2 active calls

imam isti efekat - prijem poziva od 269291 i poziv na 269291 - znači dva zauzeta kanala.

Šta sa ovim mogu uraditi: mogu pozvati sam sebe i staviti se u wait stanje par sekundi, i asteris sam sebe može dijagnosticirati

email behudin, lejla, adnan, ferid from bhtelecom

Selam alejkum,
ne znam ko mi može pomoći pa pišem svim svojim telecom ahbabima :)

Pretpostavljam da je Strikan guru za ovo, ali tamam da se i Vama ostalim javim hehe.

1) ISDN energy saving mode

imamo jedan problem sa VoIP telefonijom (asterisk prikopčan na ISDN liniju)  koja izgleda ima veze sa postavkama vaših centrala.
Raja po svijetu se žali da se dešava to da se linija nakon "idle" režima jednostavno diskonektuje i uđe u power-saving režim. To opet ISDN kartica protumači kao da je isdn linija u kvaru i izgleda da se zblazni

Ima li šanse da se to provjeri na centrali i uključi. To me konkretno muči kod mog klijenta Rm-lh

200420 i 201490

2) Poziv bez odgovora, tarifiranje

Ako ovo prvo ne mogu uticati, palo mi je na pamet, da uradim jedan "ping" linije periodično (ili echo test kako vam volja), i to na ovaj način:
a) nazovem sam sebe 200420 zove ponovo 200420, ili 201490 svejedno
b) podesim sistem da na svoje pozive ne odgovara
c) pratim na voip sistemu da li je registrovan poziv - ako jeste linija je ok, prekidam poziv
d) ako nije sistem mi je čučno, moram nešto poduzeti

Znači u ovom mom test scenariju, jedan kanal će pozvati drugi kanal, ali se veza neće uspostaviti. Da li se neodgovoreni poziv tarifira ?

evo sam ovdje

context in {

        33269290 => {
                Wait(1);
                Answer();
                if  ( "${CALLERID(num)}" =~ "061141311" )  {
                        NoOp(zvaojehernad);
                };

                Dial(${STAN_SVI},${DEFTIMEOUT}, tT);
        };

        33269291 => {
                if  ( "${CALLERID(num)}" =~ "26929" )  {
                         <<<<<<<<<<<<<<<<<<<<<<<<<<<<< napravio čeku
                        NoOp("pingam sam sebe ${CALLERID(num)}   .................");
                        Wait(5);
                        Answer();
                        hangup();
                 } else
                       Wait(1);

                Answer();
....

evo šta log kaže

   -- Executing [33269291@bringoutba:1] GotoIf("Zap/2-1", "5?2:7") in new stack
    -- Goto (bringoutba,33269291,2)
    -- Executing [33269291@bringoutba:2] NoOp("Zap/2-1", ""pingam sam sebe 269291   ................."") in new stack
    -- Executing [33269291@bringoutba:3] Wait("Zap/2-1", "5") in new stack
    -- Accepting voice call from '269291' to '33269291' on channel 0/2, span 1
    -- Zap/1-1 is ringing
    -- Executing [33269291@bringoutba:4] Answer("Zap/2-1", "") in new stack
    -- Executing [33269291@bringoutba:5] Hangup("Zap/2-1", "") in new stack
  == Spawn extension (bringoutba, 33269291, 5) exited non-zero on 'Zap/2-1'
    -- Hungup 'Zap/2-1'
    -- Zap/1-1 answered SIP/20-b5e09a30
    -- Channel 0/1, span 1 got hangup request, cause 16
    -- Hungup 'Zap/1-1'
  == Spawn extension (bringoutba, 269291, 3) exited non-zero on 'SIP/20-b5e09a30'

ferid se javio

takođe mi je ferid u tel razgovoru rekao da se ništa ne tarifira ako se ne ostvari veza

jedna stvar što me je malo bunila jeste što u debian repos-u postoji asterisk-bristuff, međutim vidim da je to virtualni paket a da asterisk provide tu bristuff funkcionalnost ...

ma da i ja sam kod dualca postavio obični asterisk s tim što sam dodao zaptel-a

http://www.asteriskguru.com/tutorials/bri.html

S/T interface

The S/T interface is the part on the ISDN modem to which all other ISDN devices connect in order to communicate over ISDN. An additional piece of hardware called an NT1 must be placed between the ISDN device and the wall jack to terminate the line. The point between the NT1 and the wall jack is the U interface. Many ISDN modems and adapters have a U interface option that builds the NT1 into their hardware. These devices can be connected directly into the ISDN wall jack. (Note that in Europe, the ISDN wall jack is an S/T interface point rather than a U interface point.)

U interface The U interface connects NT1 terminated ISDN devices to the telephone company's ISDN network. Many ISDN devices have a U interface option, which means they have the NT1 termination device built into their hardware. These U-type devices can be connected directly to the ISDN wall jack. A device that doesn't have a built-in NT1 has an S/T interface. (Note that in Europe S/T devices can be connected directly to the ISDN wall jack.)

juče sam se čitav dan vozao sa ifold-om i internetom

naime internet je juče totalno loš, a ja sam opet ganjao informacije vezano za ISDN/asterisk ... put to totalne sreće ...

bilo kako bilo juče sam instalirao na ifold mISDN 1.1.9 #17023 i njega sam na kraju ostavio

izvršio sam podešenja na extensions.ael tako da razlike između zaptel i misdn interfejsa funkcionišu.

borio sam se satima sa adhearsion-om (ASTERISK ami interfejs) ali ne baš uspješno. Cilj mi je da napravim test na nivou asteriska da li su isdn kanali u funkciji (ping isdn, echo loop - to sam pominjao gore u pismu Striki)

officesa: prvi sms ne prolazi ...¶

1. šaljem sms deaktivacija alarma ... ništa
2. zovem sa mobitela officesa, asterisk mi se javalja
3. ponovo šaljem sms, ovaj pud dobijam u par sekundi feedback

Zašto ? mislim da je centrala ujutro u power save režimu i da sms poruka je izgleda ne "oživi". Ovaj moj poziv je pak oživi i zato drugi pokušaj prolazi

sa svog mobitela pozvao fax njihov:

root@rmlh-1:/etc# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)             
IAX2/iaxfax_1-3      (None)               Up      Bridged Call(Zap/1-1)         
Zap/1-1              200421@rmlh:3        Up      Dial(IAX2/iaxfax_1/200421) <<<<<<<<<<<<<<<    
SIP/89-007fed40      (None)               Up      Bridged Call(SIP/12-00809190) 
SIP/12-00809190      800496115650036@rmlh Up      Dial(SIP/89/00496115650036|400
4 active channels
2 active calls

kasnije lovim ovo:

root@rmlh-1:/etc# asterisk -rx 'core show channels'

Channel              Location             State   Application(Data)             
SIP/89-007fed40      (None)               Up      Bridged Call(SIP/12-00809190) 
SIP/12-00809190      800496115650036@rmlh Up      Dial(SIP/89/00496115650036|400
2 active channels
1 active call

ova 89-ka je onaj skype kanal, sip.conf

[89]
type=friend
username=skype1
password=......
host=192.168.77.103
nat=no
drmfmode=auto
canreinvite=no
quality=yes
insecure=very