sending sms problem on Moto-Razr V3c | developer.brewmp.com sending sms problem on Moto-Razr V3c | developer.brewmp.com

Developer

sending sms problem on Moto-Razr V3c

Forums:

Hi all,

I m facing problem in sending SMS from Moto-Razr V3c...but it works fine on non VZW flavour of Razr....I read somewhere that send SMS isnt supported on Moto-Razr V3c...is it true...if it is...then whts the alternative to it??

thanks in adv...hoping for a quick reply...
D.Srinivas

The SMS client on the V3C is a BREW app, so you can definitely send SMS messages through BREW.
-Erik

The SMS client on the V3C is a BREW app, so you can definitely send SMS messages through BREW.
-Erik

Yes, SMS is definitely supported on the v3c. What problem are you experiencing?

Yes, SMS is definitely supported on the v3c. What problem are you experiencing?

hi mohlendo...
the problem im facing on razr V3c is tht the ITAPI_SendSMS is returning as unsupported...this is listed in the device datasheet...OEM exceptions too...so as a work around...i tried to u the ISMS_SendMsg....in which the problem im facing is the callback pointer i've set to notify after SMS is sent is never fired....can you plz help me out on this...
thnks
D.Srinivas

hi mohlendo...
the problem im facing on razr V3c is tht the ITAPI_SendSMS is returning as unsupported...this is listed in the device datasheet...OEM exceptions too...so as a work around...i tried to u the ISMS_SendMsg....in which the problem im facing is the callback pointer i've set to notify after SMS is sent is never fired....can you plz help me out on this...
thnks
D.Srinivas

Is there a synchronous failure?

Is there a synchronous failure?

hi...mohlendo
my problem is acktually this...
ISMS - Can not send SMS messages with encoding set to UNICODE (over the air).
ITAPI_SendSMS - ITAPI_SendSMS() does not work correctly since over the air encoding type is set to UNICODE. Use ISMS() APIs to send MO-SMS..
this is what Moto-Razr V3c says in the Known Issues sections....so im really confused about what to do ...since i have to port this application on Moto-Razr V3c and it requires sending SMS from device....any advice will be of great help... :)
thanks..
Srinivas

hi...mohlendo
my problem is acktually this...
ISMS - Can not send SMS messages with encoding set to UNICODE (over the air).
ITAPI_SendSMS - ITAPI_SendSMS() does not work correctly since over the air encoding type is set to UNICODE. Use ISMS() APIs to send MO-SMS..
this is what Moto-Razr V3c says in the Known Issues sections....so im really confused about what to do ...since i have to port this application on Moto-Razr V3c and it requires sending SMS from device....any advice will be of great help... :)
thanks..
Srinivas

Why can't you send the SMS? ISMS works on this device. What is the exact failure you're seeing?

Why can't you send the SMS? ISMS works on this device. What is the exact failure you're seeing?

hi mohlendo,
thnks for replying with tht gud news....well im trying with ITAPI_SendSMS....i will work with ISMS n then bug u if i have problem with it....thnks for bearing with tme... :)
thnks
Srinivas

hi mohlendo,
thnks for replying with tht gud news....well im trying with ITAPI_SendSMS....i will work with ISMS n then bug u if i have problem with it....thnks for bearing with tme... :)
thnks
Srinivas

hi mohlendo,
uff..its fixed...thnks a lot..used the ISMS api..then it worked...but the ITAPI_SendSMS..doesnt work on the razr...btw whts the difference between the both i.e ITAPI_SendSMS and ISMS_SendMsg...i mean r they different in their internal working??
thnks in adv.
Srinivas

hi mohlendo,
uff..its fixed...thnks a lot..used the ISMS api..then it worked...but the ITAPI_SendSMS..doesnt work on the razr...btw whts the difference between the both i.e ITAPI_SendSMS and ISMS_SendMsg...i mean r they different in their internal working??
thnks in adv.
Srinivas

