The cause codes can be confusing. In this case we see that the cause code is 0x10, which is decimal 16. These translate to "normal call clearing".
Mar 20 20:31:43.786: ccGetDialpeerTag (callID=0x4118)
Mar 20 20:31:43.786: ssaIgnore cid(16665), st(SSA_CS_CALL_SETTING)oldst(1), ev(21)
Mar 20 20:31:47.626: cc_api_call_disconnected(vdbPtr=0x623993C8, callID=0x4118, cause=0x10)
Mar 20 20:31:47.626: sess_appl: ev(11=CC_EV_CALL_DISCONNECTED), cid(16664), disp (0)
We see that after a 4 second delay we receive cc_api_call_disconnected. This tells us that it was the remote side that disconnected the call (cc_api_xxx messages tell us about the VoIP leg of the call).
If we had seen ccCallDisconnect first, that would have told us the disconnect was initiated by the POTS side.
It appears in this case that it is the remote PBX that is disconnecting the call.
Question: Have the phone connected and can ring out-but no sound coming from the handset - analog home phone - phone makes connection and pick up at the other end is ok. Can you help?
Question: Have the phone connected and can ring out-but no sound coming from the handset - analog home phone - phone makes connection and pick up at the other end is ok. Can you help?Answer
iPXE boot in ASR9K
This document applies to NCS5500 and ASR9000 routers and has been verified as such.
traditional ECMP or equal cost multipath loadbalances traffic over a number of available paths towards a destination. When one path fails, the traffic gets r...