Solved Fanvil phones can't provision (Yealink is good)

Status
Not open for further replies.

mujin1

Customer
Joined
Dec 3, 2018
Messages
15
Reaction score
6
Hi Everyone, I am having some troubles with the Fanvil phones. I have purchased every model in the X series range to test as I am evaluating 3CX for a Asterisk replacements (with Polycom 335).

I am currently only testing in L2 local subnet directly to the 3CX box. Everytime I assign a "ext" to the phone after the pnp discovery the phones never takes the next step to start the provisioning process.

Version: 2.4.0.5572 (offically supported)
Model: X4G (Tested with all models 3/5/6 but X4 has the logs attached here).
Original Fanvil Template that I am using: https://pastebin.com/1kbrNaJE

The steps I follow:
1. Factory default
2. Upgraded manually to 3CX offical firmware.
3. Using PnP multicast the phone shows up straight away in the GUI.
4. I click on the discovered phone -> assigned ext -> find the extension
5. I make sure the local interface with the phone on the same subnet is set.
6. I select the TZ and select "Enable LLDP" then select "OK"
7. I then select OK
Observed behaviour:
- Nothing happens, phone does not reboot.
- The Phone WebUI -> Autoprivion -> Static Provisioning Server shows the current URL:
# http://10.2.20.2/provisioning/qobhxh9mn5cw/
# Note credential are still default admin/admin
But Protocol type is still set as FTP, Update Model "Disabled"
- 3CX logo is on the startup screen.
- Check MAC.cfg for any errors in the xml but non where found.
Debug syslog capture:
Code:
Dec  7 18:42:51 10.2.20.12 [MGR]  | INFO   | save conf write ok
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 2 bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating NIST context
Dec  7 18:44:56 10.2.20.12 [SIP]  | WARNING| nist_notify_received().
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE |  the sip message from tag is  4840ed55
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the dialog local tag is 1606116065
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the sip message callid is bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the local dialog callid is 5758378527459-3353058813195
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the dialog status is 0
Dec  7 18:44:56 10.2.20.12 [MGR]  | INFO   | save conf write ok
Dec  7 18:44:56 10.2.20.12 [SIP]  | WARNING| ua_transaction_execute: could not get dialog transaction.
Dec  7 18:44:56 10.2.20.12 [SIP]  | WARNING| Transaction 2 killed.
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | free transaction ressource 2 bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | free nist ressource
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 3 bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating NIST context


--------------------------
Attempted number two
1. Factory reset
2. Phone is visable again in the 3CX UI
3. Assigned different user
4. Phone does nothing.
--------------------------
Code:
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 2 VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating NIST context
Dec  7 19:03:02 10.2.20.12 [SIP]  | WARNING| nist_notify_received().
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE |  the sip message from tag is  31b9a53b
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the dialog local tag is 1606116065
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the sip message callid is VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the local dialog callid is 5758378527459-3353058813195
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the dialog status is 0
Dec  7 19:03:02 10.2.20.12 [MGR]  | INFO   | save conf write ok
Dec  7 19:03:02 10.2.20.12 [SIP]  | WARNING| ua_transaction_execute: could not get dialog transaction.
Dec  7 19:03:02 10.2.20.12 [SIP]  | WARNING| Transaction 2 killed.
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | free transaction ressource 2 VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | free nist ressource
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 3 VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating NIST context
--------------------------
5. Log into to the WebUI I can see the provision URL is set but only that.

