system toolbox » voip

ovdje našao detalje vezano za prelazak na english firmware

uređaj je na ovoj adresi od zadnji put http://192.168.45.114/

telnet by dialing #96*7*

bringout@nmraka-2:~$ telnet 192.168.45.114

Trying 192.168.45.114...
Connected to 192.168.45.114.
Escape character is '^]'.
Fritz!Box web password: 

BusyBox v1.8.2 (2009-03-27 11:37:25 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

ermittle die aktuelle TTY
tty is "/dev/pts/0" 
Console Ausgaben auf dieses Terminal umgelenkt

1. cat /dev/mtdblock3 > /var/mtd3.bin

http://www.nat32.com/nat32e/htm/fritz.htm

http://www.tecchannel.de/server/extra/432803/tuning_hacks_fritzbox_fritz_box_erweiterungen_ftp_telnet/index9.html

ftp server

# cd /var/tmp
# 
# wget http://www.tecchannel.de/download/fritz.box/bftpd.conf 
Connecting to www.tecchannel.de (213.61.120.18:80)
bftpd.conf           100% |*******************************|   830  --:--:-- ETA
# 
# wget http://www.tecchannel.de/download/fritz.box/bftpd 
Connecting to www.tecchannel.de (213.61.120.18:80)
bftpd                100% |*******************************| 64584  --:--:-- ETA
# ./bftpd -d -c /var/tmp/bftpd.conf
-sh: ./bftpd: Permission denied
# chmod +x bftpd
# ./bftpd -d -c /var/tmp/bftpd.conf

ovo je gore bio nepotreban korak, ftp server je ustvari recovery mode ovog router-a

unutar 5 sekundi od priključenja routera zakačiti se na ftp

bringout@xp-desk-ubuntu:~$ sudo ip addr add 192.168.178.2/24 dev eth0

bringout@xp-desk-ubuntu:~$ ftp 192.168.178.1
Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
Name (192.168.178.1:bringout): adam2
331 Password required for adam2
Password:
230 User adam2 successfully logged in
Remote system type is AVM.

ftp> quote SETENV firmware_version avme
200 SETENV command successful
ftp> quote REBOOT
221 Thank you for using the FTP service on ADAM2
ftp>

zakačio se na http://192.168.178.1/

i tu setovao engleski kao jezik

uključio expert mode i podesio opet 192.168.45.114 ip adresu

kod internet provajdera dodao internet via L1 (lan1) i podesio gateway 192.168.45.254 i dns naš - nakon toga imamo internet

999 je sip account -> hernad_pc (asterisk.bring.out.ba)

i to radi samo za jedan kanal, ako pokušamo i drugi kanal to ne radi, on zvnoni. kada ovaj drugi kanal uradi hangup on prekine i prvu vezu koja je ovako uspostavljena

dobro to bi se moglo riješiti sa outgoing sip limitom, ali to nije rješenje

takođe ne radi transfer (a kada direktno testiram ext asterisk ifold 711 (gizmo echo test) transfer radi ...)

mrka kapa sve u svemu

kada preko ekstenzija pozovem (sa prefixom) "*121#" - gizmo, "*122#" - asterisk hernad_pc to radi (prikopčao obični analogni telefon

fritz kao samostalan pbx ?¶

**12 - analogni telefon

**620 - voip-1

transfer na gigasetu ne radi "R" - nije aktivno

Firmware version:      021910000000 / 043.00
EEPROM version:     159

Gigaset C470 IP / C475 IP / S675 IP / S685 IP Firmware update 04/2009

Download version: 02184

• ...
• VoIP: Call transfer via R key <<<<<<<<<<<<<<<<<<<<<<<<,
• VoIP: An incoming call indicated in parallel at different VoIP devices (parallel ringing) will not be stored in the "Missed calls" list if the call was accepted at one of the devices.
• ..

ali džabe to ne radi kada je voip konekcija

hajde da probam dect - uzeo jedan gigaset i prikopčao

ali on šuti kada idem na 122#60 npr ili na gizmo direktno ... interesatno je da ako uradim vezu preko običnog telefona i uradim transfer na ovaj lokal (*610 je on) tada imam normalan zvuk

ludnica pa eto

grandstream ne mogu ni registrovati ?!!!!!!!!!!!!!!!!!!!!!!!

bio je setovan nat traversal (stun)

idem ponovo pokušati e sad je ok

na grandstream ne dozvoljava *123 ... promjenio dialplan: "{[*x].}"

ne ni ovaj ne radi, probao: "{**x.|*xx#x.|x.}" ni ovaj ne radi

radi **12, ne radi *122#

ni ovo ne radi

{**x.|*xxx#x.|x.}

interesantan forum thread

Hello,

First of all, I hope it’s ok to post in English over here (as I don’t write/read German).

Here is my situation:
- I’m currently testing the latest version of trixbox (asterisk 1.2.9.1; linux kernel 2.6.9-34.0.1.EL; DistroCentOS release 4.3 (Final)).
- I bought an AVM Friztbox FON WLAN 7050 (UK version, annexB part # 20002327 ). The firmware revision is 14.03.91.

I’m trying to use this fritzbox as gateway for outbound and inbound ISDN calls.

1) I tried the (default) SIP option to do so: the asterisk is defined as “internet telephony” account. There are some limitations: for outbound calls (asterisk -> isdn), one needs to use “call through” feature; and for inbound calls (ISDN -> asterisk) call divert feature. In this latter case, ISDN caller ID is replaced by the fritzbox ID on the IP interface. Following avm support, this is normal and can not be changed.

2) CAPI over TCP: I enabled capi over tcp in the fritzbox by the code #96*3*. This is working as I was able to receive/dial calls over this interface with FRITZ!fon windows utility. Now, I don’t find any information on how to implement capi_over_TCP at the asterisk side. I’ve seen several CAPI softwares, but as far as I understand, they are intended for local hardware cards. Are some of them capable of sending CAPI over TCP? If yes, where do you configure the fritzbox IP address (and TCP port)?
3) I guess there are other ways enabled by changing the firmware. However, in my case, I’m a bit worry about this option: my original firmware (UK version, annex B DSL modem) isn’t published by AVM. So modifying it will be irreversible. And for the German ones, I don’t see the distinction between annex A/annex B models… And ok, I admit this is easier for me to deal with an English interface rather than a German one ;)

