Outbound CID not working after upgrade 15.0.37 -> 17

FreePBX Providers
1

Hi,

I’m moving my FreePBX instance to a new host and upgrading to a current version while I’m at it. I backed up my 15.0.37 instance (whose trunks and phones were old SIP).

Restoring the v15 backup onto the new v17 instance was smooth, and it warned me about the trunks needing to be migrated to pjsip and that the restore would attempt to do that.

It didn’t work, but it was easy to fix.where my register string in the old version was user:[email protected]/[user] (yes, user was there 2x), v17 didn’t like trailing /user string and complained about it when registration failed. I removed it from the reg string and I was able to register, and make outbound and take inbound calls using it.

The only problem was, with the outgoing calls, the CID configured in the Trunk definition wasn’t used. It was just set to xxxxxxxxxx so I tried “N Name” but no luck.

Is there some required change/config for CID to work when migrating to pjsip?

thanks

Kevin

2

You can try resubmitting the trunk configuration, or adding the caller ID to the extension or the outbound route.

3

I did try adding the CID to the extension and the route; by “resubmit” do you mean deleting and re-creating the trunk config?

Thanks

Kevin

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.