I’m running FreePBX with Asterisk 13.19.1.
My VoIP phone is Grandstream GXP1630.
Having trouble with call forwarding to external numbers (e.g. cell phone numbers) not working.
Call forwarding to internal extension works.
Does a c.f to external numbers has to be enabled by a different way? (e.g. creating a virtual extension “mapping” to the external number and then the c.f. is being forwarded to the internal virtual extension?)
I had a look at the Asterisk CLI (asterisk -rvvvvvvvvvvvvv) and it states that the forwarded call to the external number is not possible due to no free lines - I do have 10 SIP channels and currently nobody is using the system, so it is not possible that all channels are busy.
This trouble is usually caused by sending a caller ID that your trunking provider will not accept. By default, FreePBX attempts to display the number of the original caller on the forwarded-to mobile.
Some trunking providers won’t allow you to send a number that is not yours. In that situation, you can either use a different provider for forwarded calls, or set the outbound caller ID to your main company number (or some other number that they will accept). If you are using the Follow Me function for forwarding, set the Change External CID Configuration and Fixed CID Value as required.
Some trunking providers are fussy about the SIP headers. For example, you may need to send a fixed value in the From user field and put the desired caller ID in P-Asserted-Identity. See their documentation and set up the trunk accordingly.
Finally, caller ID coming into your system may be in a different format than what is required going out. Decide which format you want (displayed on phones, in contact and speed dial lists, etc.) and adjust the incoming and/or outgoing format accordingly.
At the Asterisk CLI, use pjsip set logger on
(if a pjsip trunk) or sip set debug on
(for chan_sip trunk)
then make a failing call to see what is being sent to the provider and what error they are returning. Compare that to what happens when you dial the mobile directly.
If you still have trouble, post a (suitably redacted) log with the SIP trace included.