VOiP – SDump le contenu des logs du Cisco CP-8851 en tant que debug

Publié par Johannes RABEYRIN le

Nous allons étudier ensemble comment rendre un IP Phone Cisco plus bavard.

Pour cela, nous partirons du principe que vous gérez votre IP Phone avec un serveur Asterisk (XiVo, WaZo, …) avec un serveur TFTP et un fichier SEPxxxxx.cnf.xml.

Les appels fonctionnent correctement mais un problème demande de s’intéresser aux logs …. attention, ….c’est parti 🙂

Situation

Dans mon cas, j’effectue les manipulations sur un Cisco CP-8851 + KEM 8800, initialement en « Unified Communication Version » mais flashé en « SIP Version » :

Configuration SEPxxxx.cnf.xml

Commençons par vérifier que la configuration pour accéder en SSH sur le téléphone est disponible :

< sshuserid>cisco</ sshuserid>
< sshpassword>cisco</ sshpassword>

 

Configuration SSH

Connectez-vous sur le téléphone en SSH en utilisant le logiciel PUTTy et rentrez l’adresse IP du téléphone concerné.
Les premiers accès sont le cisco/cisco pour l’accès SSH, puis ensuite debug/debug pour l’utilisateur sur le CP-8851.

Le prompt en retour indique « debug> »

Effectuez les commandes ci-dessous :

settmask -p pwrman -t 0xFFFFF -b LOG_DEBUG

settmask -p dman -t 0xFFFFF -b LOG_DEBUG

settmask -p cdp -t 0xFFFFF -b LOG_DEBUG

Il ne reste plus qu’à éteindre l’IP Phone et le redémarrer à nouveau.
Attendez que le téléphone redémarre totalement, rencontre la probable erreur qui vous fait analyser le mode debug puis entrez la commande suivante :

sdump

Petit conseil : Copiez l’ensemble du contenu de SDump sur un éditeur de texte (NotePad++, SublimeText voire le bloc note Windows) pour analyser tranquillement.

 

Exemple de troubleshooting – problème d’alimentation du KEM :