So, any advice is welcome!

Best regards,
Luka.

All German versions (I mean the country not the language) are Annex B (ISDN compatible) and therefore must be somehow possible to use with your box.

http://www.melware.org/MelwareWiki

http://www.voip-info.org/wiki/index.php?page=Asterisk+CAPI+channels

Remote CAPI: ISDN over TCP
One interesting use of this technology would be to be able to run Asterisk completely independent from hardware (in a virtual machine for example) while still supporting ISDN connectivity, using cheap, reliable and easy to find ISDN "bridges" (Cisco 801's for example, or an AVM Fritz!Box).

Remote CAPI already exists for a specific protocol (Bintec). This protocol is used by rcapid as well, a daemon which exports local CAPI ISDN hardware via TCP using the bintec protocol. With rcapid you can use the ISDN hardware remotely within windows with the 'brickware' (by Funkwerk/Bintec) or from another linux host with the melware modified libcapi20 (ftp://ftp.melware.de).

So you do can have an Asterisk server with chan-capi and the modified libcapi20 connected via TCP to the CAPI server running rcapid. If you want to use that Cisco router as CAPI server instead, then you just might need to extend the libcapi20 to support that protocol as well.

Currently we can find Cisco 801 ISDN Routers on ebay for about 40 euro. This equipment supports RCAPI (CAPI over TCP) Think of it as a isdn-ethernet adapter. There are other manufacturers who support this protocol in their ISDN devices. (AVM, Bintec, Draytek)

Howto: Using the S0 (BRI) on Fritz!Box Fon 7050 via remote capi rcapid on Linux (here: OpenSuSE)

Using rcapid compared to AVM-NetCAPI on the Fritz!Box has the advantage that there's a linux client available for it (update: Since Apr 2008 there's also a libcapi20 available for the AVM-NetCAPI, see blow). Please note that since a Fritz!Box only contains a passive ISDN card/controller any G3 fax communication needs be managed by an application (e.g. fax4box, HylaFax, CapiSpFax) - this capability is not provided by the exposed CAPI.

In general: Programs that use CAPI on Linux require libcapi for that. That libcapi, in return, routes the calls through the network/LAN (by using the kernel drivers) if capi20.conf exists and has valid configuration data. On the other hand, calls are handled the usual way if that capi20.conf is missing.

• German language posting: rcapid on Fritz!Box
• German language posting: faxing from OpenSuSE
• Faxen mit rcapi (german)
• Remote controller not found (german)

Fritz!Box with native NetCAPI and libcap20¶

Please do not confuse this with the rcapi method as outlined above!

• Wiki on how to use the AVM Capi-over-TCP (aka capiovertcp) with Linux, user example
• this approach does not require the installation of rcapid (see above) or any other modification of the Fritz!Box
• can be used together with CapiSpFax from a Linux PC and CUPS and/or GNOME for print-to-fax services.

Background info by Enrik on AVM-NetCAPI: After some playing around, I've finally found out what capiotcp_server is good for. It implements CMTP over TCP. CMTP (Capi Message Transport Protocol) is the protocol that is defined by the bluetooth CIP.

For the sake of completeness here an alternative means to make ISDN calls thru a Fritz!Box with Asterisk (off-topic): Let the Fritz!Box register thru SIP with Asterisk, and arrange a callthrough (Durchwahl) where the Dial() application automatically enters the requested PIN by DTMF. This approach does not require any of the above CAPI magic. :-)

