Results 1 to 2 of 2

Thread: ERROR[22783] chan_pika.c: Error: Unable to bind socket

  1. #1
    stmcknig Guest

    Default ERROR[22783] chan_pika.c: Error: Unable to bind socket

    I see this from time to time in the log,

    [Jul 27 18:48:03] ERROR[22783] chan_pika.c: Error: Unable to bind socket: Address already in use

    Doesn't seem to be stopping anything from working but I can't find much detail on the error - is the 'c' reference to say the third FXO/FXS channel?

    Here's what I have in my Warp channels status - I know channel 1 and 2 are down as they have nothing plugged into them.

    Group: 0, type FXO: channels: 1 to 4
    PIKA Channel Asterisk Group: 0, type FXO: channels: 1 to 4
    Channel number: 1, asterisk group: 0 type: FXO, state = CHANNEL IS DOWN
    Channel number: 2, asterisk group: 0 type: FXO, state = CHANNEL IS DOWN
    Channel number: 3, asterisk group: 0 type: FXO, state = CHANNEL IS READY
    Channel number: 4, asterisk group: 0 type: FXO, state = CHANNEL IS READY

    Group: 1, type FXS: channels: 1 to 1
    PIKA Channel Asterisk Group: 1, type FXS: channels: 1 to 1
    Channel number: 1, asterisk group: 1 type: FXS, state = CHANNEL IS READY

    Group: 3, type AUDIO: channels: 1 to 1
    PIKA Channel Asterisk Group: 3, type AUDIO: channels: 1 to 1
    Channel number: 1, asterisk group: 0 type: AUDIO, state = CHANNEL IS READY

  2. #2
    Join Date
    Jul 2008
    Posts
    268

    Default

    This error is related to the line-in audio port on the Warp and its interaction with the streamplayer. It should not affect any TDM connectivity.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •