Extension ip 0.0.0.0

Seemingly randomly after days, weeks or even a months of up time on a phone, the endpoint will show up with an ip of 0.0.0.0 in endpoint manager/extension mapping.
Incoming calls to the extension will fail, but outgoing calls can be made from the extension, I believe because “Outgoing Call Without Registration” is set to yes.

“Sip Show Peers” shows the extension as up but with a 0.0.0.0 address.
2111/2111 0.0.0.0 D No No A 5060 OK (1 ms)
VS an extension thats unused right now.
1255/1255 (Unspecified) D No No A 0 UNKNOWN
VS a working extension
2110/2110 10.20.254.39 D No No A 5060 OK (6 ms)
Most extensions are ~6ms. I’m thinking my server is responding to the 0.0.0.0 requests causing the shorter 1ms response.

The phones have good network connectivity and I can login via the GUI.
In the Phone GUI the Account Status is "Registered"
Changing any value under the account tab will bring the extension back up.
I usually change the “Register Expiration” value from 15 to 14, SaveSet and that will bring the extension right back up.
Also a reboot of the phone will bring the extention back online.

All phones on this PBX are Sangoma S500 or S700 phones.
Any ideas on what could be causing this behavior?

EDIT: Added more info

When the phones reregister, first the phone sends a request without the authentication information an gets a 401 unauthorized form the server. Then the phone sends registration with the authentication and gets a 200 OK. I see this on both working and not working phones so I’m guessing thats normal behavior?

In packet captures I see 0.0.0.0 in the registration request where a working phone has its ip address.

Extension thats not working

    To: "3217" <sip:[email protected]:5061>
        SIP Display info: "3217"
        SIP to address: sip:[email protected]:5061
            SIP to address User Part: 3217
            SIP to address Host Part: 10.10.70.7
            SIP to address Host Port: 5061
    Call-ID: [email protected]
    CSeq: 4936 REGISTER
        Sequence Number: 4936
        Method: REGISTER
    Contact: <sip:[email protected]:5060;transport=UDP>
        Contact URI: sip:[email protected]:5060;transport=UDP
            Contact URI User Part: 3217
            Contact URI Host Part: 0.0.0.0
            Contact URI Host Port: 5060
            Contact URI parameter: transport=UDP

Working extension

    To: "1008" <sip:[email protected]:5061>
        SIP Display info: "1008"
        SIP to address: sip:[email protected]:5061
            SIP to address User Part: 1008
            SIP to address Host Part: 10.10.70.7
            SIP to address Host Port: 5061
    Call-ID: [email protected]
    CSeq: 13132 REGISTER
        Sequence Number: 13132
        Method: REGISTER
    Contact: <sip:[email protected]:5060;transport=UDP>
        Contact URI: sip:[email protected]:5060;transport=UDP
            Contact URI User Part: 1008
            Contact URI Host Part: 10.10.254.48
            Contact URI Host Port: 5060
            Contact URI parameter: transport=UDP

Broken extensions do get a 200 (OK) back from the server after sending the registration request.
I also don’t see any Request: OPTIONS on a broken extension packet capture.

I know this ticket is approaching 4 years old, but did you ever find a fix for this?

We have the same thing happening and I’d love to know how to fix it.

The issue has been resolved but I don’t remember what fixed it. I believe it was an issue in the network and not something in FreePBX. This was happening on HPE Comware equipment at the time. What does your network stack look like?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.