[chan-capi-users] capicommand chat

Jens Vagelpohl jens at dataflake.org
Tue Mar 18 17:32:11 CET 2008


I'm trying out capicommand chat. This is my system:

  - chan_capi 1.10
  - Asterisk 1.4.11
  - divas driver  Rel:3.0.9-107.775-1  Rev:1.46  Build: 107-103(local)
  - CentOS 5.1
  - Diva Server BRI-2M 2.0 PCI

I get the following symptoms:

  - the first caller is correctly added to the conference (with or  
without on-hold-music, as set in the capicommand invocation)
  - the second caller will always generate an error (see below)

This is what I have in extensions.conf:

; 2015 is a CAPI CHAT conference
exten => 2015,1,capicommand(chat|meeting||1)
exten => 2015,2,Hangup()

The log below is what I see on the console. The first caller dials in  
and is put into the conference. The second caller dials in and causes  
the error. The second caller hangs up. Then the first caller hangs up.

Any help appreciated :-)

jens

-----------------------------------------------------------
     -- Accepting AUTHENTICATED call from 192.168.168.10:
        > requested format = ulaw,
        > requested prefs = (),
        > actual format = ulaw,
        > host prefs = (ulaw|gsm),
        > priority = mine
     -- Executing [2015 at privileged:1] capicommand("IAX2/jens-2", "chat| 
meeting||1") in new stack
     -- IAX2/jens-2-NULLPLCI: added new chat member to room  
'meeting' (1)
     -- Executing [2015 at privileged:1] capicommand("SIP/s75-099509a8",  
"chat|meeting||1") in new stack
[Mar 18 17:21:21] ERROR[6227]: chan_capi_utils.c:319  
log_capi_error_message: CAPI error sending CONNECT_REQ                 
ID=002 #0x1f78 LEN=0044
   Controller/PLCI/NCCI            = 0x21
   CIPValue                        = 0x0
   CalledPartyNumber               = default
   CallingPartyNumber              = default
   CalledPartySubaddress           = default
   CallingPartySubaddress          = default
   BProtocol
    B1protocol                     = 0x1
    B2protocol                     = 0x1
    B3protocol                     = 0x0
    B1configuration                = default
    B2configuration                = default
    B3configuration                = default
    GlobalConfiguration            = default
   BC                              = default
   LLC                             = default
   HLC                             = default
   AdditionalInfo
    BChannelinformation            = <03 00 00 00 00 00 00>
    Keypadfacility                 = default
    Useruserdata                   = default
    Facilitydataarray              = default
    SendingComplete                = default
  (NCCI=0x21) (error=0x1108 OS Resource error (no memory ?))
[Mar 18 17:21:23] WARNING[6227]: chan_capi.c:296 capi_wait_for_b3_up:  
SIP/s75-099509a8-NULLPLCI: timed out waiting for b3 up.
     -- Executing [2015 at privileged:2] Hangup("SIP/s75-099509a8", "")  
in new stack
   == Spawn extension (privileged, 2015, 2) exited non-zero on 'SIP/ 
s75-099509a8'
     -- IAX2/jens-2-NULLPLCI: removed chat member from room  
'meeting' (1)
     -- Hungup 'IAX2/jens-2'
        > IAX2/jens-2-NULLPLCI: CAPI INFO 0x3303: Protocol error layer 3
fon*CLI>




More information about the Chan-capi-users mailing list