Hi!
I am having severe troubles with Motorola V3C. The same application works without any trouble on other devices.
First I tried to use ITAPI_SendSMS() and recieved 0x400005 on callback (the same works fine on other devices). Then, I tried to use ISMS_SendMsg() and recieved 0x200001 in dwSMSSendResult (last parameter passed to ISMS_SendMsg).
I am really out of clues.
Here's the code:
SMSMsgOpt sOpts[2];
int res;
// Configure our options buffer. Options will be added
// one at a time
sOpts[1].nId = MSGOPT_END;
sOpts[1].pVal = NULL;
// We need to instruct the ISMSMessage to copy options that
// are passed
sOpts[0].nId = MSGOPT_COPYOPTS;
sOpts[0].pVal = (void *)TRUE;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( "Failed on ISMSMSG_AddOpt( MSGOPT_COPYOPTS=TRUE )" );
return res;
}
// priority
sOpts[0].nId = MSGOPT_PRIORITY;
sOpts[0].pVal = (void *)AEESMS_PRIORITY_NORMAL;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( "Failed on ISMSMSG_AddOpt( MSGOPT_PRIORITY=AEESMS_PRIORITY_NORMAL )" );
return res;
}
// Set the destination address on our outbound sms message
sOpts[0].nId = MSGOPT_TO_DEVICE_SZ;
sOpts[0].pVal = (void *)m_szRecipient;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( "Failed on ISMSMSG_AddOpt( MSGOPT_TO_DEVICE_SZ=\"%s\"" )"", (char*)m_szRecipient );
return res;
}
TAPIStatus sStatus;
res = ITAPI_GetStatus( m_pITAPI, &sStatus );
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ITAPI_GetStatus()"" );
return res;
}
sOpts[0].nId = MSGOPT_FROM_DEVICE_SZ;
sOpts[0].pVal = (void *)&sStatus.szMobileID[5];
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_FROM_DEVICE_SZ=\""%s\"" )"", &sStatus.szMobileID[5] );
return res;
}
sOpts[0].nId = MSGOPT_MOSMS_ENCODING;
sOpts[0].pVal = (void *)AEE_ENC_ASCII;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_MOSMS_ENCODING=AEE_ENC_ASCII )"" );
return res;
}
sOpts[0].nId = MSGOPT_PAYLOAD_SZ;
sOpts[0].pVal = (void *)m_szMessage;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_PAYLOAD_SZ=\""%s\"" )"", m_szMessage );
return res;
}
sOpts[0].nId = MSGOPT_PAYLOAD_ENCODING;
sOpts[0].pVal = (void *)AEE_ENC_ISOLATIN1;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_PAYLOAD_ENCODING=AEE_ENC_ISOLATIN1 )"" );
return res;
}
CALLBACK_Init(
&m_cbSendMessage,
&CSMSSender::s_OnSMSSend,
this
);
ISMS_SendMsg(
m_pISMS,
m_pISMSMsg,
&m_cbSendMessage,
&m_dwSMSSendResult
);
return(SUCCESS);"

Hi!
I am having severe troubles with Motorola V3C. The same application works without any trouble on other devices.
First I tried to use ITAPI_SendSMS() and recieved 0x400005 on callback (the same works fine on other devices). Then, I tried to use ISMS_SendMsg() and recieved 0x200001 in dwSMSSendResult (last parameter passed to ISMS_SendMsg).
I am really out of clues.
Here's the code:
SMSMsgOpt sOpts[2];
int res;
// Configure our options buffer. Options will be added
// one at a time
sOpts[1].nId = MSGOPT_END;
sOpts[1].pVal = NULL;
// We need to instruct the ISMSMessage to copy options that
// are passed
sOpts[0].nId = MSGOPT_COPYOPTS;
sOpts[0].pVal = (void *)TRUE;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( "Failed on ISMSMSG_AddOpt( MSGOPT_COPYOPTS=TRUE )" );
return res;
}
// priority
sOpts[0].nId = MSGOPT_PRIORITY;
sOpts[0].pVal = (void *)AEESMS_PRIORITY_NORMAL;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( "Failed on ISMSMSG_AddOpt( MSGOPT_PRIORITY=AEESMS_PRIORITY_NORMAL )" );
return res;
}
// Set the destination address on our outbound sms message
sOpts[0].nId = MSGOPT_TO_DEVICE_SZ;
sOpts[0].pVal = (void *)m_szRecipient;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( "Failed on ISMSMSG_AddOpt( MSGOPT_TO_DEVICE_SZ=\"%s\"" )"", (char*)m_szRecipient );
return res;
}
TAPIStatus sStatus;
res = ITAPI_GetStatus( m_pITAPI, &sStatus );
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ITAPI_GetStatus()"" );
return res;
}
sOpts[0].nId = MSGOPT_FROM_DEVICE_SZ;
sOpts[0].pVal = (void *)&sStatus.szMobileID[5];
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_FROM_DEVICE_SZ=\""%s\"" )"", &sStatus.szMobileID[5] );
return res;
}
sOpts[0].nId = MSGOPT_MOSMS_ENCODING;
sOpts[0].pVal = (void *)AEE_ENC_ASCII;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_MOSMS_ENCODING=AEE_ENC_ASCII )"" );
return res;
}
sOpts[0].nId = MSGOPT_PAYLOAD_SZ;
sOpts[0].pVal = (void *)m_szMessage;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_PAYLOAD_SZ=\""%s\"" )"", m_szMessage );
return res;
}
sOpts[0].nId = MSGOPT_PAYLOAD_ENCODING;
sOpts[0].pVal = (void *)AEE_ENC_ISOLATIN1;
res = ISMSMSG_AddOpt(m_pISMSMsg, sOpts);
if (SUCCESS != res)
{
DBGPRINTF( ""Failed on ISMSMSG_AddOpt( MSGOPT_PAYLOAD_ENCODING=AEE_ENC_ISOLATIN1 )"" );
return res;
}
CALLBACK_Init(
&m_cbSendMessage,
&CSMSSender::s_OnSMSSend,
this
);
ISMS_SendMsg(
m_pISMS,
m_pISMSMsg,
&m_cbSendMessage,
&m_dwSMSSendResult
);
return(SUCCESS);"

