PitzKey

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 237 total)
  • Replies
  • PitzKey
    Participant
    US
    Up
    0
    Down
    That fixed it. Also, it seems like if you don’t have the Multi Tenant add-on installed, it causes issues. Is there a way to install the add-on while it is restoring a multi tenant backup?
    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Also, I see now that it only restored the main and one more tenant. This machine has a valid VitalPBX Carrier license.

    I tried running vitalpbx build-db and vitalpbx fully-dump-conf, it made no difference.

    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Bump?….
    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Bump? Any ETA when this will be available?
    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Following up. Is there a way to make this a bit more friendly to do a daily replication or even every few hours?
    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Diego,

    Please see my comment above that contains the API output. The INTERNAL one is NOT working, the EXTERNAL one DOES work.

    Additionally, as far as I am aware, this was working in a previous version.

    Thanks

    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Hi Diego

    Sorry for not clarifying. This issue is only with internal phonebooks:

    /api/v2/phonebooks/2
    {
        "status": "success",
        "message": null,
        "data": {
            "id": 2,
            "description": "Test Intrernal",
            "source_type": "internal",
            "prefix": null,
            "tenant_id": 1
        }
    }
    /api/v2/phonebooks/2/contacts
    {
        "status": "success",
        "message": null,
        "data": [
            {
                "name": "Test 1",
                "telephone": "6701",
                "mobile_number": "8458881111",
                "home_number": "8459991123",
                "email": null,
                "organization": "ABC 123",
                "job_title": "Job 1",
                "category": "Extensions"
            },
    Now with external:
    /api/v2/phonebooks/3
    {
        "status": "success",
        "message": null,
        "data": {
            "id": 3,
            "description": "Test External",
            "source_type": "external",
            "prefix": null,
            "tenant_id": 1
        }
    }
    /api/v2/phonebooks/3/contacts
    {
        "status": "success",
        "message": null,
        "data": [
            {
                "name": "A Z",
                "telephone": "8451112222",
                "mobile_number": "8452221111",
                "home_number": "8456665555",
                "email": "A.Z@gmail.com",
                "organization": "ABC 987",
                "job_title": "IT GUY",
                "category": "General"
            },
    As you can see, the field is there on both, but with internal phonebooks it shows null.
    Let me know if you need any further info
    Thanks
    0
    PitzKey
    Participant
    US
    Up
    1
    Down
    There’s two things, the SIP auth and the App auth. Eg, with VitXi WebRTC, the user never enters the SIP credentials, they login with whatever username the admin chose.
    1
    PitzKey
    Participant
    US
    Up
    1
    Down
    There are more settings that are different. Eitherway, the login to the WebRTC app should NEVER be the SIP credentials.
    1
    PitzKey
    Participant
    US
    Up
    1
    Down
    As explained earlier, it’s not possible.

    Your end user won’t know that WebRTC is 203_1, as users will just dial 203 and it’ll ring both devices.

    1
    PitzKey
    Participant
    US
    Up
    0
    Down
    Bump?
    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    For now, you can password protect it to avoid this from happening.
    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Polycom is not yet added under the new provisioning. Hopefully soon.
    0
    PitzKey
    Participant
    US
    Up
    1
    Down
    PJSIP and WebRTC uses different transports, it is impossible to have the same settings work for both types of endpoints.

    You need to create another device under that extension, and use each device exclusively with the profile settings suitable for that endpoint.

    1
    PitzKey
    Participant
    US
    Up
    0
    Down
    You have allowed diversions enabled.
    0
Viewing 15 replies - 1 through 15 (of 237 total)