Solved Can't Get SIP Trunk Working After Deleting

[kraichle]

Hi,

I have v14 currently working on a cloud server. I saved a backup file from the v14 and then setup v15.5 on completely different cloud server. During the install I used the v14 backup so v15.5 was mostly configured.

I'm using a Callcentric SIP trunk (ext 110) and I added another trunk extension (111) to Callcentric for the v15.5 PBX so I could keep v14 alive until I worked all the bugs of v15.5.

After I got v15.5 installed it had ext 110 as the Callcentric Trunk as expected. The PBX register the trunk as expected, and I did a test call with one of SIP phones that I pointed to the v15.5 PBX. I stopped all the services of v14 so there wasn't any conflict. The call went through fine.

I then added the 111 trunk and deleted the 110 trunk. I wasn't able to make a sucessful call anymore. The PBX shows both the phone extension and the 111 trunk sucessfully registered. The log shows the call coming in from the phone extension, but says no answer when it tries to get out the trunk.

I tried adding back the 110 trunk only and can't make that one work either. I can use a soft phone like zioper and connect to either trunk 110 or 111 and get a call through.

I've spent tons of hours wading through all the new v15.5 menus to see if I can find something I'm missing. It almost seems like there was a parameter that got blown away when I deleted the original trunk that got install with the restored backup, but have no clue what it might be. Any ideas?

 

[leejor]

I then added the 111 trunk and deleted the 110 trunk

So...other than the user name and password, are all other settings on these two trunks, the same?

The log shows the call coming in from the phone extension, but says no answer when it tries to get out the trunk.

What says "no answer"? The 3CX Activity Log? Does it show that call being sent to the correct trunk, but a timeout?

It almost seems like there was a parameter that got blown away when I deleted the original trunk that got install with the restored backup, but have no clue what it might be. Any ideas?

I would remove all trunks and start from scratch. Then...does the trunk register, if so, and a call from an extension still fails, post the Activity Log for that call. Check the log for an incoming call as well.

 

[kraichle]

I've deleted and added the trunk back, but an extension to external number still fails. Extension to extension works though. The trunk is registered on both ends PBX and Callcentric, but never makes it to Callcentric. For some reason the log seems to be missing the Trunk PBX extension like 10000 in v14. The log below says it isn't registered, but there is a green dot on the trunk status indicating it is.

See the log below,

09/09/2018 10:02:45 PM - Currently active calls [none]
09/09/2018 10:02:40 PM - Leg L:5.1[Extn:74] is terminated: Cause: BYE from PBX
09/09/2018 10:02:40 PM - [CM503020]: Call(C:5): Normal call termination. Call originator: Extn:74. Reason: Not available
09/09/2018 10:02:40 PM - L:5.1[Extn:74] failed to reach Out#:>>Rule{Calls Preceded by 1}>>15073633357, reason Not Registered
09/09/2018 10:02:40 PM - [CM503017]: Call(C:5): Target is not registered: Out#:>>Rule{Calls Preceded by 1}>>15073633357
09/09/2018 10:02:40 PM - Call(C:5): Call from Extn:74 to 15073633357 matches outbound rule 'Calls Preceded by 1'
09/09/2018 10:02:40 PM - [Flow] Call(C:5): has built target endpoint: Out#:>>Rule{Calls Preceded by 1}>>15073633357 for call from L:5.1[Extn:74]
09/09/2018 10:02:40 PM - [Flow] Target endpoint for 15073633357 is Out#:>>Rule{Calls Preceded by 1}>>15073633357
09/09/2018 10:02:40 PM - [CM503010]: Call(C:5): Making route(s) from Extn:74 to <sip:[email protected]:5060>
09/09/2018 10:02:40 PM - [CM505001]: Endpoint Extn:74: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Z 5.2.19 rv2.8.99] PBX contact: [sip:[email protected]:5060;transport=TCP]
09/09/2018 10:02:40 PM - [CM500002]: Call(C:5): Info on incoming INVITE from Extn:74:

 

[leejor]

09/09/2018 10:02:40 PM - [CM503017]: Call(C:5): Target is not registered: Out#:>>Rule{Calls Preceded by 1}>>15073633357

First be certain that the trunk that rule Calls Preceded by 1 is actually registered, and not simply set to not require registration and thus showing green. The error message is that Target is not registered. Double check where you are sending the calls.

 

[CentrexJ]

Check ip blacklist.

 

[kraichle]

omg, anyone see a problem here, ha. Well, I knew it was going to be simple, that's why I spent nearly all my Sat pissing around with it. I guess I'm still a novice. That's again leejor, you're the best.

 

[kraichle]

Meant to say thanks leejor. Other than the rule snag the upgrade to v15.5 went pretty smoothly, probably less than an hour overall.

 

[leejor]

Sometimes it's just a simple thing right, in front of us, but we still can't see it. Glad it worked out for you.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.