fbrcapi http://fbrcapi.v3v.de/fbrcapi.html¶

Description

fbrcapi (Fritz!Box Remote CAPI over TCP) is a kernel module, for Fritz!Box Fon Routers to transport CAPI messages over TCP.

It uses the transport protocol of the capiotcp_server daemon.

This kernel module is for v2.6.X kernel only.

You'll need CAPI 2.0 subsystem enabled in your kernel and libcapi20 from isdn4linux (libcapi20-3).

Getting started¶

Get the kernel headers:

apt-cache search linux-headers # (see 'uname -r' for the correct version)

The Linux kernel headers should normally be located under /usr/src Of course you'll need CAPI subsystem enabled in your current kernel. Required modules are kernelcapi.ko and capi.ko

Then run make && make install. After that, you can load the module:

modprobe kernelcapi
modprobe capi
modprobe fbrcapi addr=[your FB IP] port=[5031] controllers=[1,2,...] debug=[0-4] boost=[0|1]

The module parameters are optional and only needed, if your Fritz!Box
has another IP than the default one (or for debugging purposes):

        addr=        The Fritz!Box IP address (default: 192.168.178.1)
        port=        The Fritz!Box capiotcp server port (default: 5031)
        debug=    The syslog debugging level
        controllers=  The remote controllers to attach (default: all)
        boost=    Renice kthread process with 1 (default)
                      0 to turn it off

An init script is included in the fbrcapi package (rc.fbrcapi).

To check if everything is ok, you can run capiinfo from the capiutils package. This should show the attached remote CAPI controllers.

To uninstall the module, run: make uninstall.

Attention¶

Remote CAPI should be enabled, when loading the kernel module, otherwise it will fail to load. This is required to attach the CAPI controllers!

      To disable remote CAPI: #96*2*
      To enable remote CAPI:  #96*3*

When connection is lost when the module was loaded, fbrcapi will automatically try to reconnect.

Also, the addr= parameter HAS TO be an IP address!!

Licence

Copyright (C) 2009 Marco Zissen

fbrcapi is free software; you can redistribute it and/or modify
        it under the terms of the GNU General Public License as published by
        the Free Software Foundation; either version 2 of the License, or
        (at your option) any later version.

This program is distributed in the hope that it will be useful,
        but WITHOUT ANY WARRANTY; without even the implied warranty of
        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
        GNU General Public License for more details.

You should have received a copy of the GNU General Public License
        along with this program; if not, write to the Free Software
        Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

ChangeLog

v0.3:
          o fix: Send socket buffer didn't get freed

v0.2:
          o fix: non-linear skb
          o check and give error whenever "addr=..." is not an IP
          o added module parameter "controllers=x,y,..." to enable/disable remote controllers
          o added "make [install|uninstall]" 
          o added init script

v0.1:
          o ported from libcapi20_fb-0.7 (user space / lib) to fbrcapi (kernel space / module) (NG)
          o the default libcapi20 from isdn4linux can be used (no libcapi20 hacking anymore)
          o some module parameters (addr=, port=, debug=, boost=)
          o auto reconnect
          o first release :)

Troubleshooting

When something went wrong, try to increase debug= module parameter and
      look into dmesg. When everything is ok, something like that should be shown:

