Yealink T48s call forward issue

This is caused by your rewriting the caller ID of the original caller to something that the provider won’t accept on the outbound leg. I had warned you in your previous thread that using prefixes like this is not a good idea. If you want to keep going down this rocky road, you’ll need to remove the prefix when used as caller ID for outgoing calls. This can be done with a ‘hook’ before dialing the trunk. See

IMO a better solution is to stop rewriting the caller ID (which begins with +) and edit your Outbound Routes so a number in E.164 format is accepted.