Caller ID with Dell Voice

[neronut]

Howdy everyone,

When I make calls from my Dell Voice app no name gets passed along to the other party. Is it suppose to? If so, does it just use the 911 info that one provides?

Thanks,

[TheHardy]

When I make calls from my Dell Voice app no name gets passed along to the other party. Is it suppose to? If so, does it just use the 911 info that one provides?

AFAIK, this is the "correct" behavior from DV and Fongo apps --- to ONLY pass the number. Name is passed only on SIP to SIP calls, not on calls to POTS/VOIP numbers ...

It was discussed elsewhere WHY this was (cost issue I think). So only the # being passed _IS_ the behavior to expect.

[neronut]

If I use the FPL app and set the Caller ID there and call my cell number Rogers One Number (RON) shows what text I entered in the app and my number. Is this because it is also SIP and the info somehow passes? Strange happenings...

At least now I know this is normal and something isn't wrong.

Off-topic: TheHardy, how's the latency and jitter on a 3G stick for SIP calls?

[dibsmft]

If you are calling a service that has caller ID and does name lookups then the caller should/may see your name if you are listed (which you might not be) but if you call a service that does not do caller-name lookups then you will only see the phone number or perhaps Anonymous or Unknown. It would help if Fongo would allow the use of your PSTN or mobile number if you have one rather than the number that they give you so caller ID lookups would work more often. Sometimes, your phone, if it is cordless or an IP phone, will look the caller up in its local directory and so that information (Usually name and number) if it is shown. Since my phone system uses only voip and no caller ID I normally see the phones directory information which gives me the name and number just like caller ID.

[TheHardy]

Off-topic: TheHardy, how's the latency and jitter on a 3G stick for SIP calls?

Using the stick is hit and miss (best description). I almost always have "service" but if I don't have a strong signal, the voice quality and drop outs can make the call darn near impossible. Being that I am with WIND and in a supposedly STRONG signal area, I would rate my QoS and consistency about 80+% ... there are times, especially in bad weather, where my calls are so broken and fragmented, that tin cans and string sound more viable! That all said, it is more of the ISP/carrier issue than anything FPL.

When I generally make calls, I do have most other progs on my confuser closed, to max the processor time for the app ... on INCOMING calls, it can be problematic to get crap closed to have the call succeed, but as long as I can see who called (this is a MAJOR gripe I have with FPL 3.0.3.0 -- the CID on inbound calls is broken, and I have to use my CALL LOGS to see who called!!!), I can generally call back when my confuser is in a more stable mode for a successful call.

I don't have hard and fast numbers for you as for jitter and latency, as even though I am at the "supposed higher threshhold" of what others have told me, I would still rate it as passable service (except incoming, see above for why!).