Click here to get back home

Delay on one end in receiving LINECALLSTATE_CONNECTED
 Home | NewsGroups | Search | About
Login Password
Register Now! Lost Password?
 microsoft.public.smartphone    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
Delay on one end in receiving LINECALLSTATE_CONNECTED ralphdepping 10-26-2006
Get Chitika Premium
Posted by ralphdepping on October 26, 2006, 6:00 am
Please log in for more thread options
 Hi All,
when making a data call between 2 mobile phones one of the phones
receives the LINECALLSTATE_CONNECTED before the other phone. We've
seen two distinct cases:

1.) There is about a 12 second delay between receiving the connect on
one phone and then the other.
2.) The first phone receives the connect and the second phone doesn't
receive the connect. When you hang up on the first phone the second
phone then receives the connect.

What, in general, could cause this behaviour?

Here is the setup:

Developing on Windows Mobile 5.0 with a couple of Qtek phones - 8500
and 8310. Using a GSM data channel (CSD) to make a data connection
between two mobile phones.

- When making the call between two 8310 phones there are no problems,
the connect is received at both ends at roughly the same time.

- When making a call from the 8310->8500 we have no problems, the
connect is received at both ends at roughly the same time.

- When making a call from the 8500->8310 we see the problems as
detailed in 1.) and 2.) above.

If there are further details that I should provide please let me know,
Ralph


Posted by Grant Schenck on October 26, 2006, 8:55 am
Please log in for more thread options
 Does the audio actually connect at the same time? Is it only the TAPI call
state event which is delayed?

Is it the same phone in the interaction (i.e., the calling phone or the
called phone) which exhibit the problems or is it random?

Bottom line is that if the problem is the delayed event then ultimately this
has to be a problem either in the actual connection detection in the
scenario you describe or a bug in the TAPI Service Provider (TSP) where
somehow it gets confused. Given that your only option may be to work
directly with the vendor who provided the hardware/TSP.
--
Grant Schenck
http://grantschenck.tripod.com/

> Hi All,
> when making a data call between 2 mobile phones one of the phones
> receives the LINECALLSTATE_CONNECTED before the other phone. We've
> seen two distinct cases:
>
> 1.) There is about a 12 second delay between receiving the connect on
> one phone and then the other.
> 2.) The first phone receives the connect and the second phone doesn't
> receive the connect. When you hang up on the first phone the second
> phone then receives the connect.
>
> What, in general, could cause this behaviour?
>
> Here is the setup:
>
> Developing on Windows Mobile 5.0 with a couple of Qtek phones - 8500
> and 8310. Using a GSM data channel (CSD) to make a data connection
> between two mobile phones.
>
> - When making the call between two 8310 phones there are no problems,
> the connect is received at both ends at roughly the same time.
>
> - When making a call from the 8310->8500 we have no problems, the
> connect is received at both ends at roughly the same time.
>
> - When making a call from the 8500->8310 we see the problems as
> detailed in 1.) and 2.) above.
>
> If there are further details that I should provide please let me know,
> Ralph
>



Posted by ralphdepping on October 26, 2006, 11:19 am
Please log in for more thread options

Grant Schenck wrote:
> Does the audio actually connect at the same time? Is it only the TAPI call
> state event which is delayed?
>

I am waiting for the connect message before starting communications
(using a serial interface to the modem to transfer data). So the first
phone (which receives the connect in a timely fashion) begins
transmitting and receiving. As the connect wasn't received at the
other end I don't being transmitting or receiving at that end (so I
haven't verified if the line is actually open). So I can try and have
both sides tx/rx from an earlier point and see if the line is up, even
though I don't receive the connect on one end. What do you think?

> Is it the same phone in the interaction (i.e., the calling phone or the
> called phone) which exhibit the problems or is it random?
>

I tried to detail the phone interaction in my original post. Basically
it is only a problem for the QTEK 8500 making a call. When receiving a
call it is fine.

> Bottom line is that if the problem is the delayed event then ultimately this
> has to be a problem either in the actual connection detection in the
> scenario you describe or a bug in the TAPI Service Provider (TSP) where
> somehow it gets confused. Given that your only option may be to work
> directly with the vendor who provided the hardware/TSP.

