[Asterisk-Users] Registration from <xxx> failed for 'xxx'

Thomas Gallaway rescue at port11.net
Fri Mar 19 16:26:31 MST 2004


Eric Wieling wrote:

>If the phones are behind NAT you can try lowering the registration
>interval to something LESS than 4 hours, like 60 seconds or 120
>seconds.  Usually this problem is because the NAT firewall sees no
>activity on the registration port and so deletes the NAT translation for
>that port.
>
>On Fri, 2004-03-19 at 16:26, Thomas Gallaway wrote:
>  
>
>>Hi
>>
>>Here is my problem. I have 2 phones (Grandstream Budge Tone-100) loosing 
>>the sip registration
>>every 4 hours. I can not find out why.
>>
>>It seems like the registration fails, then a few minutes after registers 
>>sucessfull.
>>
>>Mar 19 14:06:14 NOTICE[147466]: Registration from 
>>'<sip:114 at 192.168.1.3;user=phone>' failed for '192.168.1.114'
>>-- Executing NoOp("SIP/114-5d35", "") in new stack
>>-- Registered SIP '114' at 192.168.1.114 port 5060 expires 180
>>
>>sip show peers show's me this:
>>116/116          192.168.1.116   (D)  255.255.255.255  5060     Unmonitored
>>114/114          (Unspecified)   (D)  255.255.255.255  0        Unmonitored
>>113/113          192.168.1.113   (D)  255.255.255.255  5060     Unmonitored
>>
>>Thanks for any input on this.
>>
>>-- Thomas
>>    
>>

Not using nat. That is the weird thing. They are all directly connected 
on the same switch as asterisk.

-- Thomas



More information about the asterisk-users mailing list