[44956.628068] fbrcapi: Fritz!Box Remote CAPI over TCP 0.3 (c) 2009 Marco Zissen 
      [44956.628276] fbrcapi: Connecting to Fritz!Box CAPI server 192.168.178.1:5031 ...
      [44956.636022] fbrcapi: Connected successfully!
      [44956.662111] fbrcapi: 5 CAPI controllers found!
      [44956.662724] kcapi: Controller [001]: fbrcapi_ctrl_1 attached
      [44956.663584] kcapi: card [001] "fbrcapi_ctrl_1" ready.
      [44956.664220] kcapi: Controller [002]: fbrcapi_ctrl_2 attached
      [44956.664631] kcapi: card [002] "fbrcapi_ctrl_2" ready.
      [44956.665066] kcapi: Controller [003]: fbrcapi_ctrl_3 attached
      [44956.665461] kcapi: card [003] "fbrcapi_ctrl_3" ready.
      [44956.665835] kcapi: Controller [004]: fbrcapi_ctrl_4 attached
      [44956.666369] kcapi: card [004] "fbrcapi_ctrl_4" ready.
      [44956.666748] kcapi: Controller [005]: fbrcapi_ctrl_5 attached
      [44956.667132] kcapi: card [005] "fbrcapi_ctrl_5" ready.

... and capiinfo should output something like this:

Number of Controllers : 5
      Controller 1:
      Manufacturer: AVM Berlin
      CAPI Version: 2.0
      Manufacturer Version: 0.0-03  (0.3)
      Serial Number: 0004711
      BChannels: 2
      Global Options: 0x00000039
         internal controller supported
         DTMF supported
         Supplementary Services supported
         channel allocation supported (leased lines)
      B1 protocols support: 0x80003c0b
         64 kbit/s with HDLC framing
         64 kbit/s bit-transparent operation
         V.110 synconous operation with HDLC framing
      B2 protocols support: 0x00000003
         ISO 7776 (X.75 SLP)
         Transparent
      B3 protocols support: 0x00000001
         Transparent

0500
        0200
        39000000

remote capi for windows and linux

'fbrcapi' - The new CAPI kernel module for Linux

http://en.opensuse.org/Installing_and_using_modified_capifax_to_remotely_fax_via_CAPI_of_AVM_Fritz!Box_7170

Recent firmwares of several Fritz!Boxes provide a so called remote-capi.

It enables LAN-Clients to send/receive faxes.

Until recently only clients for Windows (AVM) and MAC (3rd-Party) were available.

Thanks to Marco Zissen et. al. a modified version of capifax solving this problem for LINUX is available.

• install/use this modification
• automate the process of
  • preparing/converting documents and
  • sending them via command-line

with the 32-bit-version of OpenSuSE 11.1 and a AVM Fritz!Box 7170 with latest official firmware (no modifications necessary :-).

The reception of faxes was not tested as the latest firmware of Fritz!Box 7170 allows to mail received faxes automatically.

build fbrcapi¶

bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ sudo apt-get install libcapi20-dev

bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ make

make -C /usr/src/linux-headers-`uname -r` M=/home/bringout/asterisk14/fbrcapi-0.3 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.31-13-generic'
  CC [M]  /home/bringout/asterisk14/fbrcapi-0.3/core.o
/home/bringout/asterisk14/fbrcapi-0.3/core.c: In function ‘fbrc_reset_ctr’:
/home/bringout/asterisk14/fbrcapi-0.3/core.c:62: error: implicit declaration of function ‘capi_ctr_reseted’
make[2]: *** [/home/bringout/asterisk14/fbrcapi-0.3/core.o] Error 1
make[1]: *** [_module_/home/bringout/asterisk14/fbrcapi-0.3] Error 2
...

http://bugs.gentoo.org/show_bug.cgi?id=284565

Should be a simple fix -- capi_ctr_reseted was renamed to capi_ctr_down in
2.6.31
Assigning to fcpci maintainers.

bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ sudo make install

mkdir -p /lib/modules/`uname -r`/kernel/drivers/isdn/capi
cp fbrcapi.ko /lib/modules/`uname -r`/kernel/drivers/isdn/capi
depmod -a

uključio remote capi preko telefona

bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ sudo modprobe fbrcapi addr=192.168.45.114 port=5031 controllers=1,2,3,4 debug=4 boost=0