Thanks for your time and help. It may be that we need to talk to QTEK.
There are well publicised issues with the 8500 (with a new ROM image
in the pipe works) and it may be that we're coming up against a problem
at that end. However we're assuming at the moment the problem is
elsewhere (i.e. one that we may have introduced....although it seems to
be strongly phone/scenario dependent)
> --
> Grant Schenck
> http://grantschenck.tripod.com/
>
> > Hi All,
> > when making a data call between 2 mobile phones one of the phones
> > receives the LINECALLSTATE_CONNECTED before the other phone. We've
> > seen two distinct cases:
> >
> > 1.) There is about a 12 second delay between receiving the connect on
> > one phone and then the other.
> > 2.) The first phone receives the connect and the second phone doesn't
> > receive the connect. When you hang up on the first phone the second
> > phone then receives the connect.
> >
> > What, in general, could cause this behaviour?
> >
> > Here is the setup:
> >
> > Developing on Windows Mobile 5.0 with a couple of Qtek phones - 8500
> > and 8310. Using a GSM data channel (CSD) to make a data connection
> > between two mobile phones.
> >
> > - When making the call between two 8310 phones there are no problems,
> > the connect is received at both ends at roughly the same time.
> >
> > - When making a call from the 8310->8500 we have no problems, the
> > connect is received at both ends at roughly the same time.
> >
> > - When making a call from the 8500->8310 we see the problems as
> > detailed in 1.) and 2.) above.
> >
> > If there are further details that I should provide please let me know,
> > Ralph
> >


Posted by ralphdepping on October 26, 2006, 11:31 am
Please log in for more thread options
Hi All/Grant,
re-reading my posts I probably wasn't very clear. Here's what I see
happening....

- Make a call from an 8500 to an 8310.
- The 8500 receives a connect message within a reasonable amount of
time.
- The 8310 does not receive a connect message.
- Hang up on the 8500. The 8310 now receives the connect message.

I can make calls from the 8310 to the 8500 and from one 8310 to another
8310 without any issue (i.e. both phones receive the connect in a
timely fashion, start tx/rx and receive data on both phones).

It's a strange problem. Why would disconnecting on the 8500 suddenly
cause the connect to appear on the 8310?

Thanks,
Ralph


ralphdepp...@googlemail.com wrote:
> Grant Schenck wrote:
> > Does the audio actually connect at the same time? Is it only the TAPI call
> > state event which is delayed?
> >
>
> I am waiting for the connect message before starting communications
> (using a serial interface to the modem to transfer data). So the first
> phone (which receives the connect in a timely fashion) begins
> transmitting and receiving. As the connect wasn't received at the
> other end I don't being transmitting or receiving at that end (so I
> haven't verified if the line is actually open). So I can try and have
> both sides tx/rx from an earlier point and see if the line is up, even
> though I don't receive the connect on one end. What do you think?
>
> > Is it the same phone in the interaction (i.e., the calling phone or the
> > called phone) which exhibit the problems or is it random?
> >
>
> I tried to detail the phone interaction in my original post. Basically
> it is only a problem for the QTEK 8500 making a call. When receiving a
> call it is fine.
>
> > Bottom line is that if the problem is the delayed event then ultimately this
> > has to be a problem either in the actual connection detection in the
> > scenario you describe or a bug in the TAPI Service Provider (TSP) where
> > somehow it gets confused. Given that your only option may be to work
> > directly with the vendor who provided the hardware/TSP.
>
> Thanks for your time and help. It may be that we need to talk to QTEK.
> There are well publicised issues with the 8500 (with a new ROM image
> in the pipe works) and it may be that we're coming up against a problem
> at that end. However we're assuming at the moment the problem is
> elsewhere (i.e. one that we may have introduced....although it seems to
> be strongly phone/scenario dependent)
> > --
> > Grant Schenck
> > http://grantschenck.tripod.com/
> >
> > > Hi All,
> > > when making a data call between 2 mobile phones one of the phones
> > > receives the LINECALLSTATE_CONNECTED before the other phone. We've
> > > seen two distinct cases:
> > >
> > > 1.) There is about a 12 second delay between receiving the connect on
> > > one phone and then the other.
> > > 2.) The first phone receives the connect and the second phone doesn't
> > > receive the connect. When you hang up on the first phone the second
> > > phone then receives the connect.
> > >
> > > What, in general, could cause this behaviour?
> > >
> > > Here is the setup:
> > >
> > > Developing on Windows Mobile 5.0 with a couple of Qtek phones - 8500
> > > and 8310. Using a GSM data channel (CSD) to make a data connection
> > > between two mobile phones.
> > >
> > > - When making the call between two 8310 phones there are no problems,
> > > the connect is received at both ends at roughly the same time.
> > >
> > > - When making a call from the 8310->8500 we have no problems, the
> > > connect is received at both ends at roughly the same time.
> > >
> > > - When making a call from the 8500->8310 we see the problems as
> > > detailed in 1.) and 2.) above.
> > >
> > > If there are further details that I should provide please let me know,
> > > Ralph
> > >


Posted by Grant Schenck on October 26, 2006, 3:40 pm
Please log in for more thread options
Sorry, I hadn't realized it was a data call.

