In article <m2gh1v$lp$
1...@dont-email.me>,
Peter <
occassional...@nospam.co.uk> writes:
> The standard UDP port 5060 is totally blocked.
Just tried it over 3G from my mobile (3G contract) to my home server,
and port 5060 works fine.
> Another similar port # which the SIP provider gave me almost works but
> the voice is so broken up it is useless. I can't tell whether this is
> due to the link too slow / not the right codec / Voda detecting VOIP
> and buggering it up.
>
> This is on HSPA, 3mbits/sec.
>
> It worked fine Dec 2013...
>
> There is a lot of stuff on google about this (Voda blocking Skype etc)
> but most of it pre-dates 12/2013 so doesn't make sense.
>
> I've emailed Voda - no reply of course from their script chimps in
> India...
>
> The SIP login is established OK - presumably this is over port 80. The
> SIP provider offers TLS (443) for this but that won't help because the
> voice is still carried openly over 5060 or whatever.
SIP login (or rather, registration) is on port 5060.
Call setup is on port 5060.
Voice is carried on different ports, which are agreed between the
two parties during call setup.
> There are wholly-443 solutions but only for Iphone or Android. I have
> a Nokia 808...
>
> VOIP works brilliantly on the 808 but only on WIFI, as a result of the
> above.
Broken up voice may simply be down to the quality of Vodafone's IP
access network. It has noticably deteriorated over the last few years
on 3G, IME, and voice does require better quality than most other
things, because it's realtime.
--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]