ITAPI_SendSMS doesn't work ok in Razr (loads of issues, acknoledged by Motorola). You would be better off in using ISMS API.

ITAPI_SendSMS doesn't work ok in Razr (loads of issues, acknoledged by Motorola). You would be better off in using ISMS API.

As you can see from my message I _did_ use ISMS and it does not work.

As you can see from my message I _did_ use ISMS and it does not work.

Recently 3 people are having same problem. This should not be an issue at all as it worked for me and many people.
Check this link and try that way
http://brewforums.qualcomm.com/showthread.php?t=11434

Recently 3 people are having same problem. This should not be an issue at all as it worked for me and many people.
Check this link and try that way
http://brewforums.qualcomm.com/showthread.php?t=11434

Their implementation for ISMS is terrible and the same for ITAPI, at least in the firmware I was testing with. I tested with 3 different devices of V3C and all failed. Testing with other devices such as Telit 120 and Motorola V710 worked.
The final conclusion is that Motorola's V3C BREW implementation contains critical bugs so someone in Motorola Mobile needs to work harder.
There was no "solution" offered in that link you gave. This guy was saying that his application was crashing because a bug he finally found somewhere else in his program not related to ISMS at all.
Thanks anyway. My customer blames me for Motorola bugs and thinks I am making excuses, that's bad enough.
That's not the first time I encounter faulty BREW implementations making me think twice before ever starting a new application based on BREW as this V3C is a BREW 3.1 device and there's no excuse for such critical bugs to appear there.

Their implementation for ISMS is terrible and the same for ITAPI, at least in the firmware I was testing with. I tested with 3 different devices of V3C and all failed. Testing with other devices such as Telit 120 and Motorola V710 worked.
The final conclusion is that Motorola's V3C BREW implementation contains critical bugs so someone in Motorola Mobile needs to work harder.
There was no "solution" offered in that link you gave. This guy was saying that his application was crashing because a bug he finally found somewhere else in his program not related to ISMS at all.
Thanks anyway. My customer blames me for Motorola bugs and thinks I am making excuses, that's bad enough.
That's not the first time I encounter faulty BREW implementations making me think twice before ever starting a new application based on BREW as this V3C is a BREW 3.1 device and there's no excuse for such critical bugs to appear there.

Silver Armor,
I was trying to give you some sample code, not the solution for your code. These kind of problem will always exist in any of the mobile/handheld platforms with different manufacturers. If the problem is 100% exist then we may either get a work around or changing/removing our feature in the app for that handset before releasing it the public.
I understand your frustration and agree it is pain to do some R&D each time, but things will get settled once the problem is identified. In this forum, there are lot of solutions were posted and you can search and use it.
Thanks
BRU

Silver Armor,
I was trying to give you some sample code, not the solution for your code. These kind of problem will always exist in any of the mobile/handheld platforms with different manufacturers. If the problem is 100% exist then we may either get a work around or changing/removing our feature in the app for that handset before releasing it the public.
I understand your frustration and agree it is pain to do some R&D each time, but things will get settled once the problem is identified. In this forum, there are lot of solutions were posted and you can search and use it.
Thanks
BRU