Inbound calls failing on Cbeyond SIP Trunk

[IPScec]

IP 500v2 8.0.44

This is an existing SIP trunk with Cbeyond that is up and working on a Trix Box currently
LAN1 and WAN (LAN2) are plugged into ports on the switch. The Cbeyond IAD is going directly into the same switch.
Internal static IP on LAN1 and the Public IP given to me by Cbeyond on LAN2
SIP trunk is registering with Cbeyond
Outbound calls are working
Cannot get inbound calls to work – returns either a fast busy or a disconnect message
I have set the SIP Credentials and SIP URI per the Avaya IPO7.0 Cbeyond configuration guide. The only thing I am unsure about is the credentials on the SIP Registration screen. I have:

USER NAME: customer main number
AUTHENTICATION NAME: customer main number
CONTACT: have tried leaving it blank and <@cbeyond-msp> per cbeyond information
PASSWORD: confirmed and entered
EXPIRY: 15
REGISTRATION REQUIRED: checked

Cbeyond states my SIP trunk registration is coming from the public IP Address of the Gateway (IAD) not the one I gave to the IP Office LAN2. When it registers with that, then Cbeyond automatically sends the inbound calls to that IP Address. We currently have the IAD setup to forward all traffic on port 5060 to my public IP address on LAN2. From my understanding, this is the same way it’s setup with the Trix Box however the traffic forwards to the internal private static IP which is set in the Trix Box.

Happy to give any additional details as needed. Thanks in advance for your help!

 

[tlpeter]

Can you post a default trace of a call that fails?

BAZINGA!

I'm not insane, my mother had me tested!

 

[IPScec]

I did not get a default trace on inbound calls failing. I was not seeing them hit system status and the Cbeyond tech didn't see them getting past the IAD gateway so I just didn't think about it. Right now they are back up on their old system, I will not be able to switch over again until the end of the day today. Huge oversight on my part!

 

[tlpeter]

You will need monitor for traces.
SSA is not made for that.


BAZINGA!

I'm not insane, my mother had me tested!

 

[IPScec]

Yeah - I am going back to attempt again at 3:30 central time today. This will be the first thing I do. Thank you!

 

[IPScec]

I ran trace monitor - nothing hitting the phone system.

 

[amriddle01]

Then it isn't the system at fault

 

[trinetintl]

I had the same issue with a Broadbox SIP trunk, everything working perfectly then all of a sudden incoming calls stopped working with a busy signal after a long wait. Broadbox said it was the firewall but after screaming and yelling at them for a little bit, all of a sudden it started to work, perfect timing, because I don't remember the password for the firewall.
You are not going to see anything in SSA or Monitor because something is blocking the traffic, Broadbox kept telling me to trace it using WireShark but I could never figure out how to plug my laptop to allow me to trace on the public side of the firewall I was only able to trace on the LAN side and as expected nothing was coming in. Once traffic starts flowing from your carrier to the IPO, SSA and monitor will come back to life.


RE

http://www.trinet-intl.com

APSS - SME
ACIS - SME

 

[IPScec]

Okay, so I got inbound working. Had to remove the codes entered in CONTACT on my SIP Credential tab. Was told to put that in per Cbeyond tech. Took it out and it worked. Was sending bogus info in my registration string. Now, my outbound stopped working. No reason. I see in Monitor that the string I am sending send's my dialed number 4 times repeated.
To: <sip:7637671960o763767196076376719608240t7637671960m@sipconnect.msp0.cbeyond.net>

I have no idea where this is coming from. I have rechecked with another tech that everything is the same in my sip trunk and line, system, everything.

 

[IPScec]

Okay, just to update quick. I have out and in working now. I simply resorting to uploading a config I had saved when I knew out was working and in wasn't. Pushed it to the box, made the one change in the CONTACT field and viola - it worked. Thanks everyone. If anyone knows why my outbound string was repeating the phone number so many times, I would be very interested in that information.