- Home
- Services & Support
- Downloads
- Helpweb
- Dialogic API information
- Find a Dialogic API
- DM3 & JCT Media Boards
- Host Media Processing (HMP)
- Global Call API
- Brooktrout Fax
- IP Media Server
- CSP / MSP / IMG
- DMG-series Media Gateways
- Signaling products
- Global Call API
- Multimedia Platform for ATCA
- Diva Media Boards
- Diva SDK
- Diva Client
- Eiconcards (X.25)
- Other products
- Online Training
- Manuals
- Contact
Dialogic Support Helpweb
Dialogic® Diva® SDK
Making GSM data calls with the Diva SDK
The calltype GSM in the Diva SDK sets the B channel to GSM data (V.110) but it does not automatically set the bearer capabilities.Therefore, when you try and make an outgoing data call (using the Simple Data Transfer sample in the SDK, for example), you will get disconnected - DisconnectReason = 12 which translates to "DivaDRUnspecifiedError".
The reason that we do not set the bearer capabilities is that several switches do not like this and do not pass the call.
Therefore, customers should modify the sample and set the bearer capabilities. The bearer capabilities are set by the property DivaCPT_BearerCapabilities. The coding is done first byte length field then the coding. For 9600 it should be (values as hex):
0x04 0x88 0x90 0x21 0x48So, instead of using DivaConnect, the typical sequence in the application would be:
DivaCreateCall DivaSetCallProperties (DivaCPT_CallType = DivaCallTypeGSM) DivaSetCallProperties (DivaCPT_LineDevice = LINEDEV_ALL) DivaSetCallProperties (DivaCPT_BearerCapabilities (length=0x04 data=0x88 0x90 0x21 0x48))NOTE: A customer in Denmark reported that in his case, he had to set the string to be
0x06 0x88 0x90 0x21 0x48 0x46 0xBB


