Callback when the remote has Aborted the stream

Callback when the locally-initiated Abort stream has successfully completed

Callback when a bearer has been created for a session in the stream. The session the bearer is for can be examined from the socket address given in the callback Each socket created in this way is created on the client's socket server session, and responsibility for socket closure is ceded to the client. TAvdtpSockAddr

Callback when locally-initiated (re)configuration procedure successfully completes

Callback when remotely initiated configuration of local SEP is completed The client can still error, as the local side may have expected to see more capabilities proposed

Callback when each capability is being proposed by the peer during configuration Each capability can be refused, but doing so completes whole configure operation

Callback when remote is beginning to configure a local SEP This cannot be rejected by the client at this stage - it must examine each capability proposed by the GAVDP peer.

Callback when a signalling channel has successfully been created Note this can be called by GAVDP without the client having called RGavdp::Connect The reason being that as soon as a GAVDP session is created AVDTP begins listening Therefore a remote device can connect to us. The GAVDP client can check the address to confirm if the device is that they originally Connect()ed

Callback when a GAVDP error occurs TAvdtpConfigRejectPckgBuf as an example of what may be passed back

Callback when the remote end has Released a stream The user-plane bearers will subsequently error with KErrDisconnected.

Callback when a capability from a remote SEP has been retrieved The client takes owenership of the capability given TAvdtpServiceCapability

Callback when remote SEP has no more capabilities to be discovered

Callback when a remote SEP has been discovered TAvdtpSEPInfo

Callback when no more SEPs have been discovered on the remote device. This may be called without GAVDP_SEPDiscovered being called if the remote has no SEPs (such a remote would be in contravention of the specification however)

Callback when the locally-initiated Security Control message successfully completed

Callback when the remote is sending Security Control information

Callback when the remote is trying to Start a stream The allowable error codes are defined in the Bluetooth SIG AVDTP specification and profiles design to operate above that layer, such as GAVDP. However those "local" error code values should be offset by the Symbian KErrAvdtpSignallingErrorBase (-18045) to convert to system-wide, absolute error codes.

For example; the error code for NOT_SUPPORTED_COMMAND = 25 Therefore, the system code would be (-18045)-25 = -18070

Callback when the locally-initiated Start stream has successfully completed

Callback when the remote is trying to Suspend a stream The allowable error codes are defined in the Bluetooth SIG AVDTP specification and profiles design to operate above that layer, such as GAVDP. However those "local" error code values should be offset by the Symbian KErrAvdtpSignallingErrorBase (-18045) to convert to system-wide, absolute error codes.

For example; the error code for NOT_SUPPORTED_COMMAND = 25 Therefore, the system code would be (-18045)-25 = -18070

Callback when the locally-initiated Suspend stream has successfully completed