Re: Nokia 808 VOIP and keep-alive process for NAT etc

[alexd]

[This belongs over in uk.telecom.voip really]

Peter (for it is he) wrote:

> Agreed 100% but even when I keep "sticking" ALWAYS ON in there, it
> doesn't do anything.

That's surely a bug, although if you've ever managed to receive a call then
I would think it's a user interface display bug, as the phone would surely
ignore incoming calls if it didn't think it was registered.

> I see no evidence of anything being sent out, because the NAT hole
> closes always after 180 seconds.

Your phone may well be sending it, but [to rephrase what I said earlier] if
the far end doesn't support it or doesn't like it, you'll see no difference.

> The proxy server config is blank.

> The registrar server is configured correctly, AFAICT.
>
> What do these two servers do?

Sorry, I've conflated the two terms here.

Proxy = thing you make calls through
Registrar = thing that you subscribe with, in order to receive calls

These are often one and the same, and even if they're not, manufacturers
confuse them as well:

http://www.smartvox.co.uk/sipfaq_sipproxy_explained.htm

Perhaps as an experiment you might like to fill in the proxy server config
as well.

--
<http://ale.cx/> (AIM:troffasky) (UnSoEs...@ale.cx)
10:18:35 up 9 days, 2:14, 4 users, load average: 1.96, 1.39, 1.20
Qua illic est reprehendit, illic est a vindicatum

[alexd]

Peter (for it is he) wrote:

> alexd <trof...@hotmail.com> wrote

>>Your phone may well be sending it, but [to rephrase what I said earlier]
>>if the far end doesn't support it or doesn't like it, you'll see no
>>difference.
>

> I don't think the phone is sending *anything* because if it did, to
> any IP whatever, the NAT session would not be closing after 3 mins.

We're [most likely] talking about UDP here. There's no UDP keepalive
mechanism like there is in TCP, and as such, if you want to keep a UDP
'session' alive you have to do it at the application layer. That's what
RFC4028 is. So, if the far end doesn't support it...

--
<http://ale.cx/> (AIM:troffasky) (UnSoEs...@ale.cx)

21:29:33 up 9 days, 13:25, 5 users, load average: 0.83, 0.92, 0.86

[R. Mark Clayton]

"alexd" <trof...@hotmail.com> wrote in message
news:kins9b$v5a$1...@dont-email.me...

> Peter (for it is he) wrote:
>
>> alexd <trof...@hotmail.com> wrote
>
>>>Your phone may well be sending it, but [to rephrase what I said earlier]
>>>if the far end doesn't support it or doesn't like it, you'll see no
>>>difference.
>>
>> I don't think the phone is sending *anything* because if it did, to
>> any IP whatever, the NAT session would not be closing after 3 mins.
>
> We're [most likely] talking about UDP here. There's no UDP keepalive
> mechanism like there is in TCP, and as such, if you want to keep a UDP
> 'session' alive you have to do it at the application layer. That's what
> RFC4028 is. So, if the far end doesn't support it...

IIRC this is configurable, OTOH it will put your bill up.

[R. Mark Clayton]

"Peter" <occassional...@nospam.co.uk> wrote in message
news:ue71l811d1v792sou...@4ax.com...
> This is the config I am using, and maybe VOIP experts might see
> something odd:
>
> Profile name
> didlogic
> Service profile
> IETF
> Default destination
> Internet
> Public username
> sip:12...@sip.didlogic.net
> Use compression
> NO
> Registration
> Always ON
> Use Security
> NO
>
> Proxy server address
> sip:sip.didlogic.net **
> Realm
> sip.didlogic.net **
> Username
> none
> Password
> none
> Allow Loose routing
> YES
> Transport type
> UDP
> Port
> 5060
>
> Registrar server address
> sip:sip.didlogic.net
> Username
> 12345
> Password
> my password
> Transport type
> UDP
> Port
> 5060
>
> The funny thing is that if I put in the bits marked **, it stops
> working totally. So it looks like it doesn't like the proxy server.

I use an N8 with Voipfone (and other devices) the user name and password are
the same as for registration.

>
> Their Nokia FAQ is here
> http://didlogic.com/support/setup-guides/did-for-your-nokia
>
> but it's ambiguous as to how that applies to the Nokia client (non
> Asterisk AFAICT).
>
> Nothing I do seems to create any kind of keep-alive process - evident
> from the router's NAT hole closing after 180 seconds exactly, from the
> last activity on port 5060.