Provision Grandstream GXP2170

VitalPBX Community Support General Discussion Provision Grandstream GXP2170

  • Post
    Charlie
    Participant

    I’m having trouble provisioning this phone. I have created a template with the host settings and mapped the device. I’m not using VitalPBX for DHCP so I created a 66 scope option in Windows DHCP Server with the address being: http://[ip address of PBX]/xepm-provision/ The phone still shows as being unregistered though. I’ve been able to register on VitalPBX with Yate Client and connect to one of the extensions I created. I’m pretty new to this so I may very well be missing something obvious.

    Anyone have any ideas?

    0
Viewing 6 replies - 1 through 6 (of 6 total)
  • Replies
    Charlie
    Participant
    Up
    0
    Down

    Edit:

    I also noticed that when I reboot the server some modules don’t seem to be loading. I’m not sure how much of an issue this is?

    [2019-09-04 13:19:42] WARNING[2766] loader.c: Some non-required modules failed to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: Error loading module ‘res_pjsip_phoneprov_provider.so’, missing dependency: res_phoneprov
    [2019-09-04 13:19:42] ERROR[2766] loader.c: Error loading module ‘res_hep_pjsip.so’, missing dependency: res_hep
    [2019-09-04 13:19:42] ERROR[2766] loader.c: res_pjsip_dialog_info_digium_body_supplement declined to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: res_pjsip_transport_websocket declined to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: res_ari declined to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: Declined modules which depend on res_ari: res_ari_events, res_ari_applications, res_ari_endpoints, res_ari_channels, res_ari_sounds, res_ari_playbacks, res_ari_asterisk, res_ari_bridges, res_ari_recordings, res_ari_device_states
    [2019-09-04 13:19:42] ERROR[2766] loader.c: res_pjsip_notify declined to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: app_alarmreceiver declined to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: Failed to resolve dependencies for res_http_media_cache
    [2019-09-04 13:19:42] ERROR[2766] loader.c: res_http_media_cache declined to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: func_odbc declined to load.
    [2019-09-04 13:19:42] ERROR[2766] loader.c: app_festival declined to load.

    0
    Up
    0
    Down

    Did you already configured your EPM with the template and assigned the template to your phone?

    0
    Charlie
    Participant
    Up
    0
    Down

    Yes I can see the phone listed in EPM and I can click the info button to view the XML configuration file.

    0
    Up
    0
    Down

    You may use the whiresark to determinate if the phone is sending the request (option 66) to the server while rebooting.

    0
    Charlie
    Participant
    Up
    0
    Down

    I installed Wireshark on VitalPBX which is running on Centos 7.6. I didn’t see option 66 when I rebooted the phone but I did see a lot of unreachable stuff where it looked like the phone is trying to register but can’t. The IP address 192.168.1.10 is the PBX and 192.168.1.31 is the phone.

    Capturing on ‘eth0’
    1 0.000000000 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    2 1.415536773 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    3 1.999842858 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    4 2.999706868 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    5 7.415894518 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    6 7.999342294 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    7 8.999999016 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    8 17.317335181 Grandstr_fb:d0:ec -> Broadcast ARP 60 Who has 192.168.1.31? Tell 0.0.0.0
    9 20.425314468 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    10 20.999490824 Giga-Byt_3a:5e:81 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.150
    11 21.410689454 Grandstr_fb:d0:ec -> Broadcast ARP 60 Gratuitous ARP for 192.168.1.31 (Request)
    12 21.410999424 Grandstr_fb:d0:ec -> Broadcast ARP 60 Who has 192.168.1.150? Tell 192.168.1.31
    13 21.419491463 Grandstr_fb:d0:ec -> Broadcast ARP 60 Who has 192.168.1.1? Tell 192.168.1.31
    14 23.808770583 Grandstr_fb:d0:ec -> Broadcast ARP 60 Who has 192.168.1.2? Tell 192.168.1.31
    15 23.815192801 Vmware_6b:b2:17 -> Broadcast ARP 60 Who has 192.168.1.31? Tell 192.168.1.2
    16 23.852191648 Grandstr_fb:d0:ec -> Broadcast ARP 60 Who has 192.168.1.1? Tell 192.168.1.31
    17 23.876438804 Grandstr_fb:d0:ec -> Broadcast ARP 60 Who has 192.168.1.10? Tell 192.168.1.31
    18 23.876463571 Vmware_35:f5:f7 -> Grandstr_fb:d0:ec ARP 42 192.168.1.10 is at 00:0c:29:35:f5:f7
    19 23.876964038 192.168.1.31 -> 192.168.1.10 SIP 655 Request: REGISTER sip:192.168.1.10 |
    20 23.877066212 192.168.1.10 -> 192.168.1.31 ICMP 590 Destination unreachable (Port unreachable)
    21 24.363099889 192.168.1.31 -> 192.168.1.10 SIP 655 Request: REGISTER sip:192.168.1.10 |
    22 24.363177622 192.168.1.10 -> 192.168.1.31 ICMP 590 Destination unreachable (Port unreachable)
    23 25.366141936 192.168.1.31 -> 192.168.1.10 SIP 655 Request: REGISTER sip:192.168.1.10 |
    24 25.366259670 192.168.1.10 -> 192.168.1.31 ICMP 590 Destination unreachable (Port unreachable)
    25 28.887076911 Vmware_35:f5:f7 -> Grandstr_fb:d0:ec ARP 42 Who has 192.168.1.31? Tell 192.168.1.10
    26 28.887649722 Grandstr_fb:d0:ec -> Vmware_35:f5:f7 ARP 60 192.168.1.31 is at 00:0b:82:fb:d0:ec
    27 48.401444329 192.168.1.31 -> 192.168.1.10 SIP 656 Request: REGISTER sip:192.168.1.10 |
    28 48.401553116 192.168.1.10 -> 192.168.1.31 ICMP 590 Destination unreachable (Port unreachable)
    29 48.898509653 192.168.1.31 -> 192.168.1.10 SIP 656 Request: REGISTER sip:192.168.1.10 |
    30 48.898608393 192.168.1.10 -> 192.168.1.31 ICMP 590 Destination unreachable (Port unreachable)
    31 49.900129644 192.168.1.31 -> 192.168.1.10 SIP 656 Request: REGISTER sip:192.168.1.10 |
    32 49.900247564 192.168.1.10 -> 192.168.1.31 ICMP 590 Destination unreachable (Port unreachable)
    33 51.902042640 192.168.1.31 -> 192.168.1.10 SIP 656 Request: REGISTER sip:192.168.1.10 |
    34 51.902162926 192.168.1.10 -> 192.168.1.31 ICMP 590 Destination unreachable (Port unreachable)

    0
    Charlie
    Participant
    Up
    0
    Down

    Just an update, I’m able to manually register a Grandstream GXP1630 phone on the PBX but the GXP2170 won’t register using the same settings. I’m not sure why this is. Thanks for all your help mrivera.

    0
Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.