[Spce-user] Upper registration to Asterisk - phones unreachable after a while

[Theo]

Hi John

I agree that that stuff is almost never helpful (sip-alg in routers for
example). Unless there is a setting I am overlooking, there is nothing like
that enabled on the SNOM. STUN is off. SIP ALG on the router is off as well.

On Fri, Feb 15, 2013 at 2:24 PM, John Murray <john.murray at skyracktelecom.com
> wrote:

> Theo,****
>
> ** **
>
> Almost certainly the Snom is trying to be NAT ‘helpful’ so doing STUN or
> some such thing by discovering the NAT external address and including it in
> the SIP header. This fools the SPCE into thinking the device is not behind
> a NAT device.****
>
> Please disable any NAT ‘helper’ stuff which is usually not helpfull.****
>
> ** **
>
> Regards****
>
> ** **
>
> John****
>
> ** **
>
> *From:* spce-user-bounces at lists.sipwise.com [mailto:
> spce-user-bounces at lists.sipwise.com] *On Behalf Of *Theo
> *Sent:* 15 February 2013 11:58
> *To:* Daniel Grotti
> *Cc:* spce-user at lists.sipwise.com
> *Subject:* Re: [Spce-user] Upper registration to Asterisk - phones
> unreachable after a while****
>
> ** **
>
> HI Daniel****
>
> ** **
>
> SCPE - open internet, no NAT in front, nor any firewall. Device is on a
> simple network with a TP-Link router which means it's behind NAT. What
> could be the cause of the SCPE not detecting NAT?****
>
> On Fri, Feb 15, 2013 at 1:54 PM, Daniel Grotti <dgrotti at sipwise.com>
> wrote:****
>
> Hi Theo,
> If SPCE didn't figure out that your client is behind nat, then it won't
> perform the nat_sipping.
> What are the network of your client,of your NAT device and of your SCPE ?
>
> Daniel****
>
>
>
>
>
>
> On 02/15/2013 12:37 PM, Theo wrote:****
>
> Hi ****
>
> ** **
>
> Nope, the problem persists. Been fine for a couple of hours. Then all of a
> sudden - local user offline. Will try 2, 3 times, then the 4th time it's
> online again, presumably because a registration came through or
> whatever.......****
>
> On Fri, Feb 15, 2013 at 10:28 AM, Theo <axessofficetheo at gmail.com> wrote:*
> ***
>
> Hi Daniel ****
>
> ** **
>
> I have just tried that - let's see if it does the trick. I had assumed
> that a new registration attempt every 30 seconds or so would do the trick.
> Strange enough, it DOES sent a registration, but the webinterface on
> sipwise shows the last registration as 30 minutes ago. It also shows, under
> active registrations NAT = no. But the phone is behind NAT - is there a
> setting similar to ASTERISK where one specifies that or is it meant to just
> detect it?****
>
> ** **
>
> Cheers****
>
> ** **
>
> Theo ****
>
> ** **
>
> On Fri, Feb 15, 2013 at 10:16 AM, Daniel Grotti <dgrotti at sipwise.com>
> wrote:****
>
> Hi, ****
>
> if the client is behind nat you can try to set a nat keep alive on the
> snom. ****
>
> ** **
>
> Daniel****
>
>
>
>
> Sent from Samsung Mobile ****
>
>
>
>
> African Axess African Axess <axessofficetheo at gmail.com> wrote:
>
>
> Hi ****
>
> ** **
>
> With the help of this list I have upper registration working and can phone
> between extensions. However, at (seemingly) random, the devices cannot be
> reached. All appears fine and they appear registered, but when I make the
> call it doesn't work, until I log into my device and click "re-register".
> The proxy log is fairly clear:****
>
> ** **
>
> Feb 15 08:13:22 sipwise /usr/sbin/kamailio[2138]: INFO: <script>: Local
> user offline -
> R=sip:user404 at my.domain.com:5060;uuid=c6d7434d-5026-4394-86d5-d3c43d2fd2cc
> ****
>
> ** **
>
> telling me that the user is offline. Question of course is - how do I
> avoid them going offline. The phones are set to re-register every 60
> seconds, but that doesn't seem to do the trick. Once this happens, only a
> physical "re-register" the phone by doing it manually gets it back up
> again. This is with SNOM 300 phones.****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130215/3ee3c7b2/attachment-0001.html>