- Joined
- Feb 21, 2008
- Messages
- 60
- Reaction score
- 0
Help!
Anyone know why I have frequent loss of registration with my voip provider. Reg'n sometimes lasts for hours, sometimes for minutes. Does this part of my log give a hint?
17:25:34.078 ClientRegs:nFailure [CM504007]: Next attempt to register 10006@RAINTEL is scheduled in 10 minutes
17:25:34.078 ClientRegs:nFailure [CM504005]: Registration failed for: 10006@RAINTEL; Cause: 408 Request Timeout; internal
17:24:22.593 StunClient:nInitTests [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.23:3478 over Transport 192.168.1.40:5060
When I manually register the line, I have success. The big questions is why that registration is not maintaned. I am running the Apr 2 08 latest known version, behind a linksys wrt 54g with recommended port forwarding. One thing I do notice about the latest build is that the bridge is now producing proper rtp audio.
Anyone know why I have frequent loss of registration with my voip provider. Reg'n sometimes lasts for hours, sometimes for minutes. Does this part of my log give a hint?
17:25:34.078 ClientRegs:nFailure [CM504007]: Next attempt to register 10006@RAINTEL is scheduled in 10 minutes
17:25:34.078 ClientRegs:nFailure [CM504005]: Registration failed for: 10006@RAINTEL; Cause: 408 Request Timeout; internal
17:24:22.593 StunClient:nInitTests [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.23:3478 over Transport 192.168.1.40:5060
When I manually register the line, I have success. The big questions is why that registration is not maintaned. I am running the Apr 2 08 latest known version, behind a linksys wrt 54g with recommended port forwarding. One thing I do notice about the latest build is that the bridge is now producing proper rtp audio.