Addational Notes:
- Yealink phones work like magic using PnP extension assignment (tested with 3x different models)
- Legacy Polycom Soundpoint 335 work perfectly using option 66 in DHCP.
- Template is not modified (https://pastebin.com/1kbrNaJE)

I have also uploaded the mac.cfg and a tcpdump which run from the 3CX box monitoring the IP of the phone.

Any suggestions would be greatly appreciated. Seems to be really a brand specific issue for me.

Thanks.
 

Attachments

Hi Everyone, I am having some troubles with the Fanvil phones. I have purchased every model in the X series range to test as I am evaluating 3CX for a Asterisk replacements (with Polycom 335).

I am currently only testing in L2 local subnet directly to the 3CX box. Everytime I assign a "ext" to the phone after the pnp discovery the phones never takes the next step to start the provisioning process.

Version: 2.4.0.5572 (offically supported)
Model: X4G (Tested with all models 3/5/6 but X4 has the logs attached here).
Original Fanvil Template that I am using: https://pastebin.com/1kbrNaJE

The steps I follow:
1. Factory default
2. Upgraded manually to 3CX offical firmware.
3. Using PnP multicast the phone shows up straight away in the GUI.
4. I click on the discovered phone -> assigned ext -> find the extension
5. I make sure the local interface with the phone on the same subnet is set.
6. I select the TZ and select "Enable LLDP" then select "OK"
7. I then select OK
Observed behaviour:
- Nothing happens, phone does not reboot.
- The Phone WebUI -> Autoprivion -> Static Provisioning Server shows the current URL:
# http://10.2.20.2/provisioning/qobhxh9mn5cw/
# Note credential are still default admin/admin
But Protocol type is still set as FTP, Update Model "Disabled"
- 3CX logo is on the startup screen.
- Check MAC.cfg for any errors in the xml but non where found.
Debug syslog capture:
Code:
Dec  7 18:42:51 10.2.20.12 [MGR]  | INFO   | save conf write ok
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 2 bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating NIST context
Dec  7 18:44:56 10.2.20.12 [SIP]  | WARNING| nist_notify_received().
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE |  the sip message from tag is  4840ed55
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the dialog local tag is 1606116065
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the sip message callid is bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the local dialog callid is 5758378527459-3353058813195
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | the dialog status is 0
Dec  7 18:44:56 10.2.20.12 [MGR]  | INFO   | save conf write ok
Dec  7 18:44:56 10.2.20.12 [SIP]  | WARNING| ua_transaction_execute: could not get dialog transaction.
Dec  7 18:44:56 10.2.20.12 [SIP]  | WARNING| Transaction 2 killed.
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | free transaction ressource 2 bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | free nist ressource
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 3 bjKCfeiOhxCbVogazA7XvA..
Dec  7 18:44:56 10.2.20.12 [SIP]  | NOTICE | allocating NIST context


--------------------------
Attempted number two
1. Factory reset
2. Phone is visable again in the 3CX UI
3. Assigned different user
4. Phone does nothing.
--------------------------
Code:
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 2 VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating NIST context
Dec  7 19:03:02 10.2.20.12 [SIP]  | WARNING| nist_notify_received().
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE |  the sip message from tag is  31b9a53b
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the dialog local tag is 1606116065
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the sip message callid is VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the local dialog callid is 5758378527459-3353058813195
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | the dialog status is 0
Dec  7 19:03:02 10.2.20.12 [MGR]  | INFO   | save conf write ok
Dec  7 19:03:02 10.2.20.12 [SIP]  | WARNING| ua_transaction_execute: could not get dialog transaction.
Dec  7 19:03:02 10.2.20.12 [SIP]  | WARNING| Transaction 2 killed.
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | free transaction ressource 2 VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | free nist ressource
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating transaction ressource 3 VDoZ1kyQsBFXSUkw4ojUrw..
Dec  7 19:03:02 10.2.20.12 [SIP]  | NOTICE | allocating NIST context
--------------------------
5. Log into to the WebUI I can see the provision URL is set but only that.

Addational Notes:
- Yealink phones work like magic using PnP extension assignment (tested with 3x different models)
- Legacy Polycom Soundpoint 335 work perfectly using option 66 in DHCP.
- Template is not modified (https://pastebin.com/1kbrNaJE)

I have also uploaded the mac.cfg and a tcpdump which run from the 3CX box monitoring the IP of the phone.

Any suggestions would be greatly appreciated. Seems to be really a brand specific issue for me.

Thanks.
Hi,
Do you have an option 66 configured for that IP address? If so, remove it.

Try to manually download the config from the PBX. According to your example, you can use the following link:
http://10.2.20.2/provisioning/qobhxh9mn5cw/0c383e1d562c.cfg

If it works and if it's in correct format - the file generation part is okay.

Now let's check the provisioning:
1. Factory reset the phone
2. go to the Phones page and find the PnP message
3. before assign it to extension, start the network capture on PBX and on the phone
4. when both captures are started, assign it to extension.
5. wait for 5-10 seconds and stop the captures, open them and investigate

You should see:
a) SIP Notify message (with the provisioning URL in the Message Body) sent from PBX
b) That message you should see in the phone's capture too - means that the phone was able to receive it and reply with 200 OK.
c) HTTP request (for the config and phone-book files) sent from the phone and received on the PBX side
d) 200 OK for these http requests sent from the PBX and received on the phone's side
e) TCP traffic from the phone will indicate that was downloading something.

Do you see this everything in the captures?
 
Ok I found the issue. There is an issue in the current firmware from Fanvil that is supported by 3CX.
I upgraded to the latest and provisioning worked straight away.

X4-2.8.1.6305 on 2018-12-07
Bug Fixes
- Fix the issue of Push Configuration XML (Maybe this?)
http://fanvil.com/Uploads/Temp/download/20181207/5c09da2d95398.pdf

It seems all models in the "X" series had a new firmware released on last Friday.

I will test with the other mode
 
Thank-you for posting up the solution, I am not a user of Fanvil, but can say personally I have never experienced such an issue with Yealink regardless of the firmware version.
 
Status
Not open for further replies.

Forum statistics

Threads
111,835
Messages
589,289
Members
164,668
Latest member
Infinity Network