4G calls fail Samsung Galaxy Nexus

[lifespeed]

So, I had to try this and my hopes were high. Hopefully it is not the result of the evil Verizon Wireless blocking SIP applications. There are two calls in the log, first never connected while the second rang and connected with audio, but failed after a short time.

Have you guys tested on Android Ice Cream Sandwich and/or 4G?

Regards,

log#66D97B31

[Mike McMullen]

Case is being handled by support.

[lifespeed]

3G calls fail also, which may actually be a good sign, ie. not a VZW blocking problem.

[cralls]

Same issue here on Samsung Stratosphere. I've tried every combination of network traversal. I've tried on 3G, 4G, and Wifi with no success. I can hear callers but callers cannot hear me. x-lite works on my wifi network from my laptop.

[adonis]

Cralls,

your issue is slightly different than lifespeed's. Please send us an email at support at counterpath dot com address with a log file after reproducing the issue.

[lifespeed]

I figured this out, with the help of some bright guys on DSLreports voip tech chat forum http://www.dslreports.com/forum/r267429 ... art=40#end.

It seems Verizon has implemented a SIP proxy, but it only performs it's mangling on port 5060. Switching to port 5061 allows VoIP over 3/4G to continue unmolested. And with 4G bandwidth, the horror of cellphone audio can easily be supplanted with G722 or G711. So in the end, it is the fault of Verizon Wireless. Doesn't everybody know by now that SIP ALG or other such manipulative tomfoolery by the router is not helpful? We have SIP clients and servers that have long been designed to traverse NAT without the "help" of the router.

If there is anything that can be done to make Bria more resilient, I suggest it is still worthwhile. See the last two pairs of logs posted in the above thread failed using port 5060 and successful using port 5061.