[18475.985755] capifs: Rev 1.1.2.3
[18595.013755] CAPI Subsystem Rev 1.1.2.8
[18600.830615] capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
[19949.566663] fbrcapi: Fritz!Box Remote CAPI over TCP 0.3 (c) 2009 Marco Zissen <maz@v3v.de>
[19949.566715] fbrcapi: Connecting to Fritz!Box CAPI server 192.168.45.114:5031 ...
[19949.596066] fbrcapi: Unable to connect (error -111)!
[21315.841349] fbrcapi: Fritz!Box Remote CAPI over TCP 0.3 (c) 2009 Marco Zissen <maz@v3v.de>
[21315.841425] fbrcapi: Connecting to Fritz!Box CAPI server 192.168.45.114:5031 ...
[21315.872982] fbrcapi: Connected successfully!
[21315.872998] fbrcapi: Starting kthread() ...
[21315.873110] fbrcapi: fbrc_recv_message() thread started ...
[21315.883451] fbrcapi: hdr 0x40 hdrlen 2 len 82 skblen 84 skbdatalen 0
[21315.883489] fbrcapi: PROFILE  : 82 0 0 0 32 129 1 0 0 0 2 0 69 2 0 66 0 0 5 0 0 0 0 0 0 0
[21315.883521] fbrcapi: 5 CAPI controllers found!
[21315.883572] kcapi: Controller [001]: fbrcapi_ctrl_1 attached
[21315.883578] fbrcapi: Attaching local controller #1 --> remote controller #1
[21315.883728] kcapi: card [001] "fbrcapi_ctrl_1" ready.
[21315.883753] kcapi: Controller [002]: fbrcapi_ctrl_2 attached
[21315.883760] fbrcapi: Attaching local controller #2 --> remote controller #2
[21315.883776] kcapi: card [002] "fbrcapi_ctrl_2" ready.
[21315.883787] kcapi: Controller [003]: fbrcapi_ctrl_3 attached
[21315.883793] fbrcapi: Attaching local controller #3 --> remote controller #3
[21315.883802] kcapi: card [003] "fbrcapi_ctrl_3" ready.
[21315.883814] kcapi: Controller [004]: fbrcapi_ctrl_4 attached
[21315.883820] fbrcapi: Attaching local controller #4 --> remote controller #4
[21315.883828] kcapi: card [004] "fbrcapi_ctrl_4" ready.
[21315.886221] fbrcapi: hdr 0x40 hdrlen 2 len 82 skblen 84 skbdatalen 0
[21315.886255] fbrcapi: PROFILE  : 82 0 0 0 32 129 1 0 0 0 2 0 69 2 0 66 0 0 1 0 2 0 57 0 0 0
[21315.886273] fbrcapi: hdr 0x40 hdrlen 2 len 82 skblen 252 skbdatalen 0
[21315.886289] fbrcapi: PROFILE  : 82 0 0 0 32 129 1 0 0 0 2 0 69 2 0 66 0 0 1 0 2 0 57 0 0 0
[21315.886299] fbrcapi: hdr 0x40 hdrlen 2 len 82 skblen 168 skbdatalen 0
[21315.886313] fbrcapi: PROFILE  : 82 0 0 0 32 129 1 0 0 0 2 0 69 2 0 66 0 0 1 0 2 0 57 0 0 0
[21315.886323] fbrcapi: hdr 0x40 hdrlen 2 len 82 skblen 84 skbdatalen 0
[21315.886341] fbrcapi: PROFILE  : 82 0 0 0 32 129 1 0 0 0 2 0 69 2 0 66 0 0 1 0 1 0 57 0 0 0

bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ capiinfo

Number of Controllers : 4
Controller 1:
Manufacturer: AVM Berlin
CAPI Version: 2.0
Manufacturer Version: 0.0-03  (0.3)
Serial Number: 0004711
BChannels: 2
Global Options: 0x00000039
   internal controller supported
   DTMF supported
   Supplementary Services supported
   channel allocation supported (leased lines)
B1 protocols support: 0x80003c0b
   64 kbit/s with HDLC framing
   64 kbit/s bit-transparent operation
   V.110 synconous operation with HDLC framing
B2 protocols support: 0x00000003
   ISO 7776 (X.75 SLP)
   Transparent
B3 protocols support: 0x00000081
   Transparent
   Modem

  0100
  0200
  39000000
  0b3c0080
  03000000
  81000000
  00000000 00000000 00000000 00000000 00000000 00000000
  01000001 00020000 00000000 00000000 00000000

Supplementary services support: 0x000003ff
   Hold / Retrieve
   Terminal Portability
   ECT
   3PTY
   Call Forwarding
   Call Deflection
   MCID
   CCBS

Controller 2:
Manufacturer: AVM Berlin
CAPI Version: 2.0
Manufacturer Version: 0.0-03  (0.3)
Serial Number: 0004711
BChannels: 2
Global Options: 0x00000039
   internal controller supported
   DTMF supported
   Supplementary Services supported
   channel allocation supported (leased lines)
B1 protocols support: 0x80003c0b
   64 kbit/s with HDLC framing
   64 kbit/s bit-transparent operation
   V.110 synconous operation with HDLC framing
