[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Call Pickup Bug - Unknown URI Scheme
Author Message
Bryan Nelson Offline
Member
***

Posts: 71
Joined: Feb 2013
Reputation: 0
Post: #1
Call Pickup Bug - Unknown URI Scheme
I'm having trouble configuring BLF keys to have call pickup abilities on the VP-530, and I believe it is caused by a URI parsing bug in the firmware.

On other Yealink phones(newer firmware), I can configure the call pickup string as a separate value. In our case it is *8. On older firmware like the VP-530, we simply add *8 in the extension box on the BLF config screen. This has always worked in the past for T-2x series phones and T-3x series phones.

The first difference seems to be that I must put the full *8{extension} in the extension field for the VP-530 to attempt to dial the correct *8{extension} string. Once it does try, it fails to dial due to an "unknown uri scheme". I believe I have captured this, and I can see the incorrect URI in the level 6 logs:

Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | Message received: [(SIP_MSG_CALL_INVITE) -- (0x40003) wParam(0x4a7d9e40)-lParam(0x21)]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | SIPUA Build Option ---Callee = [sip:*8460@nyc-phone-1.fluentcloud.com;BLF-Index=2] Replace= [(null)] ReferBy = [(null)] Rcid = [(null)]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | SIPUA Build Option ---Video = [1] conference= [0] intercom = [0] pickup = [32] sca = [0] call_invoke = [0]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | callee is sip:*8460@nyc-phone-1.fluentcloud.com;BLF-Index=2
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | Blf Index is 2
Jul 30 22:37:13 syslog[389]: [0388] 02452216 --after---element list size (0)
Jul 30 22:37:14 syslog[389]: [0388] 02452217 dataLogicToUI.listRegionData size = 0
Jul 30 22:37:14 syslog[389]: [0388] 02452217 ------------------GetCurrentElement
Jul 30 22:37:14 syslog[389]: [0388] 02452217 -----------GetCurrentElement NULL
Jul 30 22:37:14 syslog[424]: ^[[1m[ERROR]^[[0m (sipua_call_api.c:1493)Unknown URI scheme
Jul 30 22:37:14 syslog[389]: [0388] 02452226 [TALK][CSessionManager::DeleteSession] end
Jul 30 22:37:14 syslog[389]: [0388] 02452226 [TALK][***CSessionManager::UpdateWnd***] SessionID:-1,UIName:
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | Message sent: [(PHONE_MSG_CALL_FAIL) -- (0xa0009) wParam(0x4a7d9e40)-lParam(0x1a0)]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | send notify for in blf, call_did = [-1], notify_did = [-1]
Jul 30 22:37:14 syslog[424]: [0463] 02459103 Post message 0xa0009 to 388
Jul 30 22:37:14 syslog[424]: ^[[1m[ERROR]^[[0m (sipua_call_api.c:1964)Start new call: Build invite fail!


So, what I am seeing, is that the ";BLF-Index=2" is not stripped from the end of the sip: invite string. This creates an invalid server address, and the phone cannot attempt the pickup call.

I'm worried that this may never be fixed, as this phone no longer appears to be getting firmware updates. Is there anything we can do to work around this?


Attached File(s)
.tar  syslog (26).tar (Size: 334 KB / Downloads: 2)
07-31-2014 06:45 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
mpalmer67 Offline
Junior Member
**

Posts: 2
Joined: Dec 2015
Reputation: 0
Post: #2
RE: Call Pickup Bug - Unknown URI Scheme
(07-31-2014 06:45 AM)bnelson Wrote:  I'm having trouble configuring BLF keys to have call pickup abilities on the VP-530, and I believe it is caused by a URI parsing bug in the firmware.

On other Yealink phones(newer firmware), I can configure the call pickup string as a separate value. In our case it is *8. On older firmware like the VP-530, we simply add *8 in the extension box on the BLF config screen. This has always worked in the past for T-2x series phones and T-3x series phones.

The first difference seems to be that I must put the full *8{extension} in the extension field for the VP-530 to attempt to dial the correct *8{extension} string. Once it does try, it fails to dial due to an "unknown uri scheme". I believe I have captured this, and I can see the incorrect URI in the level 6 logs:

Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | Message received: [(SIP_MSG_CALL_INVITE) -- (0x40003) wParam(0x4a7d9e40)-lParam(0x21)]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | SIPUA Build Option ---Callee = [sip:*8460@nyc-phone-1.fluentcloud.com;BLF-Index=2] Replace= [(null)] ReferBy = [(null)] Rcid = [(null)]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | SIPUA Build Option ---Video = [1] conference= [0] intercom = [0] pickup = [32] sca = [0] call_invoke = [0]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | callee is sip:*8460@nyc-phone-1.fluentcloud.com;BLF-Index=2
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | Blf Index is 2
Jul 30 22:37:13 syslog[389]: [0388] 02452216 --after---element list size (0)
Jul 30 22:37:14 syslog[389]: [0388] 02452217 dataLogicToUI.listRegionData size = 0
Jul 30 22:37:14 syslog[389]: [0388] 02452217 ------------------GetCurrentElement
Jul 30 22:37:14 syslog[389]: [0388] 02452217 -----------GetCurrentElement NULL
Jul 30 22:37:14 syslog[424]: ^[[1m[ERROR]^[[0m (sipua_call_api.c:1493)Unknown URI scheme
Jul 30 22:37:14 syslog[389]: [0388] 02452226 [TALK][CSessionManager::DeleteSession] end
Jul 30 22:37:14 syslog[389]: [0388] 02452226 [TALK][***CSessionManager::UpdateWnd***] SessionID:-1,UIName:
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | Message sent: [(PHONE_MSG_CALL_FAIL) -- (0xa0009) wParam(0x4a7d9e40)-lParam(0x1a0)]
Jul 30 22:37:14 syslog[424]: <0> | LEVEL4 | send notify for in blf, call_did = [-1], notify_did = [-1]
Jul 30 22:37:14 syslog[424]: [0463] 02459103 Post message 0xa0009 to 388
Jul 30 22:37:14 syslog[424]: ^[[1m[ERROR]^[[0m (sipua_call_api.c:1964)Start new call: Build invite fail!


So, what I am seeing, is that the ";BLF-Index=2" is not stripped from the end of the sip: invite string. This creates an invalid server address, and the phone cannot attempt the pickup call.

I'm worried that this may never be fixed, as this phone no longer appears to be getting firmware updates. Is there anything we can do to work around this?

Were you able to fix this, having the same issue here.
03-04-2016 04:58 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Call from VP530 to VC400 is possible? cozpler 1 12,776 06-03-2016 05:31 AM
Last Post: Yealink_Michael
  VP530 and Smartphone Android VIDEO CALL valentinesquenet 1 14,890 06-03-2016 05:26 AM
Last Post: Yealink_Michael
  VP530 No sound for caller incoming call sjolmers 1 12,462 12-09-2015 11:15 PM
Last Post: Karl_Yealink
  VP530, pre call pickup video ssstofff 4 22,109 03-28-2015 04:34 PM
Last Post: ngokxit
  VP530 - While on a call I can't enter extensions or conference codes gdeloach@askbis.com 1 8,811 12-15-2014 05:37 PM
Last Post: Yealink_Jim
  VP530 sending H264 traffic on voice only call aboodoo 5 16,953 09-29-2014 01:54 PM
Last Post: James_Yealink
  3cx remote phonebook when Dialling or transfer call Bit-Tween 1 9,273 06-26-2014 05:46 PM
Last Post: Yealink Support
  Paging cutting off ongoing call aboodoo 5 17,793 05-28-2014 07:25 PM
Last Post: Yealink Support
Wink Yealink; button of call forwarding cfreire 2 15,629 06-08-2013 10:21 PM
Last Post: elementpbx

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication