Moving to new system system.. busy inbound when calling main number

FreePBX Providers
1

Hi,

  • have an Allstream SIP trunk that also has our main number on it..
  • setup a new freePBX system (v16) and literally cloned the current system. system is working fine with my voip/MS numbers forwarded to the new sysetem

past weekend we did a test and activated the Allstream trunk on the new system, connection was successfull. we could make outbound calls, I could see the allstream trunk referenced in the log files..

only quirk is, when calling into the main number, it rings busy…
copied the inbound/trunk/outbound settings idential to the existing system.

its a simple:
|DID|CID|Description

|Any|Any|General-Inbound|

the trunk auth is off, and uses whitelisted IP Address with provider.

not sure what I missed. tried to put the number as the did/cid etc.. forced trunk CID etc… just rings busy…
i don’t thnk i even say freePBX attempt to answer the call when we dialed..

also not sure if the MSP had the number forwarded to one of theirs??, but i don’t see any other relevant inbound routes … there is our 800 number listed, but I would doubt they would of had teh main fowarded to that ???

any insight appreciated, thank you
Peter

2

What logs did you check ? Can you paste sanitized SIP debug in a pastebin.freepbx.org ?

What is the telco reporting on their end ?

3

Hi penguinpbx,

oh, I forgot to update this in all my excitement.

The issue was a port mis-match, For the Allstream Trunk they are using port 5060, in the pjsip settings we were using 5061, once I changed it to 5060, the trunks lite up inbound and outbound without any issues.

Thanks

1 Like