B2 protocols support: 0x00000003
   ISO 7776 (X.75 SLP)
   Transparent
B3 protocols support: 0x00000081
   Transparent
   Modem

  0100
  0200
  39000000
  0b3c0080
  03000000
  81000000
  00000000 00000000 00000000 00000000 00000000 00000000
  01000001 00020000 00000000 00000000 00000000

Supplementary services support: 0x000003ff
   Hold / Retrieve
   Terminal Portability
   ECT
   3PTY
   Call Forwarding
   Call Deflection
   MCID
   CCBS

Controller 3:
Manufacturer: AVM Berlin
CAPI Version: 2.0
Manufacturer Version: 0.0-03  (0.3)
Serial Number: 0004711
BChannels: 2
Global Options: 0x00000039
   internal controller supported
   DTMF supported
   Supplementary Services supported
   channel allocation supported (leased lines)
B1 protocols support: 0x80003c0b
   64 kbit/s with HDLC framing
   64 kbit/s bit-transparent operation
   V.110 synconous operation with HDLC framing
B2 protocols support: 0x00000003
   ISO 7776 (X.75 SLP)
   Transparent
B3 protocols support: 0x00000081
   Transparent
   Modem

  0100
  0200
  39000000
  0b3c0080
  03000000
  81000000
  00000000 00000000 00000000 00000000 00000000 00000000
  01000000 20020000 00000000 00000000 00000000

Supplementary services support: 0x000003ff
   Hold / Retrieve
   Terminal Portability
   ECT
   3PTY
   Call Forwarding
   Call Deflection
   MCID
   CCBS

Controller 4:
Manufacturer: AVM Berlin
CAPI Version: 2.0
Manufacturer Version: 0.0-03  (0.3)
Serial Number: 0004711
BChannels: 1
Global Options: 0x00000039
   internal controller supported
   DTMF supported
   Supplementary Services supported
   channel allocation supported (leased lines)
B1 protocols support: 0x80003c0b
   64 kbit/s with HDLC framing
   64 kbit/s bit-transparent operation
   V.110 synconous operation with HDLC framing
B2 protocols support: 0x00000003
   ISO 7776 (X.75 SLP)
   Transparent
B3 protocols support: 0x00000081
   Transparent
   Modem

  0100
  0100
  39000000
  0b3c0080
  03000000
  81000000
  00000000 00000000 00000000 00000000 00000000 00000000
  01000000 40020000 00000000 00000000 00000000

Supplementary services support: 0x000003ff
   Hold / Retrieve
   Terminal Portability
   ECT
   3PTY
   Call Forwarding
   Call Deflection
   MCID
   CCBS

bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ ls /dev/capi*

/dev/capi20

/dev/capi:

run asterisk

bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ sudo chmod o+x+w+r /var/run/asterisk/asterisk.ctl
bringout@nmraka-2:~/asterisk14/fbrcapi-0.3$ asterisk -rvvvvvvvvvvvvvvvvv

sinoć sam uspio preko ovog fbrcapi uspostaviti dolaznu i ulazni poziv

podesio grand1

[grand1]
type=friend
context=from-sip                
callerid=John Doe <1234>        
host=dynamic
username=grand1
password=sar...

extensions.conf

[isdn-in]
exten => 33269292,1,Answer
exten => 33269292,2,Dial(sip/grand1,15)

;
[from-sip]
exten => 10,1,Dial(CAPI/ISDN1/061141311,15)
exten => 11,1,Dial(CAPI/ISDN1/061477105,15)
exten => 12,1,Dial(CAPI/ISDN1/061479130,15)
exten => 60,1,Echo

[default]
;
; By default we include the demo.  In a production system, you 
; probably don't want to have the demo there.
;
include => demo
include => from-sip
include => isdn-in

root@nmraka-2:/etc/asterisk# modprobe fbrcapi addr=192.168.45.114 port=5031 controllers=1,2,3,4,5 debug=4 boost=0

testirao pozive direktno preko asteriska -> bjasko mob, to je ok

ali preko fbrcapi (asterisk) isprekidano

sumnjam na nmraka-2

idem podesiti fbrcapi na atom-1 ovaj nmraka-2 izdiše

bringout@atom-1:~/devel/chan_capi-1.1.4$ sudo make install

bringout@atom-1:~/devel/fbrcapi-0.3$ vi core.c

:% s/capi_ctr_reseted/capi_ctr_down/cg

bringout@atom-1:~/devel/fbrcapi-0.3$ sudo make install

