Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Looks Interesting..

  1. #11
    Join Date
    Feb 2007
    Posts
    801

    Default Re: Looks Interesting..

    OK. First of all, I don't think VOIPo has provisioning set up, even for the Grandstream. Tim will have to weigh in on this (whether or not it's set up, and if not, an ETA). Since you have a PAP2 (or PAP2T--doesn't matter), getting you up and running should be pretty straightforward.
    • I presume you have the administrative password to the PAP, correct? If not, you will need it--you can get it from your current provider by submitting a support ticket or calling support. If you call, make sure you have the correct password while you have the support rep on the line (see the two steps below this one).
    • Do you know the IP address of your PAP? If not, you can get it by dialing **** on your phone. When the voice says configuration menu, dial 110# and get ready to write.
    • Browse to the following url, replacing the IP address here with the IP address of your PAP: http://your.pap.ip.address/admin . The "/admin" part is critical. When asked for username and password, use "admin" for the username and the password your provider gave to you.
    • The first thing you need to do is disable provisioning. Click on the word "Provisioning" and change the setting next to "Provision Enable" from Yes to No. For good measure, you might also change "Resync on Reset" and "Upgrade Enable" to No, also.
    • I assume you want to keep Line 1 set up with your current provider and use Line 2 for Voipo, at least for initial testing; directions here will follow that scheme. If you need help reconfiguring, you can always ask. Click on the words Line 2 in the top menu bar, and make sure the following parameters are as shown (some may already be correct) :
      • Line Enable: Yes
      • SAS Enable: No
      • NAT Mapping Enable: Yes
      • NAT Keep Alive Enable: Yes
      • SIP Port: 5080 (It should be different from the port that's set for Line 1. 5060 is generally the default primary (Line 1), 5061 default secondary (Line 2). I've had best luck with 5080.)
      • Proxy: codeblue.voipo.com
      • Register: Yes
      • User ID: (Your 10-digit VOIPo number--see your welcome email.)
      • Password: (See your welcome email.)
      • DTMF Tx Mode: Auto (Auto works for me; try the other settings if you can't use IVRs like business voicemail, banks, etc.)
      • Dial plan: (*xx|[49]11|0|00|[2-9]xxxxxxS2|[2-9]xx[2-9]xxxxxxS0|1xxx[2-9]xxxxxxS0)

    This dial plan will allow 0, 00, 411, 911, 7-digit local dialing, 10-digit (any area code) dialing, and 1+ (11-digit) dialing. There is no pattern in this dial plan to allow international calls, but they're disabled in the Beta, anyway. I'm not sure if 0, 00, or 411 connect to anything; 911 will route correctly within a few days of you entering your 911 info into the "vPanel".

    Once you click "Save Settings" your adapter will reboot, and if the Line 2 light comes on solid, you should be able to make calls on your voipo line. Please let us know how it goes...

  2. #12
    Join Date
    Feb 2007
    Posts
    801

    Default Re: Looks Interesting..

    So provisioning is enabled for the Grandstreams? Nice! Do Beta users (at this point) have access to the full (administrator) configuration menu of the Grandstream?

  3. #13
    Join Date
    Feb 2007
    Location
    Kitsap County, WA.
    Posts
    734

    Default Re: Looks Interesting..

    So provisioning is enabled for the Grandstreams? Nice! Do Beta users (at this point) have access to the full (administrator) configuration menu of the Grandstream?

    Yes and No... in that order.
    I Void Warranties.

  4. #14
    Join Date
    Apr 2008
    Location
    Aventura Fl
    Posts
    860

    Default Re: Looks Interesting..

    Quote Originally Posted by fisamo View Post
    So provisioning is enabled for the Grandstreams? Nice! Do Beta users (at this point) have access to the full (administrator) configuration menu of the Grandstream?
    To answer your questions above, I have all the access and was going to do this but I decided to get a Grandstream, since they support this and go from there.

    If VOIPo were to post a complete configuration for their service, I could easily set up the PAP2T, but till then, I'll wait for their adapter.

    Thanks again....

    burris

  5. #15
    Join Date
    Apr 2008
    Location
    Aventura Fl
    Posts
    860

    Default Re: Looks Interesting..

    Quote Originally Posted by fisamo View Post
    OK. First of all, I don't think VOIPo has provisioning set up, even for the Grandstream. Tim will have to weigh in on this (whether or not it's set up, and if not, an ETA). Since you have a PAP2 (or PAP2T--doesn't matter), getting you up and running should be pretty straightforward.
    • I presume you have the administrative password to the PAP, correct? If not, you will need it--you can get it from your current provider by submitting a support ticket or calling support. If you call, make sure you have the correct password while you have the support rep on the line (see the two steps below this one).
    • Do you know the IP address of your PAP? If not, you can get it by dialing **** on your phone. When the voice says configuration menu, dial 110# and get ready to write.
    • Browse to the following url, replacing the IP address here with the IP address of your PAP: http://your.pap.ip.address/admin . The "/admin" part is critical. When asked for username and password, use "admin" for the username and the password your provider gave to you.
    • The first thing you need to do is disable provisioning. Click on the word "Provisioning" and change the setting next to "Provision Enable" from Yes to No. For good measure, you might also change "Resync on Reset" and "Upgrade Enable" to No, also.
    • I assume you want to keep Line 1 set up with your current provider and use Line 2 for Voipo, at least for initial testing; directions here will follow that scheme. If you need help reconfiguring, you can always ask. Click on the words Line 2 in the top menu bar, and make sure the following parameters are as shown (some may already be correct) :
      • Line Enable: Yes
      • SAS Enable: No
      • NAT Mapping Enable: Yes
      • NAT Keep Alive Enable: Yes
      • SIP Port: 5080 (It should be different from the port that's set for Line 1. 5060 is generally the default primary (Line 1), 5061 default secondary (Line 2). I've had best luck with 5080.)
      • Proxy: codeblue.voipo.com
      • Register: Yes
      • User ID: (Your 10-digit VOIPo number--see your welcome email.)
      • Password: (See your welcome email.)
      • DTMF Tx Mode: Auto (Auto works for me; try the other settings if you can't use IVRs like business voicemail, banks, etc.)
      • Dial plan: (*xx|[49]11|0|00|[2-9]xxxxxxS2|[2-9]xx[2-9]xxxxxxS0|1xxx[2-9]xxxxxxS0)

    This dial plan will allow 0, 00, 411, 911, 7-digit local dialing, 10-digit (any area code) dialing, and 1+ (11-digit) dialing. There is no pattern in this dial plan to allow international calls, but they're disabled in the Beta, anyway. I'm not sure if 0, 00, or 411 connect to anything; 911 will route correctly within a few days of you entering your 911 info into the "vPanel".

    Once you click "Save Settings" your adapter will reboot, and if the Line 2 light comes on solid, you should be able to make calls on your voipo line. Please let us know how it goes...
    I just took a look. Turned provisioning off and changed those fields you listed. What about the stun server that still points to VTnoc, and also the dns that belongs to VT?

    Also interesting is after I insert the voipo password and save , it appears to revert to the old password. Can't read it, but the length is far greater than he one I was given..

  6. #16
    Join Date
    Feb 2007
    Posts
    801

    Default Re: Looks Interesting..

    For the time being, if you wanted to get away from any VTnoc addresses, you could use stun.fwdnet.net:3478 as the stun server (for now--may have to google for public stun servers if FWD doesn't last...), and for DNS, use 4.2.2.2 and 4.2.2.3. I do not know how these changes will impact your VT service, though. Does the voipo line indicate that it's registered with the VTnoc settings for stun and DNS?

    As for the password, the one you entered is still saved--I think Linksys just replaced whatever you type with a set number of *'s. If your line shows Registered, (or Online) on the info screen (first screen when you login to the PAP), you should be good to go. (Your "Line 2" light would also be on.)

  7. #17
    Join Date
    Apr 2008
    Location
    Aventura Fl
    Posts
    860

    Default Re: Looks Interesting..

    Quote Originally Posted by fisamo View Post
    For the time being, if you wanted to get away from any VTnoc addresses, you could use stun.fwdnet.net:3478 as the stun server (for now--may have to google for public stun servers if FWD doesn't last...), and for DNS, use 4.2.2.2 and 4.2.2.3. I do not know how these changes will impact your VT service, though. Does the voipo line indicate that it's registered with the VTnoc settings for stun and DNS?

    As for the password, the one you entered is still saved--I think Linksys just replaced whatever you type with a set number of *'s. If your line shows Registered, (or Online) on the info screen (first screen when you login to the PAP), you should be good to go. (Your "Line 2" light would also be on.)
    I'm out of steam tonight so I'll check tomorrow. The VPanel shows that my device is not registered. Never got the light to go on..it works ok on line 2 with VT.

    Thanks

    burris

  8. #18
    Join Date
    Mar 2007
    Posts
    190

    Default Re: Looks Interesting..

    Are we going to get the password for the Grandstream or are we for ever locked out ?
    No problem either way, just asking as I now have one.....thanks Tim.

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
  •