The following example shows typical output generated by ctasip when the program places an inbound call:
Event: NCCEVN_SEIZURE_DETECTED
Event: NCCEVN_INCOMING_CALL
TO : <sip:4801@sipserver.dialogic.com>
FROM: "SIPPhone"<sip:4800@sipserver.dialogic.com>
cc
ok
Event: NCCEVN_ACCEPTING_CALL
ac
ok
Event: NCCEVN_ANSWERING_CALL
Event: NCCEVN_CALL_CONNECTED
MSPP : Created: PM endpont, slot 0 board 0
MSPP : Created: RTP endpont, 10.122.20.20:8004 -> 10.122.20.22:5004
MSPP : Created: channel
MSPP : Channel: connected and enabled
Event: NCCEVN_CALL_DISCONNECTED
MSPP : Channel: disabled and disconnected
MSPP : Destroyed: RTP endpoint
MSPP : Destroyed: PM endpoint
MSPP : Destroyed: channel
rc
ok
Event: NCCEVN_CALL_RELEASED
The following table describes the sequence of events and commands:
Sequence |
Event or command |
Description |
1 |
NCCEVN_SEIZURE_DETECTED |
Indicates a new call has arrived as the result of an incoming INVITE message. |
2 |
NCCEVN_INCOMING_CALL |
Carries the called (To) and calling (From) information along with the SDP information. |
3 |
cc |
Sends a 180 Ringing response to the remote SIP phone. The event NCCEVN_ACCEPTING_CALL is generated by the SIP stack indicating that the response was successfully sent. |
4 |
ac |
Answers the call by sending a 200 OK response to the initial INVITE. |
5 |
MSPP events |
Result from setting up an MSPP endpoint. |
6 |
NCCEVN_CALL_DISCONNECTED |
Indicates that the remote end disconnected. The SIP stack automatically acknowledges this call. |
7 |
rc |
Calls nccReleaseCall to free up the SIP context. |