Author Topic: Another conferencing call fail.  (Read 3720 times)

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Another conferencing call fail.
« on: June 10, 2015, 08:12:59 AM »
Customer can't create conferences either internal or external. This is the log entry from trying...anyone any thoughts.

  24  Warning  2015/Jun/09  17:31:20  Call Control - Software  INVALID MESSAGE, OFFSET 0:$A60, PC: $24B32 LOG_ID: outpthdlr#1, PROCEDURE: cp_dispatch_with_swid, SEVERITY: cp_major PID: ($8, $5A3) MSG_FUNC_CODE: $4B, MSG_TX_PID: ($8, $5A3), MSG_TX_PROG_NAME: cpconfmgr MSG_DATA: $E $1F $7F  log_outputs_util_en.c;1595 
  23  Warning  2015/Jun/09  17:31:20  Call Control - Software  INVALID MESSAGE, OFFSET 0:$A60, PC: $24B32 LOG_ID: outpthdlr#1, PROCEDURE: cp_dispatch_with_swid, SEVERITY: cp_major PID: ($8, $5A3) MSG_FUNC_CODE: $4B, MSG_TX_PID: ($8, $5A3), MSG_TX_PROG_NAME: cpconfmgr MSG_DATA: $E $1F $7F  log_outputs_util_en.c;1595 
  22  Warning  2015/Jun/09  17:31:19  Call Control - Software  INVALID MESSAGE, OFFSET 0:$A60, PC: $24B32 LOG_ID: outpthdlr#1, PROCEDURE: cp_dispatch_with_swid, SEVERITY: cp_major PID: ($8, $5A3) MSG_FUNC_CODE: $4B, MSG_TX_PID: ($8, $5A3), MSG_TX_PROG_NAME: cpconfmgr MSG_DATA: $E $1F $7F  log_outputs_util_en.c;1595 
  21  Warning  2015/Jun/09  17:31:19  Call Control - Software  SWERR invalid return code, OFFSET 2:$4B5E, PC: $3A5E34 LOG_ID: cpconfmgr#27, PROCEDURE: manage_conference_calls, SEVERITY: cp_major PID: ($8, $5A3)  log_outputs_util_en.c;1595 
  20  Warning  2015/Jun/09  17:31:19  Call Control - Software  SWERR invalid software id, OFFSET 2:$568, PC: $28EAAA LOG_ID: confrm#1, PROCEDURE: setup_conference_call, SEVERITY: cp_major PID: ($8, $5A3) SWID: conference 14  log_outputs_util_en.c;1595 
  19  Warning  2015/Jun/09  17:31:19  Call Control - Software  setup_conference_call_ logged error = invalid software id for PID: $85A3  log_outputs_util_en.c;1595 
  18  Warning  2015/Jun/09  17:31:16  Call Control - Software  Program: chanalloc Offset: 2:00000EBA PC: 00296F4C Program: chanalloc Offset: 2:00000F88 PC: 0029701A Program: confrm Offset: 2:0000089C PC: 0028EDDE   log_outputs_util_en.c;1595 
  17  Warning  2015/Jun/09  17:31:16  Call Control - Software  Free_channel: owner mismatch, active pid = cpconfmg 8-5A3 RX pid = Nil Pid TX pid = Nil Pid RX link and channel: 127-31 TX link and channel: 127-31 Perform a PCM STAT on the link and channel for more info. Traceback:   log_outputs_util_en.c;1595 
  16  Warning  2015/Jun/09  17:31:16  Call Control - Software  Program: chanalloc Offset: 2:00000EBA PC: 00296F4C Program: chanalloc Offset: 2:00000F88 PC: 0029701A Program: confrm Offset: 2:0000089C PC: 0028EDDE   log_outputs_util_en.c;1595


Offline lundah

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1216
  • Country: us
  • Karma: +66/-0
  • Senior Chief Grunt
    • View Profile
Re: Another conferencing call fail.
« Reply #1 on: June 10, 2015, 08:40:58 AM »
Perform a PCM STAT on the link and channel for more info.

Looks like PCM faults. Do a "PCM Totals" maintenance command, find the faults, clear them. Or you could just try rebooting the controller and see if that clears it up.

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: Another conferencing call fail.
« Reply #2 on: June 10, 2015, 10:13:02 AM »
Done that and the PCM totals reports zero faults. Reboot is scheduled for tonight. JOOI the link and channel referenced (127 -31) does not exist on the switch according to PCM totals which says 28-28 for the link range.

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: Another conferencing call fail.
« Reply #3 on: June 11, 2015, 01:45:14 PM »
Right, to put this to bed. It 'looks' like their may have been two issues or not....we did a reboot and customer reported no difference. Then we queried a bit more and it looks like they did a mis-op and they were testing from one phone only (even though we had asked them to check from two or three) After the reboot other users were able to to make a conference (taking into account the obvious mis-op) but the main phone they were testing from only worked after a power off reboot (on a PoE switch).

So in the end we really don't know but its working fine now.


 

Sitemap 1 2 3 4 5 6 7 8 9 10