.titleBar { margin-bottom: 5px!important; }

Chan Capi 4.0 Pre 1

Dieses Thema im Forum "Asterisk ISDN mit CAPI (chan_capi, chan_capi_cm)" wurde erstellt von rannseier, 25 Apr. 2005.

  1. rannseier

    rannseier Aktives Mitglied

    Registriert seit:
    5 Mai 2004
    Beiträge:
    986
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
  2. thorsten.gehrig

    thorsten.gehrig Mitglied

    Registriert seit:
    14 Juni 2004
    Beiträge:
    490
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Hi
    nicht besonders gut kenntlich gemacht - aber trotzdem gefunden :-D
    Hier sind die änderungen:
    - ATTENTION! the dialstring syntax now uses the zaptel dialstring syntax
    it used to be: Dial(CAPI/[@]<outgoingMSN>:[b|B]<destination>)

    now it is: Dial(CAPI/g<group>/[b|B]<destination>)
    or: Dial(CAPI/contr<controller>/[b|B]<destination>)

    CLIP/CLIR is now uses the calling presentation of the calling channel, this can
    be modified using the CallingPres() application. Use CallinPres(32) for CLIR.
    That is why the msn= param in capi.conf is now obsolete. The callerID is also
    taken from the calling channel.

    - fixes for BSD (Jan Stocker)

    Gruß
    Thorsten
     
  3. thorsten.gehrig

    thorsten.gehrig Mitglied

    Registriert seit:
    14 Juni 2004
    Beiträge:
    490
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Hi
    also compiliert klieg ich´s nicht. Ich verwende die letzte Brit-Stuff-Version.
    beim make bekomme ich
    Code:
    debian:/usr/src/chan_capi-0.4.0-PRE1# make
    gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -g  -I/usr/include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686  -DCAPI_ES -DCAPI_GAIN -DCAPI_SYNC -DASTERISKVERSION=\"\" -DCVS_HEAD -Wno-missing-prototypes -Wno-missing-declarations -DCRYPTO   -c -o chan_capi.o chan_capi.c
    chan_capi.c: In function `capi_call':
    chan_capi.c:674: error: structure has no member named `cid'
    chan_capi.c:730: error: structure has no member named `cid'
    chan_capi.c:741: error: structure has no member named `cid'
    chan_capi.c:741: error: structure has no member named `cid'
    chan_capi.c:741: error: structure has no member named `cid'
    chan_capi.c:741: error: structure has no member named `cid'
    chan_capi.c:741: error: structure has no member named `cid'
    chan_capi.c: In function `capi_read':
    chan_capi.c:864: error: structure has no member named `cid'
    chan_capi.c: In function `capi_new':
    chan_capi.c:1110: error: structure has no member named `cid'
    chan_capi.c:1111: error: structure has no member named `cid'
    chan_capi.c: In function `change_callingpres':
    chan_capi.c:2637: error: structure has no member named `cid'
    chan_capi.c: At top level:
    chan_capi.c:2646: error: variable `capi_tech' has initializer but incomplete type
    chan_capi.c:2647: error: unknown field `type' specified in initializer
    
    und wenn ich das make-file anpasse (#CFLAGS+=-DCVX_HEAD) dann kommt
    Code:
    debian:/usr/src/chan_capi-0.4.0-PRE1# make
    gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -g  -I/usr/include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686  -DCAPI_ES -DCAPI_GAIN -DCAPI_SYNC -DASTERISKVERSION=\"\" -Wno-missing-prototypes -Wno-missing-declarations -DCRYPTO   -c -o chan_capi.o chan_capi.c
    chan_capi.c:2646: error: variable `capi_tech' has initializer but incomplete type
    chan_capi.c:2647: error: unknown field `type' specified in initializer
    chan_capi.c:2647: warning: excess elements in struct initializer
    chan_capi.c:2647: warning: (near initialization for `capi_tech')
    chan_capi.c:2648: error: unknown field `description' specified in initializer
    chan_capi.c:2648: warning: excess elements in struct initializer
    chan_capi.c:2648: warning: (near initialization for `capi_tech')
    chan_capi.c:2652: error: unknown field `capabilities' specified in initializer
    chan_capi.c:2652: warning: excess elements in struct initializer
    chan_capi.c:2652: warning: (near initialization for `capi_tech')
    chan_capi.c:2654: error: unknown field `requester' specified in initializer
    chan_capi.c:2654: warning: excess elements in struct initializer
    chan_capi.c:2654: warning: (near initialization for `capi_tech')
    chan_capi.c:2655: error: unknown field `send_digit' specified in initializer
    chan_capi.c:2655: warning: excess elements in struct initializer
    chan_capi.c:2655: warning: (near initialization for `capi_tech')
    chan_capi.c:2656: error: unknown field `send_text' specified in initializer
    chan_capi.c:2656: warning: excess elements in struct initializer
    chan_capi.c:2656: warning: (near initialization for `capi_tech')
    chan_capi.c:2657: error: unknown field `call' specified in initializer
    chan_capi.c:2657: warning: excess elements in struct initializer
    chan_capi.c:2657: warning: (near initialization for `capi_tech')
    chan_capi.c:2658: error: unknown field `hangup' specified in initializer
    chan_capi.c:2658: warning: excess elements in struct initializer
    chan_capi.c:2658: warning: (near initialization for `capi_tech')
    chan_capi.c:2659: error: unknown field `answer' specified in initializer
    chan_capi.c:2659: warning: excess elements in struct initializer
    chan_capi.c:2659: warning: (near initialization for `capi_tech')
    chan_capi.c:2660: error: unknown field `read' specified in initializer
    chan_capi.c:2660: warning: excess elements in struct initializer
    chan_capi.c:2660: warning: (near initialization for `capi_tech')
    chan_capi.c:2661: error: unknown field `write' specified in initializer
    chan_capi.c:2661: warning: excess elements in struct initializer
    chan_capi.c:2661: warning: (near initialization for `capi_tech')
    chan_capi.c:2662: error: unknown field `bridge' specified in initializer
    chan_capi.c:2662: warning: excess elements in struct initializer
    chan_capi.c:2662: warning: (near initialization for `capi_tech')
    chan_capi.c:2663: error: unknown field `exception' specified in initializer
    chan_capi.c:2663: warning: excess elements in struct initializer
    chan_capi.c:2663: warning: (near initialization for `capi_tech')
    chan_capi.c:2664: error: unknown field `indicate' specified in initializer
    chan_capi.c:2664: warning: excess elements in struct initializer
    chan_capi.c:2664: warning: (near initialization for `capi_tech')
    chan_capi.c:2665: error: unknown field `fixup' specified in initializer
    chan_capi.c:2665: warning: excess elements in struct initializer
    chan_capi.c:2665: warning: (near initialization for `capi_tech')
    chan_capi.c:2666: error: unknown field `setoption' specified in initializer
    chan_capi.c:2666: warning: excess elements in struct initializer
    chan_capi.c:2666: warning: (near initialization for `capi_tech')
    make: *** [chan_capi.o] Error 1
    
    Any Hints?

    Gruß
    Thorsten Gehrig
     
  4. Karl23

    Karl23 Neuer User

    Registriert seit:
    8 Nov. 2004
    Beiträge:
    108
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Es compiliert mit bristuff-RC8a-CVS und damit mit
    Asterisk aus dem CVS datum 20.4.2005.
     
  5. thorsten.gehrig

    thorsten.gehrig Mitglied

    Registriert seit:
    14 Juni 2004
    Beiträge:
    490
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Ah - bisher habe ich die Bristuff-CVS versionen noch nicht wahrgenommen...

    Danke
    Gruß
    Thorsten
     
  6. Karl23

    Karl23 Neuer User

    Registriert seit:
    8 Nov. 2004
    Beiträge:
    108
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    @thorsten.gehrig

    Mittlerweile gibt es bristuff-RC8b-CVS.

    Wie stabiel ist denn bei Dir chan_capi_0.4.0-PRE1?

    bei meinem Versuchen wurde asterisk nach kurzer Zeit beendet.
     
  7. thorsten.gehrig

    thorsten.gehrig Mitglied

    Registriert seit:
    14 Juni 2004
    Beiträge:
    490
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Hi
    ich habe derzeit kein "Wartungsfenster" für Exprtimente mit CVS-Bristuffs.... daher auch kein chan_capi (98% meiner Gespräche gehen eh über SIP raus - allerdings verwende ich Intern ISDN...)

    Gruß
    Thorsten