Bottom line it sure sounds like an issue in your 8500's TSP.
--
Grant Schenck
http://grantschenck.tripod.com/

> Hi All/Grant,
> re-reading my posts I probably wasn't very clear. Here's what I see
> happening....
>
> - Make a call from an 8500 to an 8310.
> - The 8500 receives a connect message within a reasonable amount of
> time.
> - The 8310 does not receive a connect message.
> - Hang up on the 8500. The 8310 now receives the connect message.
>
> I can make calls from the 8310 to the 8500 and from one 8310 to another
> 8310 without any issue (i.e. both phones receive the connect in a
> timely fashion, start tx/rx and receive data on both phones).
>
> It's a strange problem. Why would disconnecting on the 8500 suddenly
> cause the connect to appear on the 8310?
>
> Thanks,
> Ralph
>
>
> ralphdepp...@googlemail.com wrote:
>> Grant Schenck wrote:
>> > Does the audio actually connect at the same time? Is it only the TAPI
>> > call
>> > state event which is delayed?
>> >
>>
>> I am waiting for the connect message before starting communications
>> (using a serial interface to the modem to transfer data). So the first
>> phone (which receives the connect in a timely fashion) begins
>> transmitting and receiving. As the connect wasn't received at the
>> other end I don't being transmitting or receiving at that end (so I
>> haven't verified if the line is actually open). So I can try and have
>> both sides tx/rx from an earlier point and see if the line is up, even
>> though I don't receive the connect on one end. What do you think?
>>
>> > Is it the same phone in the interaction (i.e., the calling phone or the
>> > called phone) which exhibit the problems or is it random?
>> >
>>
>> I tried to detail the phone interaction in my original post. Basically
>> it is only a problem for the QTEK 8500 making a call. When receiving a
>> call it is fine.
>>
>> > Bottom line is that if the problem is the delayed event then ultimately
>> > this
>> > has to be a problem either in the actual connection detection in the
>> > scenario you describe or a bug in the TAPI Service Provider (TSP) where
>> > somehow it gets confused. Given that your only option may be to work
>> > directly with the vendor who provided the hardware/TSP.
>>
>> Thanks for your time and help. It may be that we need to talk to QTEK.
>> There are well publicised issues with the 8500 (with a new ROM image
>> in the pipe works) and it may be that we're coming up against a problem
>> at that end. However we're assuming at the moment the problem is
>> elsewhere (i.e. one that we may have introduced....although it seems to
>> be strongly phone/scenario dependent)
>> > --
>> > Grant Schenck
>> > http://grantschenck.tripod.com/
>> >
>> > > Hi All,
>> > > when making a data call between 2 mobile phones one of the phones
>> > > receives the LINECALLSTATE_CONNECTED before the other phone. We've
>> > > seen two distinct cases:
>> > >
>> > > 1.) There is about a 12 second delay between receiving the connect on
>> > > one phone and then the other.
>> > > 2.) The first phone receives the connect and the second phone doesn't
>> > > receive the connect. When you hang up on the first phone the second
>> > > phone then receives the connect.
>> > >
>> > > What, in general, could cause this behaviour?
>> > >
>> > > Here is the setup:
>> > >
>> > > Developing on Windows Mobile 5.0 with a couple of Qtek phones - 8500
>> > > and 8310. Using a GSM data channel (CSD) to make a data connection
>> > > between two mobile phones.
>> > >
>> > > - When making the call between two 8310 phones there are no problems,
>> > > the connect is received at both ends at roughly the same time.
>> > >
>> > > - When making a call from the 8310->8500 we have no problems, the
>> > > connect is received at both ends at roughly the same time.
>> > >
>> > > - When making a call from the 8500->8310 we see the problems as
>> > > detailed in 1.) and 2.) above.
>> > >
>> > > If there are further details that I should provide please let me
>> > > know,
>> > > Ralph
>> > >
>



Similar ThreadsPosted
delay in receiving email August 2, 2006, 9:38 am
Delay after I pick up in WM 2003 based Smartphone November 27, 2005, 5:11 pm
8 Minute Email Push Delay in Activesync with Blackjack II March 27, 2008, 4:41 pm
WM5 bug when receiving SMS? January 9, 2006, 10:21 am
Receiving SMS - eVB 3.0 September 1, 2006, 4:31 pm
Outlook sending and receiving July 5, 2005, 5:45 am
SPV C550 Bluetooth Receiving Files October 11, 2005, 2:11 pm
IE not receiving cookie for forms authentication November 8, 2006, 3:53 pm
Automatically activate application on receiving SMS December 21, 2006, 1:12 am
Receiving call inside baground application and Interjecting Sound with receivers voice. October 10, 2006, 10:35 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap