Outnound Route Not Working

[hfoster]

Yeh, in the outbound route you can change the:

effective_caller_id_number=${outbound_caller_id_number}

to:

effective_caller_id_number=01234555555

A lot of SIP trunk providers will typically normalise the CLI if not correctly formatted (usually to the trunk authentication number) but some don't and just reject it. It really is a wild west out there with SIP.

 

[Adrian Fretwell]

Is there a global setting for CLID within FusionPBX

Just set it in the outbound route, if you don't want to add it to the extensions.

EDIT: Sorry, somehow didn't see the post from hfoster. - As he says...

 

[DigitalDaz]

IMHO you are much better putting it in the outbound caller ID on the extension. By hard coding it in the outbound route you are restricting yourself to that one caller ID. If you are single tenant, maybe not a problem but not a good habit to get into if you are multitenant being as it takes no time to add it anyway to the extension.

Also, when bulk creating extensions I always add the outbound caller ID there too.

 

[DigitalDaz]

Also, I see voip ms is saying they don't recognise the remote party id.

Go into the advanced gateway settings and try changing the caller id type to pid.

Don't forget to stop and start the gateway.