Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: XLite causes PAP2T to fail re-registration

  1. #1

    Default XLite causes PAP2T to fail re-registration

    I've seen this a couple of times - an incoming call on my VOIPo line, everything rings, none can actually answer successfully (Line 1, Line 2 or XLite) - and then the PAP2T fails to re-register both lines. Seems to be 'mass confusion' going on.

    I searched and could not find any 'current' specifications for setting up XLite.
    Could someone from Voipo post the specific configuration settings necessary - ideally screen shots of the dialogs. Maybe it could even be added to the FAQ so that it's easy to find for those who need/want it.

    I'm reasonably sure that something is askew with the XLite config - which is why I didn't feel it necessary to open a support ticket.

  2. #2

    Default Re: XLite causes PAP2T to fail re-registration

    I took the liberty of doing screen shots of what currently exists on my XLite config - attached.

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

    Default Re: XLite causes PAP2T to fail re-registration

    Try adding a port to your X-Lite registration string that's not in use by the ATA.

    That way when the registration response comes back to your network, it'll be on a different port.

    So it'd be like east01.voipwelcome.com:5062
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  4. #4

    Default Re: XLite causes PAP2T to fail re-registration

    Thanks for the quick response Tim.

    So this would be in the 'DOMAIN' entry that currently shows "EAST01.VOIPWELCOME.COM" - and since 5062/5079 are the current ports for the PAP2, I should use something like 5065 ?

  5. #5

    Default Re: XLite causes PAP2T to fail re-registration

    5065 and 5070 both got time outs/failed to register.

    5060 worked.

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

    Default Re: XLite causes PAP2T to fail re-registration

    Quote Originally Posted by dbmaven View Post
    5065 and 5070 both got time outs/failed to register.

    5060 worked.
    For East01, you can use 5060, 5061, 5062, 5069, or 5079.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  7. #7

    Default Re: XLite causes PAP2T to fail re-registration

    Good info - thanks.

  8. #8
    Join Date
    Dec 2008
    Posts
    200

    Default Re: XLite causes PAP2T to fail re-registration

    Did you get it to work? I think you have to put the local port in "Topology" section in the "Manually specify port range".

    Also, I am not sure if Voipo allows more than 2 lines to register for incoming calls.

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

    Default Re: XLite causes PAP2T to fail re-registration

    Quote Originally Posted by sr98user View Post
    Did you get it to work? I think you have to put the local port in "Topology" section in the "Manually specify port range".

    Also, I am not sure if Voipo allows more than 2 lines to register for incoming calls.
    That may be the case... I'm not personally sure, but will ask one of our support guys to confirm.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

  10. #10

    Default Re: XLite causes PAP2T to fail re-registration

    Same behavior on Port 5061.

    Incoming call rings to all, answered on XLite. PAP2 lines keep ringing (that's annoying...).

    Then both ports on the PAP2 fail to register.

    Reboot the PAP2 leads nowhere - and I can't bounce my network.

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
  •