iPod IWIP3G User Guide - Page 41

CALL 00:1f:00:bc:73:99 19 A2DP

Page 41 highlights

PAIR If the PAIR event is enabled by using "SET CONTROL CONFIG", it will be displayed during the call if paring has to be done. CLOCK If piconet clock event is enabled, CLOCK event will be displayed. AUTH IF interactive pairing mode is enabled and no paring exists, AUTH event will be displayed. 5.8.2 Examples Creating a successful connection to 00:07:80:80:52:27 using Serial Port Profile. (UUID16 SPP = 1101) CALL 00:07:80:80:52:27 1101 RFCOMM CALL 0 CONNECT 0 RFCOMM 1 Creating a successful connection to 00:07:80:80:52:27 using RFCOMM channel 1. CALL 00:07:80:80:52:27 1 RFCOMM CALL 0 CONNECT 0 RFCOMM 1 Unsuccessful SPP connection attempt to 00:07:80:80:52:26. CALL 00:07:80:80:52:26 1101 RFCOMM CALL 0 NO CARRIER 0 ERROR 406 RFC_CONNECTION_FAILED Creating a successful connection to 00:07:80:80:52:27 with MTU 600. CALL 00:07:80:80:52:27 1101 RFCOMM MTU 600 CALL 0 CONNECT 0 RFCOMM 1 Creating a successful A2DP connection CALL 00:1f:00:bc:73:99 19 A2DP CALL 0 CONNECT 0 A2DP 25 CONNECT 1 A2DP 25 Creating a successful AVRCP connection CALL 00:1f:00:bc:73:99 17 A2DP CALL 0 CONNECT 0 A2DP 23 Creating a successful HID connection CALL 00:1f:00:bc:73:99 11 HID CONNECT 0 HID 17 CONNECT 0 HID 19 41

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211

41
PAIR
If the
PAIR
event is enabled by using “
SET CONTROL CONFIG
”, it will
be displayed during the call if paring has to be done.
CLOCK
If piconet clock event is enabled,
CLOCK
event will be displayed.
AUTH
IF interactive pairing mode is enabled and no paring exists,
AUTH
event
will be displayed.
5.8.2
Examples
Creating a successful connection to 00:07:80:80:52:27
using Serial Port Profile.
(UUID16 SPP = 1101)
CALL 00:07:80:80:52:27 1101 RFCOMM
CALL 0
CONNECT 0 RFCOMM 1
Creating a successful connection to 00:07:80:80:52:27 using RFCOMM channel 1.
CALL 00:07:80:80:52:27 1 RFCOMM
CALL 0
CONNECT 0 RFCOMM 1
Unsuccessful SPP connection attempt to 00:07:80:80:52:26.
CALL 00:07:80:80:52:26 1101 RFCOMM
CALL 0
NO CARRIER 0 ERROR 406 RFC_CONNECTION_FAILED
Creating a successful connection to 00:07:80:80:52:27
with MTU 600.
CALL 00:07:80:80:52:27 1101 RFCOMM MTU 600
CALL 0
CONNECT 0 RFCOMM 1
Creating a successful A2DP connection
CALL 00:1f:00:bc:73:99 19 A2DP
CALL 0
CONNECT 0 A2DP 25
CONNECT 1 A2DP 25
Creating a successful AVRCP connection
CALL 00:1f:00:bc:73:99 17 A2DP
CALL 0
CONNECT 0 A2DP 23
Creating a successful HID connection
CALL 00:1f:00:bc:73:99 11 HID
CONNECT 0 HID 17
CONNECT 0 HID 19