Fritz USB 2.1 chan_capi-cm ISDN Performance-Problem

[mbier]

Hallo,

ich habe eine Fritz USB 2.1 an einem dezidiertem PBX-Rechner (MMX mit 200 MHz, Linux Kernel 2.6.15) hängen. Ich weiss - recht schwachbrüstig, aber wenn 7/24 im Betrieb verbraucht er weniger Strom wie eine x GHz-Maschine.
Die Fritz hängt am internen S0 einer ISDN-TK-Anlage.

VoIP, Ansagen, VoiceMail, ... funktioniert.

Mein Problem ist ein externer Anruf.
Laut DialPlan soll versucht werden eine interne Nebenstelle über CAPI zu wählen. Da beginnt Asterisk zu stottern: Der Anrufer hört das Läuten nur mehr stotternd und manchmal hängt sich die Asterisk überhaupt auf -> kein "stop" / "stop gracefully" mehr mögich, nur mehr "kill".

Ich habe in Asterisk einen hohen "verbose"-Level und CAPI-Debug eingeschaltet.

Die wahrscheinlich fragliche Sequenz:

INFO_RESP ID=001 #0x769d LEN=0012
  Controller/PLCI/NCCI            = 0x201

    -- ISDN1: info element ALERTING
    -- CAPI/ISDN1/2-1c is ringing
  == ISDN1: Requested RINGING-Indication for CAPI/ISDN1/-1b
    -- ISDN1: attempting ALERT in state 2
INFO_IND ID=001 #0x769e LEN=0017
  Controller/PLCI/NCCI            = 0x201
  InfoNumber                      = 0x1e
  InfoElement                     = <81 88>

INFO_RESP ID=001 #0x769e LEN=0012
  Controller/PLCI/NCCI            = 0x201

    -- ISDN1: info element PI 81 88
       > ISDN1: In-band information available
    -- CAPI/ISDN1/2-1c is making progress passing it to CAPI/ISDN1/-1b
  == ISDN1: Requested PROGRESS-Indication for CAPI/ISDN1/-1b
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
       > ISDN1: too much voice to send for NCCI=0x10101
INFO_IND ID=001 #0x76e8 LEN=0015
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0x8045
  InfoElement                     = default

Wenn das ein Performance-Problem ist, kann man diese noch beeinflussen?

Ausschnitt aus capi.conf:

...
[ISDN1]          ;this example interface gets name 'ISDN1' and may be any
                 ;name not starting with 'g' or 'contr'.
isdnmode=msn     ;'MSN' (point-to-multipoint) or 'DID' (direct inward dial)
                 ;when using NT-mode, 'DID' should be set in any case
incomingmsn=*    ;allow incoming calls to this list of MSNs/DIDs, * = any
                 ;this caller id will be used when dial option 'd' is set.
controller=1     ;capi controller number to use
group=1          ;dialout group
softdtmf=on      ;enable/disable software dtmf detection, recommended for AVM cards
relaxdtmf=on     ;in addition to softdtmf, you can use relaxed dtmf detection
accountcode=     ;Asterisk accountcode to use in CDRs
context=capi-in  ;context for incoming calls
                 ;set to 'local' (default value), no hold is done and Asterisk may
                 ;play MOH.
immediate=yes   ;DID: immediate start of pbx with extension 's' if no digits were
                 ;     received on incoming call (no destination number yet)
                 ;MSN: start pbx on CONNECT_IND and don't wait for SETUP/SENDING-COMPLETE.
                 ;     info like REDIRECTINGNUMBER may be lost, but this is necessary for
                 ;     drivers/pbx/telco which does not send SETUP or SENDING-COMPLETE.
                 ;(possible values: 'no', 'yes', 'force', 'g164', 'g165')
echocancelold=yes;use facility selector 6 instead of correct 8 (necessary for older eicon drivers)
devices=2        ;number of concurrent calls on this controller
                 ;(2 makes sense for single BRI, 30 for PRI)

Ausschnitt aus extensions.conf:

...
; CAPI [
;--------------------------------------------------
[capi-in]
exten => s,1,Goto(MainMenu,s,1)
exten => s,2,Hangup
;--------------------------------------------------
; CAPI ]
...
; MainMenu [
;--------------------------------------------------
[MainMenu]
exten => s,1,Background(welcome-mainmenu)       ; Ansage
exten => 1,1,Goto(User2,s,1)                    ; -> User2
exten => 2,1,Goto(User1,s,1)                    ; -> User1
exten => 3,1,Goto(User3User4,s,1)               ; -> User3User4
exten => s,2,WaitExten(10|m)                    ; Warte auf Taste
exten => s,3,Goto(s,1)                          ; Loop
exten => i,1,Goto(s,1)                          ; Invalid
exten => t,1,Hangup                             ; TimeOut
;--------------------------------------------------
; MainMenu ]
...
; User1 [
;--------------------------------------------------
[User1]
exten => s,1,Ringing
exten => s,n,Wait,2
exten => s,n,Dial(CAPI/ISDN1/3,20)              ; Nebenstelle 3, 20 Sekunden timeout
exten => s,n,Voicemail,u100
exten => i,n,Hangup
exten => t,n,Hangup
;--------------------------------------------------
; User1 ]

; User2 [
;--------------------------------------------------
[User2]
exten => s,1,Ringing
exten => s,n,Wait,2
exten => s,n,Dial(CAPI/ISDN1/2,20)             ; Nebenstelle 2, 20 Sekunden timeout
;exten => s,n,Dial(SIP/200|20|m)                        ; 20 Sekunden timeout, mit MusicOnHold
exten => s,n,Voicemail,u200
exten => i,n,Hangup
exten => t,n,Hangup
;--------------------------------------------------
; User2 ]
...

Asterisk 1.2.5
chan_capi-cm-0.6.5

Besten Dank für jeden Tipp.

mbier

 

[armincm]

Eigentlich haette ich gesagt, dass die 200MHz ausreichen, aber es sieht doch nach einem Perfomance Problem aus. Es koennte aber auch einfach am USB liegen...

"too much voice to send" bedeutet, dass Voice-Pakete fuer das CAPI device zu schnell kommen. Zum Beispiel weil vorher die Pakete ausblieben, also ein Jitter existiert.

Armin