6106 NOT Mar 02 08:07:01.758720 (442:487) CDP-cprCdpGetPort address: 10:BD:18:B0:F5:85  Phyport=0 appPort=0
6107 NOT Mar 02 08:07:01.759194 (442:487) CDP-cprCdpGetPort address: 10:BD:18:B0:F5:85  Phyport=0 appPort=0
6108 DEB Mar 02 08:07:04.522204 (436:438) DMAN-ITRACE-bluetooth_sendMsg
6109 NOT Mar 02 08:07:04.764725 (442:487) CDP-cprCdpGetPort address:  0:50:56:BA:65:3A  Phyport=0 appPort=0
6110 NOT Mar 02 08:07:04.765075 (442:487) CDP-cprCdpGetPort address:  0:50:56:BA:65:3A  Phyport=0 appPort=0
6111 NOT Mar 02 08:07:05.766454 (442:487) CDP-cprCdpGetPort address: 10:BD:18:B0:F7:2B  Phyport=0 appPort=0
6112 NOT Mar 02 08:07:05.767013 (442:487) CDP-cprCdpGetPort address: 10:BD:18:B0:F7:2B  Phyport=0 appPort=0
6113 DEB Mar 02 08:07:09.524881 (436:438) DMAN-ITRACE-bluetooth_sendMsg
6114 NOT Mar 02 08:07:09.765024 (442:487) CDP-cprCdpGetPort address:  0:50:56:BA:65:3A  Phyport=0 appPort=0
6115 NOT Mar 02 08:07:09.765372 (442:487) CDP-cprCdpGetPort address:  0:50:56:BA:65:3A  Phyport=0 appPort=0
6116 NOT Mar 02 08:07:12.673662 (378:392) PWRMAN-eventThrd(): select(): 1
6117 NOT Mar 02 08:07:12.673714 (378:392) PWRMAN-eventRcv(): fd 10
6118 NOT Mar 02 08:07:12.673742 (378:392) PWRMAN-eventRcv(): cmd: CMD_EVENT  event: 0x100  pid: 442  status: FAIL  procname: cdp
6119 NOT Mar 02 08:07:12.673759 (378:392) PWRMAN-eventPwrNeg():
6120 NOT Mar 02 08:07:12.673772 (378:392) PWRMAN-eventPwrNeg(): curReq.valid: 1  info->curPwr: 8500  curReq.newPwr: 11500
6121 WRN Mar 02 08:07:12.673785 (378:392) PWRMAN-eventPwrNeg(): power neg failed: TIMEOUT
6122 NOT Mar 02 08:07:12.673798 (378:392) PWRMAN-sendPwrReq():  cmd: 0x5  event: 0x400  status: 0x2  reqPwr: 3000  devID: 0x5a5afff0
6123 NOT Mar 02 08:07:12.673821 (378:392) PWRMAN-eventPwrNeg(): swtype: POE  pwrInfo.swtype: POE
6124 NOT Mar 02 08:07:12.673837 (378:392) PWRMAN-eventThrd(): waiting for socket activity
6125 DEB Mar 02 08:07:12.674013 (436:655) DMAN-sendMsgToPM(): PM  Response Rcvd
6126 NOT Mar 02 08:07:12.674070 (436:655) DMAN-sendMsgToPM()-10475: Freeing memory for pwrMsg 160 bytes
6127 DEB Mar 02 08:07:12.677904 (436:655) DMAN-isPowerAvailable(): Status = 0x600
6128 NOT Mar 02 08:07:12.679643 (436:655) DMAN-isPowerAvailable(): Response from PM: NO POWER
6129 NOT Mar 02 08:07:12.680300 (436:655) DMAN-lkemHandler(): Power Request for KEM Rejected.
6130 NOT Mar 02 08:07:12.680533 (436:655) DMAN-removeFromInactiveList(): Enter
6131 NOT Mar 02 08:07:12.680595 (436:655) DMAN-removeFromInactiveList(): GETDEVINFO_LOCK:: Locking inactivedev_mutex
6132 NOT Mar 02 08:07:12.680638 (436:655) DMAN-removeFromInactiveList(): DEV_LOCK::Got inactivedvev_mutex : 4080
6133 NOT Mar 02 08:07:12.680676 (436:655) DMAN-removeFromInactiveList(): GETDEVINFO_LOCK:: Unlocking inactivedev_mutex
6134 NOT Mar 02 08:07:12.680711 (436:655) DMAN-removeFromInactiveList(): DEV_LOCK::Released inactivedvev_mutex: 4104
6135 NOT Mar 02 08:07:12.680744 (436:655) DMAN-removeFromInactiveList(): Leave
6136 NOT Mar 02 08:07:12.680778 (436:655) DMAN-addToInactiveList(): Enter^H
6137 NOT Mar 02 08:07:12.680810 (436:655) DMAN-addToInactiveList(): GETDEVINFO_LOCK:: Locking inactivedev_mutex
6138 NOT Mar 02 08:07:12.680843 (436:655) DMAN-addToInactiveList(): DEV_LOCK::Got inactivedvev_mutex : 4058
6139 NOT Mar 02 08:07:12.680876 (436:655) DMAN-addToInactiveList(): Adding New device to inactive list
6140 NOT Mar 02 08:07:12.680907 (436:655) DMAN-addToInactiveList(): deviceID=0x5a5afff0, deviceStatus=6
6141 NOT Mar 02 08:07:12.680939 (436:655) DMAN-addToInactiveList(): GETDEVINFO_LOCK:: Unlocking inactivedev_mutex
6142 NOT Mar 02 08:07:12.680971 (436:655) DMAN-addToInactiveList(): DEV_LOCK::Released inactivedvev_mutex: 4067
6143 NOT Mar 02 08:07:12.681003 (436:655) DMAN-addToInactiveList(): Leave^H
6144 NOT Mar 02 08:07:12.681057 (436:655) DMAN-handleNewEvent(): Enter
6145 NOT Mar 02 08:07:12.681101 (436:655) DMAN-handleNewEvent()-5770: Allocating memory for usbMsg 148 bytes
6146 NOT Mar 02 08:07:12.681143 (436:655) DMAN-handleNewEvent(): Calling usb_callbackFunc
6147 DEB Mar 02 08:07:12.681179 (436:655) DMAN-handleNewEvent(): usbMsg->cmdInfo.deviceID = 0x5a5afff0
6148 NOT Mar 02 08:07:12.681213 (436:655) DMAN-callbackForClientComm():Enter
6149 DEB Mar 02 08:07:12.681246 (436:655) DMAN-callbackForClientComm(): client = 64, 0x40
6150 DEB Mar 02 08:07:12.681279 (436:655) DMAN-callbackForClientComm():ui_fd = 18
6151 DEB Mar 02 08:07:12.681310 (436:655) DMAN-callbackForClientComm():ui_fd = 18, event=0xb0004000, add on module=0
6152 DEB Mar 02 08:07:12.681344 (436:655) DMAN-callbackForClientComm():In DM_CLIENT_UI
6153 NOT Mar 02 08:07:12.681405 (731:788) JAVA-Calling handleDevManEvent
6154 DEB Mar 02 08:07:12.681616 (436:438) DMAN-CHANDLER_INFO::clientHandler:: select returned: 1
6155 DEB Mar 02 08:07:12.681644 (436:438) DMAN-CHANDLER_LOG::clientHandler:: New connection?? Trying accept 7
6156 DEB Mar 02 08:07:12.681669 (436:438) DMAN-CHANDLER_LOG::clientHandler:: New connection : 22
6157 DEB Mar 02 08:07:12.681684 (436:438) DMAN-CHANDLER_LOG::clientHandler:: Adding Info to Base
6158 DEB Mar 02 08:07:12.681696 (436:438) DMAN-In addtoInfoBase()
6159 DEB Mar 02 08:07:12.681706 (436:438) DMAN-Checking if entry is already present
6160 DEB Mar 02 08:07:12.681716 (436:438) DMAN-SLIST_LOG::In checkInfoBase()
6161 DEB Mar 02 08:07:12.681727 (436:438) DMAN-List is NOT empty so looking for duplicates
6162 NOT Mar 02 08:07:12.681738 (436:438) DMAN-SLIST_LOG::tmp->fd=20, data->fd=22
6163 NOT Mar 02 08:07:12.681750 (436:438) DMAN-SLIST_LOG::tmp->fd=19, data->fd=22
6164 NOT Mar 02 08:07:12.681762 (436:438) DMAN-SLIST_LOG::tmp->fd=18, data->fd=22
6165 NOT Mar 02 08:07:12.681773 (436:438) DMAN-SLIST_LOG::tmp->fd=7, data->fd=22
6166 NOT Mar 02 08:07:12.681784 (436:438) DMAN-SLIST_LOG::Entry is not found so adding it
6167 DEB Mar 02 08:07:12.681796 (436:438) DMAN-reutrning back from addttoInfoBase()
6168 DEB Mar 02 08:07:12.681808 (436:438) DMAN-CHANDLER_LOG::clientHandler:: Adding Info to Base: Successful
6169 DEB Mar 02 08:07:12.681821 (436:438) DMAN-CHANDLER_DEBUG::max_sock=22 cfd=22
6170 DEB Mar 02 08:07:12.681841 (436:438) DMAN-CHANDLER_INFO::clientHandler:: select returned: 1
6171 DEB Mar 02 08:07:12.681854 (436:438) DMAN-CHANDLER_DEBUG::Checking to see if any of the clients have sent any data
6172 DEB Mar 02 08:07:12.681867 (436:438) DMAN-CHANDLER_DEBUG::Reading Data from fd = 22
6173 DEB Mar 02 08:07:12.681878 (436:438) DMAN-ITRACE-::Enter
6174 NOT Mar 02 08:07:12.681889 (436:438) DMAN-rcvData()-394: Allocating memory for sockCmd 148 bytes
6175 DEB Mar 02 08:07:12.681902 (436:438) DMAN-Waiting for Data from client: fd = 22
6176 DEB Mar 02 08:07:12.681923 (436:438) DMAN-Got Data from Client fd = 22
6177 DEB Mar 02 08:07:12.681937 (436:438) DMAN-Got DM_CMD_GET_INFO command from client: fd = 22, subsystem = 0x20
6178 NOT Mar 02 08:07:12.681950 (436:438) DMAN-Malloc Here
6179 NOT Mar 02 08:07:12.681960 (436:438) DMAN-rcvData()-734: Allocating memory for usbMsg 148 bytes
6180 DEB Mar 02 08:07:12.682018 (436:438) DMAN-senddata(): Data sent successfully: 148 bytes
6181 DEB Mar 02 08:07:12.682036 (436:438) DMAN-senddata(): Data sent successfully: 12 bytes
6182 NOT Mar 02 08:07:12.682048 (436:438) DMAN-rcvData()-772: Allocating memory for tmp 12 bytes
6183 DEB Mar 02 08:07:12.682063 (436:438) DMAN-senddata(): Data sent successfully: 12 bytes
6184 NOT Mar 02 08:07:12.682076 (436:438) DMAN-rcvData()-791: Freeing tmp memory
6185 NOT Mar 02 08:07:12.682088 (436:438) DMAN-rcvData()-795: Freeing usbMsg memory
6186 NOT Mar 02 08:07:12.682101 (436:438) DMAN-rcvData()-798: Freeing sockCmd memory
6187 DEB Mar 02 08:07:12.682114 (436:438) DMAN-CHANDLER_DEBUG:: Returned from rcvData with sttus=12
6188 DEB Mar 02 08:07:12.682644 (436:438) DMAN-CHANDLER_INFO::clientHandler:: select returned: 1
6189 DEB Mar 02 08:07:12.682675 (436:438) DMAN-CHANDLER_DEBUG::Checking to see if any of the clients have sent any data
6190 DEB Mar 02 08:07:12.682688 (436:438) DMAN-CHANDLER_DEBUG::Reading Data from fd = 22
6191 DEB Mar 02 08:07:12.682700 (436:438) DMAN-ITRACE-::Enter
6192 NOT Mar 02 08:07:12.682711 (436:438) DMAN-rcvData()-394: Allocating memory for sockCmd 148 bytes
6193 DEB Mar 02 08:07:12.682725 (436:438) DMAN-Waiting for Data from client: fd = 22
6194 DEB Mar 02 08:07:12.682743 (436:438) DMAN-Got Data from Client fd = 22
6195 DEB Mar 02 08:07:12.682755 (436:438) DMAN-Got DM_CMD_GET_INFO command from client: fd = 22, subsystem = 0x10
6196 NOT Mar 02 08:07:12.682767 (436:438) DMAN-Malloc Here
6197 NOT Mar 02 08:07:12.682777 (436:438) DMAN-rcvData()-734: Allocating memory for usbMsg 148 bytes
6198 DEB Mar 02 08:07:12.682791 (436:438) DMAN-rcvData(): sockCmd->cmfInfo.data = 0x0
6199 DEB Mar 02 08:07:12.682806 (436:438) DMAN-ITRACE-linout_device_info
6200 DEB Mar 02 08:07:12.682818 (436:438) DMAN-linout_device_info(): Sending LineIn Info
6201 NOT Mar 02 08:07:12.682831 (436:438) DMAN-Send devInfo Successful
6202 DEB Mar 02 08:07:12.682841 (436:438) DMAN-Returning back from devInfo reqeust
6203 DEB Mar 02 08:07:12.682851 (436:438) DMAN-ITRACE-linout_device_info
6204 DEB Mar 02 08:07:12.682861 (436:438) DMAN-linout_device_info(): Sending LineOut Info
6205 NOT Mar 02 08:07:12.682873 (436:438) DMAN-Send devInfo Successful
6206 DEB Mar 02 08:07:12.683549 (436:438) DMAN-Returning back from devInfo reqeust
6207 DEB Mar 02 08:07:12.683577 (436:438) DMAN-ITRACE-linout_device_info
6208 DEB Mar 02 08:07:12.683591 (436:438) DMAN-End of accessories detected
6209 NOT Mar 02 08:07:12.683603 (436:438) DMAN-rcvData()-916: Allocating tmp memory from getdeviceInfo for 20 bytes
6210 NOT Mar 02 08:07:12.683627 (436:438) DMAN-Send devInfo Successful
6211 DEB Mar 02 08:07:12.683639 (436:438) DMAN-Returning back from devInfo reqeust
6212 NOT Mar 02 08:07:12.683650 (436:438) DMAN-rcvData()-991: Freeing tmp memory
6213 NOT Mar 02 08:07:12.683663 (436:438) DMAN-rcvData()-994: Freeing usbMsg memory
6214 NOT Mar 02 08:07:12.683675 (436:438) DMAN-rcvData()-996: Freeing sockCmd memory
6215 DEB Mar 02 08:07:12.683687 (436:438) DMAN-CHANDLER_DEBUG:: Returned from rcvData with status=20
6216 DEB Mar 02 08:07:12.683880 (436:438) DMAN-CHANDLER_INFO::clientHandler:: select returned: 1
6217 DEB Mar 02 08:07:12.683902 (436:438) DMAN-CHANDLER_DEBUG::Checking to see if any of the clients have sent any data
6218 DEB Mar 02 08:07:12.683915 (436:438) DMAN-CHANDLER_DEBUG::Reading Data from fd = 22
6219 DEB Mar 02 08:07:12.683926 (436:438) DMAN-ITRACE-::Enter
6220 NOT Mar 02 08:07:12.683937 (436:438) DMAN-rcvData()-394: Allocating memory for sockCmd 148 bytes
6221 DEB Mar 02 08:07:12.683951 (436:438) DMAN-Waiting for Data from client: fd = 22
6222 DEB Mar 02 08:07:12.683968 (436:438) DMAN-Got Data from Client fd = 22
6223 DEB Mar 02 08:07:12.683981 (436:438) DMAN-Got DM_CMD_GET_INFO command from client: fd = 22, subsystem = 0x1
6224 NOT Mar 02 08:07:12.683993 (436:438) DMAN-Malloc Here
6225 NOT Mar 02 08:07:12.684003 (436:438) DMAN-rcvData()-734: Allocating memory for usbMsg 148 bytes
6226 DEB Mar 02 08:07:12.684017 (436:438) DMAN-rcvData(): sockCmd->cmfInfo.data = 0x0
6227 NOT Mar 02 08:07:12.684032 (436:438) DMAN-usbapi_getDeviceInfo(): Enter
6228 DEB Mar 02 08:07:12.684043 (436:438) DMAN-usbapi_getDeviceInfo(): Calling devadd_head1
6229 NOT Mar 02 08:07:12.684054 (436:438) DMAN-GetActiveDevList(): GETDEVINFO_LOCK:: Locking activedev_mutex1 in multi-devices
6230 NOT Mar 02 08:07:12.684066 (436:438) DMAN-GetActiveDevList(): DEV_LOCK::Got activedvev_mutex1: 10793
6231 NOT Mar 02 08:07:12.684077 (436:438) DMAN-GetActiveDevList(): GETDEVINFO_LOCK:: Un-Locking activedev_mutex1 in multi-devices
6232 NOT Mar 02 08:07:12.684088 (436:438) DMAN-GetActiveDevList(): DEV_LOCK::Released activedvev_mutex1: 10898
6233 DEB Mar 02 08:07:12.684099 (436:438) DMAN-usbapi_getDeviceInfo(): Done devadd_head1
6234 DEB Mar 02 08:07:12.684109 (436:438) DMAN-usbapi_getDeviceInfo(): Calling devadd_head0
6235 NOT Mar 02 08:07:12.684120 (436:438) DMAN-GetActiveDevList(): GETDEVINFO_LOCK:: Locking activedev_mutex0 in multi-devices
6236 NOT Mar 02 08:07:12.684130 (436:438) DMAN-GetActiveDevList(): DEV_LOCK::Got activedvev_mutex0 : 10799
6237 NOT Mar 02 08:07:12.684141 (436:438) DMAN-GetActiveDevList(): GETDEVINFO_LOCK:: Un-Locking activedev_mutex0 in multi-devices
6238 NOT Mar 02 08:07:12.684152 (436:438) DMAN-GetActiveDevList(): DEV_LOCK::Released activedvev_mutex0 : 10904
6239 DEB Mar 02 08:07:12.684163 (436:438) DMAN-usbapi_getDeviceInfo(): Done devadd_head0
6240 DEB Mar 02 08:07:12.684173 (436:438) DMAN-usbapi_getDeviceInfo(): Moving onto InactiveDevice List
6241 NOT Mar 02 08:07:12.684184 (436:438) DMAN-GetInActiveDevList(): Enter
6242 NOT Mar 02 08:07:12.684194 (436:438) DMAN-GetInActiveDevList(): GETDEVINFO_LOCK:: Locking Inactivedev_mutex in multi-devices
6243 NOT Mar 02 08:07:12.684205 (436:438) DMAN-GetInActiveDevList(): DEV_LOCK::Got inactivedvev_mutex : 10929
6244 NOT Mar 02 08:07:12.684216 (436:438) DMAN-GetInActiveDevList(): GETDEVINFO_LOG::devinactive_head is not empty
6245 NOT Mar 02 08:07:12.684227 (436:438) DMAN-GetInActiveDevList()-10959: Allocating memory for dinfo 2896 bytes
6246 DEB Mar 02 08:07:12.684274 (436:438) DMAN-GetInActiveDevList(): GETDEVINFO_LOG::Returning pointer : 0xb6500888
6247 NOT Mar 02 08:07:12.684295 (436:438) DMAN-GetInActiveDevList(): Leave
6248 DEB Mar 02 08:07:12.684307 (436:438) DMAN-usbapi_getDeviceInfo(): Sending device Info from devadd_head0
6249 NOT Mar 02 08:07:12.684318 (436:438) DMAN-cpUSBInternalDevInfoToDMDevInfo(): Enter
6250 NOT Mar 02 08:07:12.684331 (436:438) DMAN-cpUSBInternalDevInfoToDMDevInfo(): parent_devid = 0x0, child_devid=0x0, appfd=0x0
6251 DEB Mar 02 08:07:12.684343 (436:438) DMAN-cpUSBInternalDevInfoToDMDevInfo(): PDINFO--> devid = 0x5a5afff0, productid=0xc, vendorfd=0x5a6
6252 DEB Mar 02 08:07:12.684355 (436:438) DMAN-cpUSBInternalDevInfoToDMDevInfo(): TMPINFO--> devid = 0x5a5afff0, productid=0xc, vendorfd=0x5a6
6253 NOT Mar 02 08:07:12.684367 (436:438) DMAN-cpUSBInternalDevInfoToDMDevInfo(): Leave
6254 NOT Mar 02 08:07:12.684377 (436:438) DMAN-usbapi_getDeviceInfo()-11177: Freeing memory for dinfo 2896 bytes
6255 NOT Mar 02 08:07:12.684395 (436:438) DMAN-Send devInfo Successful
6256 DEB Mar 02 08:07:12.684407 (436:438) DMAN-Returning back from devInfo reqeust
6257 NOT Mar 02 08:07:12.684418 (436:438) DMAN-usbapi_getDeviceInfo(): Enter
6258 DEB Mar 02 08:07:12.684428 (436:438) DMAN-usbapi_getDeviceInfo(): Moving onto InactiveDevice List
6259 NOT Mar 02 08:07:12.684439 (436:438) DMAN-GetInActiveDevList(): Enter
6260 NOT Mar 02 08:07:12.684449 (436:438) DMAN-GetInActiveDevList(): GETDEVINFO_LOG::devinactive_head is not empty
6261 DEB Mar 02 08:07:12.684460 (436:438) DMAN-GetInActiveDevList(): lindex = 0
6262 NOT Mar 02 08:07:12.684470 (436:438) DMAN-GetInActiveDevList(): GETDEVINFO_LOCK:: Un-Locking inactivedev_mutex in multi-devices
6263 NOT Mar 02 08:07:12.684481 (436:438) DMAN-GetInActiveDevList(): DEV_LOCK::Released inactivedvev_mutex: 11026
6264 NOT Mar 02 08:07:12.684492 (436:438) DMAN-GetInActiveDevList(): Leave
6265 NOT Mar 02 08:07:12.684502 (436:438) DMAN-usbapi_getDeviceInfo(): Leave
6266 DEB Mar 02 08:07:12.684513 (436:438) DMAN-End of accessories detected
6267 NOT Mar 02 08:07:12.684524 (436:438) DMAN-rcvData()-916: Allocating tmp memory from getdeviceInfo for 1060 bytes
6268 NOT Mar 02 08:07:12.684542 (436:438) DMAN-Send devInfo Successful
6269 DEB Mar 02 08:07:12.684554 (436:438) DMAN-Returning back from devInfo reqeust
6270 NOT Mar 02 08:07:12.684564 (436:438) DMAN-rcvData()-991: Freeing tmp memory
6271 NOT Mar 02 08:07:12.684576 (436:438) DMAN-rcvData()-994: Freeing usbMsg memory
6272 NOT Mar 02 08:07:12.684588 (436:438) DMAN-rcvData()-996: Freeing sockCmd memory
6273 DEB Mar 02 08:07:12.684600 (436:438) DMAN-CHANDLER_DEBUG:: Returned from cvData with status=1060
6274 DEB Mar 02 08:07:12.685478 (436:438) DMAN-CHANDLER_INFO::clientHandler:: select returned: 1
6275 DEB Mar 02 08:07:12.685512 (436:438) DMAN-CHANDLER_DEBUG::Checking to see if any of the clients have sent any data
6276 DEB Mar 02 08:07:12.685526 (436:438) DMAN-CHANDLER_DEBUG::Reading Data from fd = 22
6277 DEB Mar 02 08:07:12.685538 (436:438) DMAN-ITRACE-::Enter
6278 NOT Mar 02 08:07:12.685550 (436:438) DMAN-rcvData()-394: Allocating memory for sockCmd 148 bytes
6279 DEB Mar 02 08:07:12.685565 (436:438) DMAN-Waiting for Data from client: fd = 22
6280 DEB Mar 02 08:07:12.685674 (436:438) DMAN-Got Data from Client fd = 22
6281 DEB Mar 02 08:07:12.685694 (436:438) DMAN-Got DM_CMD_GET_INFO command from client: fd = 22, subsystem = 0x4
6282 NOT Mar 02 08:07:12.685707 (436:438) DMAN-Malloc Here
6283 NOT Mar 02 08:07:12.685717 (436:438) DMAN-rcvData()-734: Allocating memory for usbMsg 148 bytes
6284 DEB Mar 02 08:07:12.685732 (436:438) DMAN-rcvData(): sockCmd->cmfInfo.data = 0x0
6285 DEB Mar 02 08:07:12.685820 (436:438) DMAN-ITRACE-bluetooth_device_info
6286 DEB Mar 02 08:07:12.685839 (436:438) DMAN-End of accessories detected
6287 NOT Mar 02 08:07:12.685851 (436:438) DMAN-rcvData()-916: Allocating tmp memory from getdeviceInfo for 164 bytes
6288 NOT Mar 02 08:07:12.688004 (731:830) JAVA-display MQThread|EWProperty:getDurationFromNow - PSP is disabled
6289 NOT Mar 02 08:07:12.688197 (731:830) JAVA-cprLedSet: Set led data, key_index = 280, key_led_status = 1, key_led_color = 0
6290 NOT Mar 02 08:07:12.688527 (363:431) EWCLIENT-event_rcv(): LSOCK_CMD_EVENT: EV_CHANGE_LEVEL: 10
6291 NOT Mar 02 08:07:12.688693 (363:431) EWCLIENT-event_rcv(): LSOCK_CMD_EVENT: EV_GET_LEVEL proc:
6292 NOT Mar 02 08:07:12.688719 (363:431) EWCLIENT-send_level_reply():  cmd: 0x5  event: 0xc00  status: 0x0  error: 0x0  level: 10  fd: 15
6293 INF Mar 02 08:07:12.689090 (731:905) JAVA-[FIlE: LKEMManager.c FUNC: processEventsFromLJTLST LINE: 2129]:
6294 INF Mar 02 08:07:12.689123 (731:905) JAVA-Process the Events from LJT/LST.
6295 INF Mar 02 08:07:12.689148 (731:905) JAVA-[FIlE: LKEMManager.c FUNC: processEventsFromLJTLST LINE: 2146]:
6296 INF Mar 02 08:07:12.689162 (731:905) JAVA-The command types is SETPOWERLEVEL
6297 NOT Mar 02 08:07:12.698133 (436:438) DMAN-Send devInfo Successful
6298 DEB Mar 02 08:07:12.698192 (436:438) DMAN-Returning back from devInfo reqeust
6299 NOT Mar 02 08:07:12.698208 (436:438) DMAN-rcvData()-991: Freeing tmp memory
6300 NOT Mar 02 08:07:12.698223 (436:438) DMAN-rcvData()-994: Freeing usbMsg memory
6301 NOT Mar 02 08:07:12.698235 (436:438) DMAN-rcvData()-996: Freeing sockCmd memory
6302 DEB Mar 02 08:07:12.698248 (436:438) DMAN-CHANDLER_DEBUG:: Returned from rcvData with status=164
6303 DEB Mar 02 08:07:12.698277 (436:438) DMAN-CHANDLER_INFO::clientHandler:: select returned: 1
6304 DEB Mar 02 08:07:12.698291 (436:438) DMAN-CHANDLER_DEBUG::Checking to see if any of the clients have sent any data
6305 DEB Mar 02 08:07:12.698302 (436:438) DMAN-CHANDLER_DEBUG::Reading Data from fd = 22
6306 DEB Mar 02 08:07:12.698316 (436:438) DMAN-ITRACE-::Enter
6307 NOT Mar 02 08:07:12.698327 (436:438) DMAN-rcvData()-394: Allocating memory for sockCmd 148 bytes
6308 DEB Mar 02 08:07:12.698343 (436:438) DMAN-Waiting for Data from client: fd = 22
6309 DEB Mar 02 08:07:12.698359 (436:438) DMAN-Client closed connection
6310 NOT Mar 02 08:07:12.698371 (436:438) DMAN-rcvData()-423: Freeing sockCmd memory
6311 DEB Mar 02 08:07:12.698383 (436:438) DMAN-CHANDLER_DEBUG:: Returned from rcvData with status=129
6312 DEB Mar 02 08:07:12.698394 (436:438) DMAN-CHANDLER_DEBUG:: Client Closed Socket. Closing Socket on Server for fd fd = 22
6313 DEB Mar 02 08:07:12.698442 (436:438) DMAN-CHANDLER_INFO:: Removing client with fd = 22 from the database
6314 NOT Mar 02 08:07:12.698458 (436:438) DMAN-clientHandler()-265: Freeing tmp clientEntry memory
6315 DEB Mar 02 08:07:12.698774 (731:881) JAVA-Cisco/Accessories MQThread|Appframe:ALERT StartNotification - conect = Le téléphone ne peut pas alimenter cet accessoire.
6316 NOT Mar 02 08:07:12.699770 (436:655) DMAN-callbackForClientComm():Send msg to UI Successful
6317 NOT Mar 02 08:07:12.701889 (436:655) DMAN-callbackForClientComm():LSOCK_LOG::sent devInfo size sent = 148 actual = 148
6318 NOT Mar 02 08:07:12.702065 (436:655) DMAN-callbackForClientComm():Leave
6319 NOT Mar 02 08:07:12.702122 (436:655) DMAN-handleNewEvent()-5859: Freeing usbMsg memory for 148 bytes
6320 NOT Mar 02 08:07:12.702165 (436:655) DMAN-handleNewEvent(): Leave
6321 NOT Mar 02 08:07:12.890410 (378:392) PWRMAN-eventThrd(): select(): 1
6322 NOT Mar 02 08:07:12.890458 (378:392) PWRMAN-eventRcv(): fd 13
6323 NOT Mar 02 08:07:12.890486 (378:392) PWRMAN-eventRcv(): cmd: CMD_EVENT  event: 0x600  pid: 731  status: NONE  procname: sendPowerModeCmd
6324 NOT Mar 02 08:07:12.890502 (378:392) PWRMAN-eventRcv(): LSOCK_CMD_EVENT: PM_EVENT_SETMODE
6325 NOT Mar 02 08:07:12.890516 (378:392) PWRMAN-setMode(): NORMAL
6326 NOT Mar 02 08:07:12.890530 (378:392) PWRMAN-sendEvent():  cmd: 0x5  event: 0x600  status: 0x1  error: 0x0  fd: 13
6327 NOT Mar 02 08:07:12.890553 (378:392) PWRMAN-sendNewMode(): NORMAL
6328 NOT Mar 02 08:07:12.890567 (378:392) PWRMAN-sendNewMode():  cmd: 0x5  event: 0x600  status: 0x0  reqPwr: 0  devID: 0x0
6329 NOT Mar 02 08:07:12.890589 (378:392) PWRMAN-eventThrd(): waiting for socket activity
6330 NOT Mar 02 08:07:12.891191 (731:788) JAVA-Calling handlePowerManEvent
6331 NOT Mar 02 08:07:12.891249 (731:788) JAVA-Calling handlePowerManEvent
6332 DEB Mar 02 08:07:12.891330 (436:439) DMAN-udevFunc(): Select returned: 1.
6333 DEB Mar 02 08:07:12.891371 (436:439) DMAN-getDeviceInfo():

[X] Résultat :
6119 NOT Mar 02 08:07:12.673759 (378:392) PWRMAN-eventPwrNeg():
6120 NOT Mar 02 08:07:12.673772 (378:392) PWRMAN-eventPwrNeg(): curReq.valid: 1 info->curPwr: 8500 curReq.newPwr: 11500
6121 WRN Mar 02 08:07:12.673785 (378:392) PWRMAN-eventPwrNeg(): power neg failed: TIMEOUT
6128 NOT Mar 02 08:07:12.679643 (436:655) DMAN-isPowerAvailable(): Response from PM: NO POWER
6129 NOT Mar 02 08:07:12.680300 (436:655) DMAN-lkemHandler(): Power Request for KEM Rejected.

J’ai donc un problème d’alimentation lors de l’injection POE, pour alimenter mon duo CP-8851+KEM 8800.
Merci NetGear 😉

Catégories : VoIP

Johannes RABEYRIN

Ingénieur Systèmes et Réseaux à Sonceboz. Je vous partage mon IT (tests, connaissances, problèmes et solutions... si possible) via mon site, LinkedIn et (un peu de) tweets !

0 commentaire

Laisser un commentaire

Votre adresse de messagerie ne sera pas publiée. Les champs obligatoires sont indiqués avec *