Planet VIP-000 Gateway with Ovislink VOIP-800 firmware

Discussion in '3CX Phone System - General' started by Sycrest, May 15, 2009.

Thread Status:
Not open for further replies.
  1. Sycrest

    Joined:
    May 14, 2009
    Messages:
    1
    Likes Received:
    0
    Good afternoon, everyone.

    I'm new here by the forum, but I used the time to 3CX.
    Now I came across a client who needs a more complete solution, using the analogue line that it owns and also using VOIP providers for output connections.

    The client has 2 gateways Planet VIP-000, which by default only "speak" H.323 (which is not compatible with 3CX).
    To try to take advantage of these VIP-000, found in some forums to use the tip of Ovislink VOIP800 Firmware on Planet, which would enable the SIP protocol to this product. Wonder, until i update apparently worked, because now the setup of the Planet has all the features of SIP, port, IP, etc..

    Now comes the part of the problems.
    With 3CX, added an entry with a PSTN gateway generico, indicating that it has 8 ports, etc. ..
    Then when he brings me the summary of "Virtual Extensions" to be created, suggested I change the numbering for each line, for example:

    Extensions created:

    Virtual Extension | Auth. ID | Auth. Pass. | Identification
    10003 10003 10003 10003

    I change to:
    Virtual Extension | Auth. ID | Auth. Pass. | Identification
    10 10 10 10

    I made these changes in all 8 lines created, 10003 to 10008 for 10 to 17.

    I make this change because there is no gateway in place for more than 2 digits.

    After that, create the settings in the gateway, the extension is on-line in 3CX, see the system status that is gatewy were recorded correctly in the center.

    Problem 1:

    Only the first line of the gateway is registered in the central. The departure of the second line is the error below:

    16:08:31.872 AuthMgr: onAuthFailure [CM101000] Registration request from sip: 11@192.168.1.188 failed. Reason: Credentials do not match, check that authorization-ID and password match the ones in extension settings
    16:08:31.872 AuthMgr: requestCredential [CM001005] SipReq Message: REGISTER 192.168.1.188 tid =- 3a4fcaab-2488-6529 cseq = REGISTER contact = 11@192.168.1.220: 5060 / 4 from (wire) failed authentication!
    16:08:31.872 AuthMgr: requestCredential [CM001002] Authentication ID for CfgExtLine: 11 provided does not match: 10 vs 11

    The error indicates that the User or password is incorrect, but it is impossible, because everything is sequential, type, line 10, password 10, line 11, password 11, and so on. Do not have to be wrong.

    Below is the log of the gateway, indicating that the first line is recorded in 3CX:

    REGISTER sip: 192.168.1.188 SIP/2.0
    From: 10 <sip:10@192.168.1.188>; tag = c0a801dc-13c4-3c56-3a4fcf8b-1ba0aa
    To: <sip:10@192.168.1.188>
    Call-ID: c0a801dc-13c4-1db4-63e7-3a4fc880
    CSeq: 5 REGISTER
    Via: SIP/2.0/UDP 192.168.1.220:5060; branch = z9hG4bK-3a4fcf8b-14d7-1ba0ac
    Max-Forwards: 70
    Contact: <sip:10@192.168.1.220:5060>
    Expires: 900
    Content-Length: 0
    SIP/2.0 407 Proxy Authentication Required
    From: "10" <sip:10@192.168.1.188>; tag = c0a801dc-13c4-3c56-3a4fcf8b-1ba0aa
    To: <sip:10@192.168.1.188>; tag = 18212915
    Call-ID: c0a801dc-13c4-1db4-63e7-3a4fc880
    CSeq: 5 REGISTER
    Via: SIP/2.0/UDP 192.168.1.220:5060; branch = z9hG4bK-3a4fcf8b-14d7-1ba0ac
    Proxy-Authenticate: Digest realm = "3CXPhoneSystem", Nonce = "12886787729: cce28f74af
    ff6c9f13e8c5b626228edc ", algorithm = MD5
    User-Agent: 3CXPhoneSystem
    Content-Length: 0
    <---
    SIP/2.0 200 OK
    From: "10" <sip:10@192.168.1.188>; tag = c0a801dc-13c4-3c56-3a4fcf8b-1ba0aa
    To: <sip:10@192.168.1.188>; tag = 3555a802
    Call-ID: c0a801dc-13c4-1db4-63e7-3a4fc880
    CSeq: 6 REGISTER
    Via: SIP/2.0/UDP 192.168.1.220:5060; branch = z9hG4bK-3a4fcf8c-78ad-1ba306
    Contact: <sip:10@192.168.1.220:5060>; expires = 900
    User-Agent: 3CXPhoneSystem
    Content-Length: 0

    Register SIP phone 10 2 status: SUCCESS

    For the log above, it appears that the gaetway is communicating with 3CX.

    Now the log of the gateway for second-line trying to register in central 3CX:
    <---
    SIP/2.0 403 Invalid password provided
    From: "11" <sip:11@192.168.1.188>; tag = c0a801dc-13c4-203c-7644-3a4fcaaa
    To: <sip:11@192.168.1.188>; tag = 67650236
    Call-ID: c0a801dc-13c4-3a75-3a4fcaa9-1dba
    CSeq: 4 REGISTER
    Via: SIP/2.0/UDP 192.168.1.220:5060; branch = z9hG4bK-3a4fcaab-2488-6529
    User-Agent: 3CXPhoneSystem
    Content-Length: 0

    Register SIP phone 11 0 status: FAILED

    Sorry if Overworked it in the post, but wanted it to be as detailed as possible.

    I appreciate any help!
     
  2. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,913
    Likes Received:
    219
    Hi,

    You should insist that customer uses a supported gateway, it will be much easier. The gateways you mentioned are outdated..... You will spend a lot of time playing around, whilst buying an 8 port FXO is only a few hundred dollars....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.