PBXes » Search » Search Results
Showing posts 1 to 3 of 3 results
Author Post
Thread: RE: Can't register. Reply packets never reach me.
maz

Replies: 1
Views: 7208

Can't register. Reply packets never reach me. 10.01.2014 09:45 Forum: Bugs

One of my phones (extension 6) just suddenly stopped being able to register with no changes on my side. I've tried rebooting the cable modem, the router, the voip box, no change.

Running tcpdump on the router (linux box which performs static nat from 192.168.1.2:5061 to my.static.public.ip:5061 and back on both egress and ingress) shows outgoing registration requests, but no incoming responses.

I know I can reach my.static.public.ip:5061 over udp from an external test box…
So it's not just an outright connectivity problem.

The pbxes system log sip trace tool shows the registration request and seem to claim replies are being sent:

Jan 9 23:29:11 VERBOSE[84886] logger.c: Transmitting (NAT)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP my.static.public.ip:5061;branch=z9hG4bK-8153efde;received=76.191.104.53

But _where_ are they being sent to?

The received=76.191.104.53 is also curious, since the registration request is being sent to pbxes.org:5060 (188.40.65.170:5060) and not www2.pbxes.com (76.191.104.53).

Is there some sort of badly functioning redirect happening?

[Note: the 'unauthorized' is not a problem here, authorization would happen later, the problem is the 'unauthorized' message never actually reaches my router]

---

Interesting:

Jan 10 13:10:55 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-6' expires 3600

And the voip box agrees:

Registration State: Failed Last Registration At: 1/10/2014 13:10:55

So basically one registration succeeded and then it broke again…

---

And actually this (occasional success, mostly failure) seems to be happening on and off for all three of my extensions:

Jan 9 23:30:13 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-2' expires 3600
Jan 10 01:29:15 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-2' expires 3600
Jan 10 09:18:11 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-5' expires 3600
Jan 10 13:10:55 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-6' expires 3600
Jan 10 13:16:12 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-5' expires 3600
Jan 10 13:23:23 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-2' expires 3600
Jan 10 14:15:43 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-5' expires 3600
Jan 10 14:22:53 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-2' expires 3600

There should have been 3 successes per hour (or rather 3 per 59.5 minutes), instead we have 8 successes across 15 hours.

---

Hmm, I'm not actually sure that those logs are actually showing the full picture.
Seems like some logs are missing.

It is now 16:15 pacific [and my Personal Data page is set to pacific time zone]
voip box maz…-2 shows (+9 for Europe, makes it 01:15):

Current Time: 1/11/2014 01:15:06
Hook State: On Registration State: Registered
Last Registration At: 1/11/2014 00:22:23 Next Registration In: 408 s

This implies a successful registration at 00:22:23 which is 15:22:23 pacific,
but the last log for maz...-2 is:

Jan 10 14:22:53 VERBOSE[84886] logger.c: -- Registered SIP 'maz...-2' expires 3600

which means that somehow the last successful registration for maz…-2 is not showing up in the logs.

Thread: RE: www2.pbxes.com
maz

Replies: 4
Views: 8481

RE: www2.pbxes.com 23.01.2013 11:17 Forum: Bugs

Down for me as well. can't even view the ui on the web and phones don't work.

Thread: RE: Direct VOIP between two extensions (as opposed to via a proxy)
maz

Replies: 1
Views: 6227

Direct VOIP between two extensions (as opposed to via a proxy) 05.04.2011 09:59 Forum: Miscellaneous

I have three SIP ATA's (PAP2-NA, SPA-1001, SPA-3102) behind 3 different linux firewalls on 3 different internet providers. They register fine, however it would appear that calls between them are always going through a pbxes proxy (instead of going direct). Before I start searching for which aspect of my settings and NAT / port forwarding is misconfigured I thought maybe I'd ask here for some pointers (side note: this worked with another provider before I switched to pbxes)... Are such direct connections even supported by pbxes?

Showing posts 1 to 3 of 3 results

Powered by Burning Board Lite 1.0.2 © 2001-2004 WoltLab GmbH
English Translation by Satelk