root@atom-1:/etc/asterisk# vi modules.conf

load => chan_capi.so

#apt-get remove ufw

preko atom-a radi remote capi fbrcapi ko melčin horoz, jasko je naravno rekao da zvuk i nije neki a sale je rekao - dobar

od sad samo sa saletom testiram

pokušao sam transfer ali ne radi

dodao u dial "tT" ali i dalje ništa na grandstreamu dodajem rfc

podesio "rfc..." na grandstream

1. ostvarim vezu sa saletom
2. pritisnem taraba
3. ukucam 061141311 ... (odmah mene prekine nakon toga)
4. javim se na mob i pričam sa saletom

evo šta koonzola kaže:

*CLI> core show channels

Channel              Location             State   Application(Data)             
CAPI/ISDN1#01/061141 (None)               Up      AppDial((Outgoing Line))      
CAPI/ISDN1#02/061479 10@from-sip:1        Up      Dial(CAPI/ISDN1/061141311,15,t
2 active channels
1 active call
4 calls processed

dobro je sve asterisk funkcije rade

zaključak¶

fritz!box nam može koristiti kao voip gateway

kako će se ponašati fritz u slučaju kada server bude opterećen ? pa mislim da će se to samo manifestovati ovim prekidima (lošijim zvukom) kao što je bilo sa nmraka-2 ali neće doći do čučnjavanja skroz kako je to sa zaptelom slučaj

ovdje je audio procesiranje ipak najvećim dijelom na fritz-u, a server samo handlira pozive i radi asterisk-pbx dio procesiranja

podesio na 192.168.45.111 giga1 sip account i ponovo pozvao

kaže jasko sad je super

*CLI> sip show peer giga1

  * Name       : giga1
  Secret       : <Not set>
  MD5Secret    : <Not set>
  Remote Secret: <Not set>
  Context      : from-sip
  Subscr.Cont. : <Not set>
  Language     : 
  AMA flags    : Unknown
  Transfer mode: open
  CallingPres  : Presentation Allowed, Not Screened
  Callgroup    : 
  Pickupgroup  : 
  Mailbox      : 
  VM Extension : asterisk
  LastMsgsSent : 32767/65535
  Call limit   : 0
  Dynamic      : Yes
  Callerid     : "John Doe 2" <1234>
  MaxCallBR    : 384 kbps
  Expire       : 55
  Insecure     : no
  Nat          : RFC3581
  ACL          : No
  T38 pt UDPTL : No
  DirectMedia  : Yes
  PromiscRedir : No
  User=Phone   : No
  Video Support: No
  Text Support : No
  Ign SDP ver  : No
  Trust RPID   : No
  Send RPID    : No
  Subscriptions: Yes
  Overlap dial : No
  DTMFmode     : rfc2833
  Timer T1     : 500
  Timer B      : 32000
  ToHost       : 
  Addr->IP     : 192.168.45.111 Port 5060
  Defaddr->IP  : 0.0.0.0 Port 5060
  Prim.Transp. : UDP
  Allowed.Trsp : UDP
  Def. Username: giga1
  SIP Options  : replaces replace 
  Codecs       : 0x8000e (gsm|ulaw|alaw|h263)
  Codec Order  : (none)
  Auto-Framing :  No 
  100 on REG   : No
  Status       : Unmonitored
  Useragent    : C470IP021910000000
  Reg. Contact : sip:giga1@192.168.45.111:5060
  Qualify Freq : 60000 ms
  Sess-Timers  : Accept
  Sess-Refresh : uas
  Sess-Expires : 1800 secs
  Min-Sess     : 90 secs
  Parkinglot   :

takođe testirao transfer - prebaci ga na echo aplikaciju

šta nam je bitno ostalo¶

• testirati adsl via fritz
• ip refresh via fritz
• vidjeti capi4hylafax
• vidjeti šta sam fritz za faksove može uraditi (čitao sam da on to može)

podesio sam E-mail Forwarding za fax, s tim što sam morao reći da je smtp server 192.168.45.189 (nije znao po imenu mail-gw-10.sigma-com.net naći smtp server)

fritz!box Fax reception¶

podesio telefoni device "Fax reception" koji će handlirati 269-292

root@m1-fbze.fuelboss.com.ba:~# sendfax -1 -n -f hernad@bring.out.ba -R -d 033269292 test.ps
request id is 1351 (group id 1351) for host localhost (1 file)

radi Fax reception ko melčin horoz

slanje faxova via fritz¶

