Results 1 to 9 of 9

Thread: Unable to call INBOUND

  1. #1
    Join Date
    Feb 2007
    Posts
    423

    Default Unable to call INBOUND

    Was wondering if anyone had a similar issue. Outgoing calls worked, but ALL incoming calls went straight to failover to my cell phone. I unplugged the power to the grandstream 502 and re-powered it back up. All seems to be fine now. Anyone know if there were any maintenance or similar scheduled that may have "Burped" the connection. This is the 1st issue I've had with the 502, so I don't think it's a NAT issue or anything. Thanks... Mike....
    Mike
    "Born Wild - Raised Proud"
    Do you like your life? - Thank a Vet!!!

  2. #2
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,043

    Default Re: Unable to call INBOUND

    There were some MySQL cluster changes today that I don't believe affected service, but I guess there's a possibility if the registration came in exactly when the change was made or something like that.

    If you see the issue again, let us know.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  3. #3
    Join Date
    Feb 2007
    Posts
    423

    Default Re: Unable to call INBOUND

    Sounds good. Thanks tim.... Mike.....
    Mike
    "Born Wild - Raised Proud"
    Do you like your life? - Thank a Vet!!!

  4. #4
    Join Date
    Aug 2008
    Posts
    17

    Default Re: Unable to call INBOUND

    I'm having this same issue today. Anyone else? I called in a ticket and VOIPO said they would give me a call when they resolved the issue. My ATA says it is registered and it's been up for 45 days without any problems. I didn't reset it yet to see if they could figure out what is wrong.

  5. #5
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,043

    Default Re: Unable to call INBOUND

    Quote Originally Posted by rcboats24 View Post
    I'm having this same issue today. Anyone else? I called in a ticket and VOIPO said they would give me a call when they resolved the issue. My ATA says it is registered and it's been up for 45 days without any problems. I didn't reset it yet to see if they could figure out what is wrong.
    Have you tried rebooting it?
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  6. #6
    Join Date
    Apr 2008
    Location
    Aventura Fl
    Posts
    860

    Default Re: Unable to call INBOUND

    Quote Originally Posted by rcboats24 View Post
    I'm having this same issue today. Anyone else? I called in a ticket and VOIPO said they would give me a call when they resolved the issue. My ATA says it is registered and it's been up for 45 days without any problems. I didn't reset it yet to see if they could figure out what is wrong.
    No problems here..in Miami....

  7. #7
    Join Date
    Aug 2008
    Posts
    17

    Default Re: Unable to call INBOUND

    No, I figured that would fix the issue and support may not be able to look to see if the actual problem was not being registered, etc. On my side, the ATA still showed that it was registered and could make outbound calls. Support also got back to me via email and asked me to reboot the device so I assume they saw a registration issue. I checked again before rebooting and all incoming calls are working now so it's most likely that registration was lost somehow and the ATA re-registered on its own.

  8. #8
    Join Date
    Aug 2008
    Location
    San Francisco Bay Area
    Posts
    56

    Default Re: Unable to call INBOUND

    Quote Originally Posted by christcorp View Post
    Was wondering if anyone had a similar issue. Outgoing calls worked, but ALL incoming calls went straight to failover to my cell phone. I unplugged the power to the grandstream 502 and re-powered it back up. All seems to be fine now. Anyone know if there were any maintenance or similar scheduled that may have "Burped" the connection. This is the 1st issue I've had with the 502, so I don't think it's a NAT issue or anything. Thanks... Mike....
    I used my cell to phone my wife at home. My call was forwarded to my network down number which happened to be the cell phone I was using to place the call.
    Seems there might have been a brief problem.

  9. #9
    Join Date
    Feb 2007
    Posts
    270

    Default Re: Unable to call INBOUND

    Quote Originally Posted by GTOJim View Post
    I used my cell to phone my wife at home. My call was forwarded to my network down number which happened to be the cell phone I was using to place the call.
    Seems there might have been a brief problem.
    GTOJim,
    thanks, mb I should add this recursive network down forwarding "quirk"
    to my wish list
    my wish list:
    1. Intelligent Call Forwarding that detects the incoming call originated from the "forwarded" phone and rings the original destination instead
    2. Call History that makes use of CallerID/Custom CallerID+Location. Call History only shows Custom CallerId+Loc. No CNAM look up; Albeitly,it's a step in the right direction!
    3. Scheduled sim. ring with a twist (see wish #1)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •