Remote Control Outgoing Call not working anymore?

[Attila]

Hi,

Updated from 35.82.0.20 to 35.83.0.30 and now my outgoing Call URI stoped working.

http://10.0.0.xx/servlet?key=number=+324...x@xx.xx.xx

Although my T48G asks me to accept the remote control it does not make any outgoing call afterwards.
But my endcall Uri works perfectly. when I place a manual call.

Did something change in 35.83.0.30 that effects this?

This is how I call the Uri
private string HTTPActionUriCall(string phoneNumber)
{
return "http://" + this.PhoneIP + "/servlet?key=number=" + phoneNumber + "&outgoing_uri=" + this.VoipAccount;
}
private string HTTPActionUriCallEnd()
{
return "http://" + this.PhoneIP + "/servlet?key=CallEnd";
}

Thx

[anonymous1712222627012]

Hi Attila,

I tried below ACTION URI on my T48G with the FW35.83.0.30 and it was working for me.

http://10.88.0.45/servlet?key=number=123...@10.2.1.48

(1234 means the
number you dial out; 1006@10.2.1.48 means
the SIP URL you dial from.)

Can you have a try again by resetting the phone and then enable the remote control and add your computer IP in the Action URI allow list?

KR
Samuel Wang

---

I think it is the "+" causing the issue, can you try a number without the "+"?

KR
Samuel Wang

[Attila]

(04-28-2018 03:23 AM)Samuel_Yealink Wrote:  KR
Samuel Wang

---

I think it is the "+" causing the issue, can you try a number without the "+"?

KR
Samuel Wang

Hi Samuel,

Iv'e tested it and your wright, it is the "+" character that causes the problem. Why is this a problem now? Do I need to change our whole phone book now or is there a setting to enable the "+" in the phone number through this Action Uri.

Attila

[anonymous1712222627012]

No, it appears to be a bug in the new firmware, and I have submitted it to the R&D for a fix, and it should be fixed in the next version.

Kind Regards
Samuel Wang

[anonymous1712222627012]

Dear Atilla,

The R&D has responed, this is not a bug, it's change in the V83 firmware to meet the norm of the standard URL(RFC3986), the best solution is to replace the "+" with "%2B".

Kind Regards
Samuel Wang

[Attila]

(05-08-2018 05:27 PM)Samuel_Yealink Wrote:  Dear Atilla,

The R&D has responed, this is not a bug, it's change in the V83 firmware to meet the norm of the standard URL(RFC3986), the best solution is to replace the "+" with "%2B".

Kind Regards
Samuel Wang

Hi Samuel,

Thank for the update, I'll try it out tomorrow. But I'm guessing that the phone itself will not recognize the number in the phonebook to show the contact name etc.
I'll leave a message here either way.

UPDATE:
Changed the "+" to "%2B" and it work like it should.

many thx
Attila