mislim da što se tiče windows mašina tu nema problema fritz!box sigurno ima svoje drajvere kojima se kači

to treba vidjeti u uputstvu

fritz!box Fax device¶

koliko sam skontao tu fritz pita na koji port (recimo FON2 analogna linija 2 za analogne faksove) je spojen fax uređaj - eksterni fax device

tako da možemo kombinovati sa fizičkim i fritzom kao primaocem fax poruka

nama ovaj fax device u principu ne treba podešavati jer ako ga stavimo na 269292 on će handlirati fax a ne fritz-email

instalirao fritz!fax na xp-desk. instalira se fritz!fax printer driver, kao i klijentska aplikacija za slanje fax-ova

Jedini problem je što je stvar na njemačkom. Nisam našao englesku verziju

aplikacija se zove fritz!fax for fritz!box

inače aplikacija sama nađe fritz!box uređaj u lan-u

upustvo, slanje faxova¶

deinstalirao sam aplikaciju, da mi ne prlja instalaciju

ja sam tražio ali nigdje nisam našao englesku verziju, ako i nema, nije problem. Jasko ionako treba napraviti uputstvo za slanje faxova na wiki-ju za klijente http://redmine.bring.out.ba/projects/klijenti/wiki

ovaj fritz me stvarno nervira sa ovim svojim sve na njemačkom ... pola toga nema na engleskom ...

1. ps w
   

     PID  Uid        VSZ Stat Command
       1 root       1424 S   init       
       2 root            RWN [ksoftirqd/0]
       3 root            SW  [watchdog/0]
       4 root            SW< [events/0]
       5 root            SW< [khelper]
       6 root            SW< [kthread]
      18 root            SW< [kblockd/0]
      32 root            SW  [pdflush]
      33 root            SW  [pdflush]
      34 root            SW< [kswapd0]
      35 root            SW< [aio/0]
      72 root            SW  [pm_info]
      76 root            SW< [CPMAC]
      80 root            SW  [mtdblockd]
     102 root            SW  [tffsd_mtd_0]
     216 root            SW  [cleanup_timer_f]
     227 root            SW  [dectuart_route]
     235 root            SWN [jffs2_gcd_mtd5]
     281 root            SW< [capi_oslib]
     282 root            SW< [capi_oslib]
     283 root            SW  [capitransp]
     290 root            SW  [glob_codecs]
     294 root            SW  [avm_dect_thread]
     296 root            SW  [ksock tcp worke]
     297 root            SW  [ksock tcp serve]
     314 root            SW< [khubd]
     385 root       9676 R N ctlmgr 
     650 root       9676 S N ctlmgr 
     654 root       9676 R N ctlmgr 
     658 root       9676 S N ctlmgr 
     663 root       9676 S N ctlmgr 
     665 root       9676 S N ctlmgr 
     736 root       4628 S   upnpd 
     756 root       3112 S   multid -t 
     767 root       3404 S   dsld -i -n 
     776 root       1428 S   telnetd -l /sbin/ar7login 
     777 root       5628 S   telefon a127.0.0.1 
     781 root       4672 S < voipd 
     786 root       3004 S   pbd 
     787 root       3004 S   pbd 
     792 root       3004 S   pbd 
     793 root       3004 S   pbd 
     795 root       1424 S   /usr/sbin/inetd 
     798 root        980 S   /bin/run_clock -c /dev/tffs -d 
     804 root       3408 S   dect_manager 
     810 root       1424 S   init       
     812 root       2716 S   /usr/bin/faxd -a 
     815 root       2096 S   capiotcp_server -p5031 -m99 
     821 root       3112 S   multid -t 
     825 root       2636 S   usermand 
     828 root       4628 S   upnpd 
     829 root       4628 S   upnpd 
     830 root       4628 S   upnpd 
     833 root            RWN [kdsld_token]
     888 root       1304 S   /sbin/chronyd -f /var/tmp/chrony.conf 
    1142 root       1440 R   -sh 
    1261 root      14144 R   -sh 
    1320 root       1440 S   -sh 
    1359 root       1424 R   ps w
   

haman da si uhako konekciju ja sad nemogu prići bhingco mreži

mala izmjena lokala, pošto grandstream ima mogučnost 3 simultana poziva putem jednog sip- nema potrebe da se 2 sip accounta registruju.

ostavljam dakle smo lokal 50 na koji će dolaziti svi dolazni pozivi.

deregistrovao sip 51 sa grandstream telefona, izbacio ga iz default konteksta

testirao simultani poziv sa seidom na oba broja ..OK