Yealink Firmware versions

Discussion in '3CX Phone System - General' started by greg@summitrad, Jun 30, 2015.

Thread Status:
Not open for further replies.
  1. greg@summitrad

    Joined:
    Aug 15, 2014
    Messages:
    27
    Likes Received:
    0
    Good Morning,

    We use exclusively Yealink phones. We have a few T38G and T41G, but the vast majority (95%) are all T46G phones. Formerly, you had to stick with the 3CX certified Firmware (28.71.0.224). Now, the instructions say to use the most current firmware.

    "http://www.3cx.com/sip-phones/yealink-t32g-t38g-t42g-t46g/"

    So is it now OK to use the most current firmware? I've tried a few times to use a more recent firmware and the provisioning generally fails after that.

    I received a new phone with the most recent firmware on it, and it would not provision. It just leased an address and sat there. I spun up an older phone (still in the box) that came with 28.71.0.224 and voila.. it worked right away (picked up the provisioning template and went to town. (Riding on a pony and eating macaroni... well, it is almost the 4th here in the states. Time for booze and idiots with explosives. Sorry, got off track!)

    Anyone have any input on the firmware issue?

    Greg
     
  2. complex1

    complex1 Active Member

    Joined:
    Jan 25, 2010
    Messages:
    752
    Likes Received:
    38
    I use several T28P with the latest firmware and they provisioning fine.

    Did you upgrade the phone firmware through 3CX?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. greg@summitrad

    Joined:
    Aug 15, 2014
    Messages:
    27
    Likes Received:
    0
    When I wanted to test upgraded firmware in the past, I upgraded a phone locally (through it's management interface). I didn't want to have someone else get into the interface and accidentally on-purpose upgrade the rest of them if there were issues.

    This time, there was no upgrading. The one phone already had the old version and the other already had the newest.

    Greg
     
  4. Thomas 3CX

    3CX Support

    Joined:
    May 6, 2015
    Messages:
    15
    Likes Received:
    0
    Hello,

    I would like to inform you about the current supported firmware for the IP Phones mentioned above:

    • T38 > 38.70.0.221
    • T41 > 36.73.0.45
    • T46 > 28.73.0.48

    Please upgrade to the above firmware versions (per model) and update us with the results.

    Thanks.
     
  5. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    Hi,

    I have a similar case here.
    I updated the firmware to V73 on my T46 and it looks like reprovisioning isn't working.
    I can start autoprovisioning via the Web-Interface of the phone but not the 3cx interface.
    We did set autoprovision on reboot = disabled via the provisioning tempalte ofr all our phones. This was really importat to us, as people didn't liked their changes getting lost on reprovisioning.

    If we manually reenable provisioning on reboot it works fine, of course. It would be hell of a work ot manually log into all our 250 phones and set "provisioning on reboot = enabeled" as we cannont reprovision at the moment.

    When the telephone reboots while reprovisioning (while "autoprovision on reboot" being disabled) we get a "sending provisioning request" screen for a long time and than a "skipped upadate, zero touch". Enabling and disabling zero touch doesn't change anything and and provisioning via the phone interface works fine, so all the general provisioning settings seems to be working

    I am a littel lost on this one.

    Best regards Frank
     
  6. jasit

    jasit New Member

    Joined:
    Feb 12, 2013
    Messages:
    169
    Likes Received:
    1
    edit your template file, and force which version you want, when the phones reprovision they will pull the file.

    search for the configure the access URL section of your template

    #######################################################################################
    ## Configure the access URL of firmware ##
    #######################################################################################
    #Before using this parameter, you should store the desired firmware (x.71.x.x.rom) to the provisioning server.

    {IF network=LOCALLAN}
    firmware.url = http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/firmware/t46/28.73.0.48.rom
    {ENDIF}
     
  7. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    Hey jasit,

    thanks for your answer. I don't know, if editing the provisioning template will change much at the moment. Maybe I didn't understand your comment, or didn't articulate my situation. All the phones already use a template with "autoprovision = disabled" and the new firmware. And the provisioning-URL it is pulling looks nice. It works fine, when we manually log into the phone and start the reprovisioning, but it is not reprovisioning on remote request initiated via the 3cx admin panel. As far as I know both procedures are supposed to use the same URL, or aren't they? If they are not, this would explain the behaviour.

    best regards Frank
     
  8. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    I once again read the auto-provisioning manual and can articualte our situation more precisely:

    We recently updated our Yealink T46G phones to the V73 firmware.
    We edited the provisioning template and
    • disabled autoprovison on power on: auto_privion.mode = 0
      disabled repeated auto_provion: auto_provision.repeat.enable = 0

    We can still use "Autoprovision Now" via the webinterface of the phone.
    When we use the "Provision" funktion of the 3cx Admin panel, the phone will reboot, but won't provision. No changes will take effect. It will reprovision, if autoprovision on power on is enabled, which is quite obvious, as the phone can be rebooted via the 3cx inteface.
    So it looks like, the Sip-Notify Message “Event:check-sync”isn't working, but the “reboot=true” doesn t. Autoprovision on reboot doesn't have to be enabled in order to the Sip-Notify thing to work, does it?

    So at the moment we have no other way to reprovision the phones, than to manually log into each phones web-interface.

    I am not sure if this is related to the V73 firmware, or not. I will have to do some more testing. I will post some log files of the phone, while sending it a provisioning request and while "Provision Now".

    Best regards Frank


    ## Auto Provisioning ##
    #######################################################################################
    #Enable or disable the Plug and Play feature; 0-Disabled, 1-Enabled (default);
    auto_provision.pnp_enable = 1

    #Configure the auto provision mode;
    #0-Disabled (default), 1-Power on;
    auto_provision.mode = 0

    #Enable or disable the phone to check the new configuration weekly; 0-Disabled (default), 1-Enabled;
    auto_provision.repeat.enable = 0

    #Configure the interval (in minutes) for the phone to check new configuration files. It ranges from 1 to 43200, the default value is 1440.
    #It is only applicable to "Repeatedly" and "Power on + Repeatedly" modes.
    #auto_provision.schedule.periodic_minute =
    auto_provision.repeat.minutes = 1440

    auto_provision.weekly.enable = 0
    #Configure the start time of the day for the phone to check new configuration files. The default value is 00:00.
    #It is only applicable to "Weekly" and "Power on + Weekly" modes.
    #If the desired start time of the day is seven forty-five a.m., the value format is 07:45.
    auto_provision.weekly.begin_time = 00:00


    #Configure the end time of the day for the phone to check new configuration files. The default time is 00:00.
    #It is only applicable to "Weekly" and "Power on + Weekly" modes.
    #If the desired end time of the day is seven forty-five p.m., the value format is 19:45.
    auto_provision.weekly.end_time = 00:00



    #Configure the day of week for the phone to check new configuration files. The default vaule is 0123456.
    #0-Sunday,1-Monday,2-Tuesday,3-Wednesday,4-Thursday,5-Friday,6-Saturday;
    #It is only applicable to "Weekly" and "Power on + Weekly" modes.
    #If the desired week is Monday, Tuesday and Wednesday, the value format is 012.
    auto_provision.weekly.mask = 0123456


    #Configure the URL of the auto provisioning server.
    {if network=LOCALLAN}
    auto_provision.server.url = http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/%%PROVSUBDIR%%/
    auto_provision.server.username =
    auto_provision.server.password =
    {ENDIF}

    {IF network=REMOTESTUN}
    auto_provision.server.username =
    auto_provision.server.password =
    auto_provision.server.url = http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/%%PROVSUBDIR%%/
    {ENDIF}

    {IF network=REMOTESPM}
    auto_provision.server.url = http://%%param::pBXPUBLICIP%%:%%pbx_http_port%%/provisioning/%%PROVSUBDIR%%/
    auto_provision.server.username =
    auto_provision.server.password =
    {ENDIF}

    {IF network=SBC}
    auto_provision.server.url = http://%%param::pBXPUBLICIP%%:%%pbx_http_port%%/provisioning/%%PROVSUBDIR%%/
    auto_provision.server.username =
    auto_provision.server.password =
    {ENDIF}

    #Configure the name of the common file.
    #T46G: y000000000028.cfg; T48G: y000000000035.cfg;
    {IF ua=SIP-T46G}
    auto_provision.common_file_name = y000000000028.cfg
    {ENDIF}

    {IF ua=SIP-T48G}
    auto_provision.common_file_name = y000000000035.cfg
    {ENDIF}

    #Enable or disable DHCP option mode; 0-Disabled, 1-Enabled (default);
    auto_provision.dhcp_option.enable =

    #Configure the value (manufacturer of the device) of DHCP option 60.
    auto_provision.dhcp_option.option60_value =

    #Configure the custom DHCP option number. It ranges from 128 to 254.
    auto_provision.dhcp_option.list_user_options =

    #Configure AES key (16 characters) for decrypting the common CFG file.
    auto_provision.aes_key_16.com =

    #Configure AES key (16 characters) for decrypting the MAC-Oriented CFG file.
    auto_provision.aes_key_16.mac =

    custom_mac_cfg.url =
     
  9. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    Hier sind die Logs vom dem nicht-erfolgreichen "Sip-Notify-Provisioning" Versuch

    zunächst ein meiner Meinung interessanter Auszung, unten der vollständige Log:
    Jul 9 11:45:33 LIBD[591]: DCMN<3+error > Connect Failed! ret 0, errno 115 timeout 10 error -1
    Jul 9 11:45:33 LIBD[591]: HTTP<3+error > Connect Error
    Jul 9 11:45:47 LIBD[591]: DCMN<3+error > Connect Failed! ret 0, errno 115 timeout 10 error -1
    Jul 9 11:45:47 LIBD[591]: HTTP<3+error > Connect Error
    Jul 9 11:46:00 LIBD[591]: DCMN<3+error > Connect Failed! ret 0, errno 115 timeout 10 error -1
    Jul 9 11:46:00 LIBD[591]: HTTP<3+error > Connect Error
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response code: 404
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:46:04 LIBD[445]: HTTP<3+error > Client error
    Jul 9 11:46:04 ATP [445]: ATP <3+error > http to file failed, code = 404, msg = Unknown Error, retry = 1
    Jul 9 11:46:04 ATP [445]: ATP <4+warnin> Download com.cfg fail
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response code: 404
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:46:04 LIBD[445]: HTTP<3+error > Client error
    Jul 9 11:46:04 ATP [445]: ATP <3+error > http to file failed, code = 404, msg = Unknown Error, retry = 1
    Jul 9 11:46:04 ATP [445]: ATP <4+warnin> Download mac.cfg fail


    vollständig:

    Jul 9 11:45:01 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 52 s....
    Jul 9 11:45:01 ATP [445]: ANY <0+emerg > ATP log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:01 ATP [445]: ANY <0+emerg > ANY =5
    Jul 9 11:45:01 LIBD[445]: DANY<0+emerg > LIBD log :sys=1,cons=0,time=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:02 LIBD[445]: DANY<0+emerg > LIBD log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:02 LIBD[445]: DANY<0+emerg > DANY=5
    Jul 9 11:45:02 GUI [494]: ANY <0+emerg >GUI log :sys=1,cons=0,time=0,sock=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:02 GUI [494]: ANY <0+emerg >ANY =4
    Jul 9 11:45:02 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 51 s....
    Jul 9 11:45:03 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 50 s....
    Jul 9 11:45:04 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 49 s....
    Jul 9 11:45:05 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 48 s....
    Jul 9 11:45:06 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 47 s....
    Jul 9 11:45:07 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 46 s....
    Jul 9 11:45:08 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 45 s....
    Jul 9 11:45:09 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 44 s....
    Jul 9 11:45:10 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 43 s....
    Jul 9 11:45:11 ipp [617]: IIPP<5+notice> OPEN_HEADSET_MODE,00000001 00000000
    Jul 9 11:45:11 ipp [617]: IIPP<5+notice> SET_VOLUNE,00000001 00000000
    Jul 9 11:45:11 ipp [617]: IIPP<5+notice> PLAY_LOCAL_DTMF,00000000 00000001
    Jul 9 11:45:11 LIBD[591]: DANY<0+emerg > LIBD log :sys=1,cons=0,time=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:11 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 42 s....
    Jul 9 11:45:11 ipp [617]: IIPP<5+notice> OPEN_HANDSET_MODE,00000001 00000000
    Jul 9 11:45:12 LIBD[591]: DANY<0+emerg > LIBD log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:12 LIBD[591]: DANY<0+emerg > DANY=5
    Jul 9 11:45:12 ipp [617]: IIPP<5+notice> OPEN_HANDFREE_MODE,00000001 00000000
    Jul 9 11:45:12 ipp [617]: IIPP<5+notice> SET_VOLUNE,00000001 00000008
    Jul 9 11:45:12 ipp [617]: IIPP<5+notice> TALK_START,fffffffe 00070000
    Jul 9 11:45:12 ipp [617]: IIPP<5+notice> OPEN_HANDSET_MODE,00000001 00000000
    Jul 9 11:45:13 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 41 s....
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > LDAP log :sys=1,cons=0,time=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > ANY =3
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > MEM =3
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > LDAP =3
    Jul 9 11:45:13 LDAP[591]: LDAP<3+error > Init config! libldap Ver:3.2.0.3
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > LDAP log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > ANY =5
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > MEM =5
    Jul 9 11:45:13 LDAP[591]: ANY <0+emerg > LDAP =5
    Jul 9 11:45:13 LIBD[591]: HTTP<5+notice> response code: 200
    Jul 9 11:45:13 LIBD[591]: HTTP<5+notice> response process finish!
    Jul 9 11:45:13 LIBD[591]: HTTP<5+notice> recv : 55757 bytes
    Jul 9 11:45:14 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 40 s....
    Jul 9 11:45:15 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 39 s....
    Jul 9 11:45:16 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 38 s....
    Jul 9 11:45:17 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 37 s....
    Jul 9 11:45:18 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 36 s....
    Jul 9 11:45:18 GUI [591]: CUIT<3+error >318.374.389:Create dongle failed
    Jul 9 11:45:19 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 35 s....
    Jul 9 11:45:19 GUI [591]: DKUI<3+error >319.956.520:DssKeyPanel == NULL
    Jul 9 11:45:19 GUI [591]: DKUI<3+error >319.962.331:DssKeyPanel == NULL
    Jul 9 11:45:19 GUI [591]: DKUI<3+error >319.981.286:DssKeyPanel == NULL
    Jul 9 11:45:20 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 34 s....
    Jul 9 11:45:21 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 33 s....
    Jul 9 11:45:22 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 32 s....
    Jul 9 11:45:23 SIP [637]: SIP <5+notice> [SIP] wait for ui thread sync, max wait for 31 s....
    Jul 9 11:45:23 GUI [591]: DSSK<4+warnin>323.467.020:pKeys == NULL
    Jul 9 11:45:23 SIP [637]: SIP <5+notice> [SIP] ui thread is up and can handle message, sip begin to run....
    Jul 9 11:45:23 SIP [637]: SIP <5+notice> [SIP] ** Load phone context **
    Jul 9 11:45:23 SIP [637]: SIP <5+notice> [SIP] ** Load OK **
    Jul 9 11:45:23 SIP [637]: ANY <0+emerg > ANY =5
    Jul 9 11:45:23 SIP [637]: SIP <5+notice> [SIP] Message sent: [(PHONE_MSG_BLA_STATUS_UPDATE) -- (0xa001e) wParam(0x0)-lParam(0x0)]
    Jul 9 11:45:23 SIP [637]: SIP <5+notice> [SIP] ** SIPUA Loading Account BEGIN **
    Jul 9 11:45:23 SIP [637]: SDL <5+notice> [016] set http_outbound_proxy:127.0.0.1 5060!
    Jul 9 11:45:23 SIP [637]: SUA <5+notice> [016] reg status changed to [(LS_REGISTERING) -- (1)], reason=[NULL]
    Jul 9 11:45:24 SIP [637]: SUA <5+notice> [016] Listening on socket: (5060)
    Jul 9 11:45:24 SIP [637]: SDL <5+notice> [016] set http_outbound_proxy:!
    Jul 9 11:45:24 SIP [637]: SDL <5+notice> [000] set http_outbound_proxy:192.168.16.2 5060!
    Jul 9 11:45:24 SIP [637]: SUA <5+notice> [000] reg status changed to [(LS_REGISTERING) -- (1)], reason=[NULL]
    Jul 9 11:45:24 SIP [637]: SUA <5+notice> [000] Listening on socket: (5062)
    Jul 9 11:45:24 SIP [637]: SUA <5+notice> [000] reg acc:"Ulrike Burger"<sip:358@192.168.16.2>
    Jul 9 11:45:25 SIP [637]: SIP <5+notice> [SIP] ** SIPUA Account Loaded END **!
    Jul 9 11:45:25 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x00010007] wParam:(0x0002),lParam:(0x0000) BROAD_MSG_CONFIG_CHANGE
    Jul 9 11:45:25 SIP [637]: SIP <5+notice> [SIP] ** Reload phone context **
    Jul 9 11:45:25 SIP [637]: SIP <5+notice> [SIP] ** Load OK **
    Jul 9 11:45:25 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x00010007] wParam:(0x000a),lParam:(0x0000) BROAD_MSG_CONFIG_CHANGE
    Jul 9 11:45:25 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x0004000e] wParam:(0x0000),lParam:(0x0000) SIP_MSG_QUERY_BLF_STATUS
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:25 SIP [637]: SUA <5+notice> [000] reg expire updated to (120)
    Jul 9 11:45:25 SIP [637]: SUA <5+notice> [000] reg status changed to [(LS_REGISTERED) -- (2)], reason=[NULL]
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:25 SIP [637]: SUA <5+notice> [000] MWI Messages-Waiting: no
    Jul 9 11:45:25 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_NEW_VOICE_MESSAGE) -- (0xa000f) wParam(0x0)-lParam(0x0)]
    Jul 9 11:45:25 SIP [637]: SUA <5+notice> [000] Normal: New (0), Old (0), Urgent: New 0, old 0
    Jul 9 11:45:25 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x0004000e] wParam:(0x0000),lParam:(0x0000) SIP_MSG_QUERY_BLF_STATUS
    Jul 9 11:45:26 SIP [637]: SIP <5+notice> max_key_count:30, current_sub_idx:0
    Jul 9 11:45:26 SIP [637]: SIP <5+notice> no sub now
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] BLF SUB fail
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] dialog local target name:558
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] dialog state:0
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] BLF uri:sip:558@192.168.16.2 status:0
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] key 2: status change to 0
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] key: [2] line: [0] call: [0] <-> 558 status: [0]
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:45:26 SIP [637]: SIP <5+notice> max_key_count:30, current_sub_idx:3
    Jul 9 11:45:26 SIP [637]: SIP <5+notice> no sub now
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] BLF SUB fail
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:26 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] dialog local target name:258
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] dialog state:0
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] BLF uri:sip:258@192.168.16.2 status:0
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] key 3: status change to 0
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] key: [3] line: [0] call: [0] <-> 258 status: [0]
    Jul 9 11:45:26 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:45:27 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x0004000e] wParam:(0x0000),lParam:(0x0000) SIP_MSG_QUERY_BLF_STATUS
    Jul 9 11:45:27 SIP [637]: SIP <5+notice> max_key_count:30, current_sub_idx:4
    Jul 9 11:45:27 SIP [637]: SIP <5+notice> no sub now
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] BLF SUB fail
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] dialog local target name:280
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] dialog state:0
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] BLF uri:sip:280@192.168.16.2 status:0
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] key 4: status change to 0
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [0] <-> 280 status: [0]
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:45:27 SIP [637]: SIP <5+notice> max_key_count:30, current_sub_idx:5
    Jul 9 11:45:27 SIP [637]: SIP <5+notice> no sub now
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:27 SIP [637]: SUA <5+notice> [000] BLF SUB fail
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:27 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] dialog local target name:421
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] dialog state:0
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] BLF uri:sip:421@192.168.16.2 status:0
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] key 6: status change to 0
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] key: [6] line: [0] call: [0] <-> 421 status: [0]
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:45:28 SIP [637]: SIP <5+notice> max_key_count:30, current_sub_idx:7
    Jul 9 11:45:28 SIP [637]: SIP <5+notice> no sub now
    Jul 9 11:45:28 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] BLF SUB fail
    Jul 9 11:45:28 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:45:28 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:28 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] dialog local target name:453
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] dialog state:0
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] BLF uri:sip:453@192.168.16.2 status:0
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] key 7: status change to 0
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] key 12: status change to 0
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] key: [12] line: [0] call: [0] <-> 453 status: [0]
    Jul 9 11:45:28 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:45:28 SIP [637]: SIP <5+notice> max_key_count:30, current_sub_idx:13
    Jul 9 11:45:33 LIBD[591]: DCMN<3+error > Connect Failed! ret 0, errno 115 timeout 10 error -1
    Jul 9 11:45:33 LIBD[591]: HTTP<3+error > Connect Error
    Jul 9 11:45:47 LIBD[591]: DCMN<3+error > Connect Failed! ret 0, errno 115 timeout 10 error -1
    Jul 9 11:45:47 LIBD[591]: HTTP<3+error > Connect Error
    Jul 9 11:46:00 LIBD[591]: DCMN<3+error > Connect Failed! ret 0, errno 115 timeout 10 error -1
    Jul 9 11:46:00 LIBD[591]: HTTP<3+error > Connect Error
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response code: 404
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:46:04 LIBD[445]: HTTP<3+error > Client error
    Jul 9 11:46:04 ATP [445]: ATP <3+error > http to file failed, code = 404, msg = Unknown Error, retry = 1
    Jul 9 11:46:04 ATP [445]: ATP <4+warnin> Download com.cfg fail
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response code: 404
    Jul 9 11:46:04 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:46:04 LIBD[445]: HTTP<3+error > Client error
    Jul 9 11:46:04 ATP [445]: ATP <3+error > http to file failed, code = 404, msg = Unknown Error, retry = 1
    Jul 9 11:46:04 ATP [445]: ATP <4+warnin> Download mac.cfg fail
    Jul 9 11:46:24 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:46:24 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:46:24 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:46:24 SIP [637]: SUA <5+notice> [000] reg expire updated to (120)
    eth0 Link encap:Ethernet HWaddr 00:15:65:50:CE:A7
    inet6 addr: fe80::215:65ff:fe50:cea7/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1233 errors:0 dropped:0 overruns:0 frame:0
    TX packets:321 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1024
    RX bytes:195396 (190.8 KiB) TX bytes:159413 (155.6 KiB)
    Interrupt:8

    eth0.15 Link encap:Ethernet HWaddr 00:15:65:50:CE:A7
    inet addr:192.168.16.155 Bcast:192.168.23.255 Mask:255.255.248.0
    inet6 addr: fe80::215:65ff:fe50:cea7/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:543 errors:0 dropped:0 overruns:0 frame:0
    TX packets:311 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:136802 (133.5 KiB) TX bytes:156613 (152.9 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    PID USER VSZ STAT COMMAND
    1 root 2064 S init
    2 root 0 SW< [kthreadd]
    3 root 0 SW< [ksoftirqd/0]
    4 root 0 SW< [events/0]
    5 root 0 SW< [khelper]
    6 root 0 SW [bcmring_ddrvpmp]
    7 root 0 SW [knllog]
    8 root 0 SW< [kblockd/0]
    9 root 0 SW [perfpoll]
    10 root 0 SW< [hosticp]
    11 root 0 SW< [khubd]
    12 root 0 SW< [bluetooth]
    13 root 0 SW [pdflush]
    14 root 0 SW [pdflush]
    15 root 0 SW< [kswapd0]
    16 root 0 SW< [aio/0]
    17 root 0 SW< [nfsiod]
    18 root 0 SW [crypto]
    19 root 0 SW [crypto_ret]
    20 root 0 SW< [vpm_power_queue]
    21 root 0 SW< [mtdblockd]
    22 root 0 SW< []
    23 root 0 SW< [krfcommd]
    24 root 0 SW< [rpciod/0]
    64 root 1716 S < /sbin/udevd --daemon
    90 root 1712 S < /sbin/udevd --daemon
    91 root 1712 S < /sbin/udevd --daemon
    97 root 2064 S init
    104 root 0 SW< [kled]
    110 root 0 SW [expd]
    122 root 0 SW< [yaffs-bg-1]
    124 root 0 SW< [yaffs-bg-1]
    209 root 0 SW< [ethTx/0]
    210 root 0 SW< [ethStatus/0]
    217 root 9040 S /boot/bin/configServer.exx
    418 root 2772 S dbus-daemon --config-file=/config/bluetooth/dbus-1/sy
    424 root 2064 S /bin/sh /phone/scripts/netapp.sh
    432 root 32728 S /boot/bin/rtServer.exx
    445 root 25160 S /boot/bin/autoServer.exx
    452 root 4316 S bluetoothd
    493 root 3444 S ./sbin/lighttpd -f /phone/bin/lighttpd/config/lighttp
    494 root 17924 S /phone/www/WEB-INFO/bin/fcgiServer.exx
    521 root 2064 S /sbin/syslogd -S -O /tmp/log/00156550cea7.log -s 200
    524 root 2064 S /bin/sh /phone/scripts/phoneapp.sh
    591 root 170m S /phone/bin/dskPhone.exx -qws
    597 root 0 DW [hwthread]
    599 root 0 DW [hausioctl]
    600 root 0 SW< [frameProfiler]
    602 root 0 DW< [kvoice]
    603 root 0 DW< [Cadence]
    617 root 24384 S /phone/bin/vaServer
    623 root 2064 S /bin/sh /phone/scripts/sipapp.sh
    627 root 2064 S /bin/sh /phone/scripts/TR069.sh
    637 root 42304 S /phone/bin/sipServer.exx
    657 root 24976 S /phone/bin/tr069_client
    671 root 1628 S /phone/bin/busybox udhcpc -b -i eth0.15 -a -s /boot/b
    697 root 2064 S sh -c cd /tmp;ifconfig >> log/00156550cea7.log;ps >>
    699 root 2388 R ps
     
  10. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    und der Abschnitt der Yealink Logs von dem erfolgreichen "Autoprovision Now" Versuch:

    Jul 9 11:47:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:47:25 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:47:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:47:25 SIP [637]: SUA <5+notice> [000] reg expire updated to (120)
    Jul 9 11:47:57 LIBD[445]: HTTP<5+notice> response code: 404
    Jul 9 11:47:57 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:47:57 LIBD[445]: HTTP<3+error > Client error
    Jul 9 11:47:57 ATP [445]: ATP <3+error > http to file failed, code = 404, msg = Unknown Error, retry = 1
    Jul 9 11:47:57 ATP [445]: ATP <4+warnin> Download com.cfg fail
    Jul 9 11:47:57 LIBD[445]: HTTP<5+notice> response code: 404
    Jul 9 11:47:57 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:47:57 LIBD[445]: HTTP<3+error > Client error
    Jul 9 11:47:57 ATP [445]: ATP <3+error > http to file failed, code = 404, msg = Unknown Error, retry = 1
    Jul 9 11:47:57 ATP [445]: ATP <4+warnin> Download mac.cfg fail
    Jul 9 11:47:57 LIBD[445]: HTTP<5+notice> response code: 200
    Jul 9 11:47:57 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:47:57 LIBD[445]: HTTP<5+notice> recv : 16375 bytes
    Jul 9 11:47:58 LIBD[445]: HTTP<5+notice> response code: 200
    Jul 9 11:47:58 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:47:58 LIBD[445]: HTTP<5+notice> recv : 69169 bytes
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: features.history_save_display
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: DITF-change phone_setting.backgrounds
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: screen_saver.pic.url
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: linekey.3.extension
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: linekey.4.extension
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: linekey.5.extension
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: linekey.7.extension
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: linekey.8.extension
    Jul 9 11:47:58 ATP [445]: ATP <4+warnin> error: linekey.13.extension
    Jul 9 11:48:00 LIBD[445]: HTTP<5+notice> response code: 200
    Jul 9 11:48:00 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:48:00 LIBD[445]: HTTP<5+notice> recv : 24681 bytes
    Jul 9 11:48:03 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x00010007] wParam:(0x005a),lParam:(0x0000) BROAD_MSG_CONFIG_CHANGE
    Jul 9 11:48:03 ATP [445]: ATP <4+warnin> AUTOP: Upgrade rom from url starts!
    Jul 9 11:48:06 FWUP[445]: ANY <0+emerg > 486.767.663:FWUP log :type=1,time=1,E=3,W=4,N=5,I=6,D=7
    Jul 9 11:48:06 FWUP[445]: ANY <0+emerg > 486.771.249:ANY =5
    Jul 9 11:48:06 FWUP[445]: ANY <0+emerg > 486.771.913:libfwup build:1.0.5.1-release(Nov 12 2014,03:58:32).
    Jul 9 11:48:06 FWUP[445]: FWE <5+notice> 486.784.795:firmware logging :2015-7-9,11:48:06,784.598
    Jul 9 11:48:06 FWUP[445]: FWE <5+notice> 486.785.463:firmware build-at:Nov 12 2014,03:58:25
    Jul 9 11:48:06 LIBD[445]: HTTP<5+notice> response code: 200
    Jul 9 11:48:06 LIBD[445]: HTTP<5+notice> response process finish!
    Jul 9 11:48:06 FWUP[445]: UPD <5+notice> 486.843.652:fwup create done(453a8)
    Jul 9 11:48:06 FWUP[445]: UPD <5+notice> 486.844.982:fwup check enter(453a8)
    Jul 9 11:48:06 FWUP[445]: FWE <3+error > 486.847.040:give up installing for the same version:28.73.0.48
    Jul 9 11:48:06 FWUP[445]: FWE <3+error > 486.847.709:shit happed on check ROM info!
    Jul 9 11:48:06 FWUP[445]: UPD <3+error > 486.849.533:upgrade download check failed,err=-7,incompatible version
    Jul 9 11:48:06 FWUP[445]: UPD <5+notice> 486.850.715:fwup check done(453a8)
    Jul 9 11:48:06 ATP [445]: ATP <3+error > fwup_check Err(err_no = -7)
    Jul 9 11:48:06 FWUP[445]: UPD <5+notice> 486.851.868:fwup destroy enter(453a8)
    Jul 9 11:48:09 ATP [445]: ATP <3+error > AUTOP: Upgrade rom from url fail!
    Jul 9 11:48:09 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x00010007] wParam:(0x005a),lParam:(0x0000) BROAD_MSG_CONFIG_CHANGE
    Jul 9 11:48:09 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x00010007] wParam:(0x0010),lParam:(0x0000) BROAD_MSG_CONFIG_CHANGE
    Jul 9 11:48:09 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x00010007] wParam:(0x0056),lParam:(0x0001) BROAD_MSG_CONFIG_CHANGE
    Jul 9 11:48:09 SIP [637]: SIP <5+notice> [SIP] Main Recv:[0x00010007] wParam:(0x000a),lParam:(0x0000) BROAD_MSG_CONFIG_CHANGE
    Jul 9 11:48:24 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:48:24 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:48:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:48:25 SIP [637]: SUA <5+notice> [000] reg expire updated to (120)
    Jul 9 11:48:50 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:48:50 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] notify discard
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] dialog local target name:280
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] dialog call id:MDNiMDMyZDFlNTE4NDQ0MjYwMWZhNmE3ZWM0YTM4YWI.;to-tag=0e8bf82cbb194a5db106c31afb88dc8a;from-tag=d9616869
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] dialog state:1
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] dialog remote target uri:sip:412@192.168.42.162:5060
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] dialog local target uri:sip:280@192.168.16.2:5060
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] BLF uri:sip:280@192.168.16.2 status:1
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] key 4: status change to 129
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [0] 412 <-> 280 status: [1]
    Jul 9 11:48:50 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:48:51 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] dialog local target name:280
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] dialog call id:MDNiMDMyZDFlNTE4NDQ0MjYwMWZhNmE3ZWM0YTM4YWI.;to-tag=0e8bf82cbb194a5db106c31afb88dc8a;from-tag=d9616869
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] dialog state:1
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] dialog remote target uri:sip:412@192.168.42.162:5060
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] dialog local target uri:sip:280@192.168.16.2:5060
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] BLF uri:sip:280@192.168.16.2 status:1
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] key 4: status change to 129
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [0] 412 <-> 280 status: [1]
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [1] 412 <-> 280 status: [1]
    Jul 9 11:48:51 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:48:51 GUI [591]: DSSK<4+warnin>531.367.768:Is Exist In List ~!!
    Jul 9 11:49:04 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] dialog local target name:280
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] dialog call id:ZDg4OTNiN2FkNDFmNDY0MGM3ZDliZDgzMGZmY2MzMzI.;to-tag=2975590385;from-tag=d72ba673
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] dialog state:1
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] dialog remote target uri:sip:412@192.168.16.2:5060
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] dialog local target uri:sip:280@192.168.16.2
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] BLF uri:sip:280@192.168.16.2 status:1
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] key 4: status change to 129
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [0] 412 <-> 280 status: [1]
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [1] 412 <-> 280 status: [2]
    Jul 9 11:49:04 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:49:04 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] dialog local target name:280
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] dialog call id:MDNiMDMyZDFlNTE4NDQ0MjYwMWZhNmE3ZWM0YTM4YWI.;to-tag=0e8bf82cbb194a5db106c31afb88dc8a;from-tag=d9616869
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] dialog state:2
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] dialog remote target uri:sip:412@192.168.42.162:5060
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] dialog local target uri:sip:280@192.168.16.2:5060
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] BLF uri:sip:280@192.168.16.2 status:2
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] key 4: status change to 2
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [0] 412 <-> 280 status: [0]
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] key: [4] line: [0] call: [1] 412 <-> 280 status: [2]
    Jul 9 11:49:05 SIP [637]: SUA <5+notice> [000] Message sent: [(PHONE_MSG_KEY_STATUS_UPDATE_TO_UI) -- (0xa0041) wParam(0x0)-lParam(0x0)]
    Jul 9 11:49:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:49:25 SIP [637]: SDL <5+notice> [000] authinfo: 358
    Jul 9 11:49:25 SIP [637]: SDL <5+notice> [000] Message received from: 192.168.16.2:5060
    Jul 9 11:49:25 SIP [637]: SUA <5+notice> [000] reg expire updated to (120)
    eth0 Link encap:Ethernet HWaddr 00:15:65:50:CE:A7
    inet6 addr: fe80::215:65ff:fe50:cea7/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2930 errors:0 dropped:0 overruns:0 frame:0
    TX packets:860 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1024
    RX bytes:560995 (547.8 KiB) TX bytes:499728 (488.0 KiB)
    Interrupt:8

    eth0.15 Link encap:Ethernet HWaddr 00:15:65:50:CE:A7
    inet addr:192.168.16.155 Bcast:192.168.23.255 Mask:255.255.248.0
    inet6 addr: fe80::215:65ff:fe50:cea7/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1411 errors:0 dropped:0 overruns:0 frame:0
    TX packets:847 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:433374 (423.2 KiB) TX bytes:493733 (482.1 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
     
  11. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    I still don't know, why "Autoprovison Now" worked and the Provision request via the Admin panel didn't, but it looks like, if I am using the V73 provisioning template I can provision via the Admin panel all right.

    So I should be fine. I still need to do some testing.
     
  12. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    It is still not working. I got some test results mixed up, because autoprovision on power-on was still enabled.
     
Thread Status:
Not open for further replies.