freePBX Asterisk problem

[VOIPoTim]

Ray, what did you guys change? I have had no issues with outbound calls, suddenly today, I'm having the same problem (no outbound.) I added the fromuser and it works? Whatever you did, wow. I had to add fromuser, fromdomain AND change the context to specifically voipo.com

I don't know of any changes today, but there could have been. Since the residential service is designed to make sure there's no Caller ID spoofing and things along those lines, security has been tightened a lot lately. Sorry

[fisamo]

Wow. No kidding on the security tightening. I had to make the same changes. Your system is much less forgiving to * users now. I do understand why, and my comment isn't intended as criticism, just an observation.

If you're going to allow * users with a system this 'tight' (especially if you put in more restrictions), you will need to either post in your knowledgebase known-working config settings or, at least, have a canned ticket response for * setup requests. ("These settings are known to work, but beyond providing this information to you, we cannot provide specific support for * users.")

[john]

FWIW, I made all the suggested changes and still get the same error: WARNING[2350] chan_sip.c: Forbidden - wrong password on authentication for INVITE to '"305777xxxx". Security sure has been tightened! If I can't figure it out I will create a ticket.

BTW: I like what the Gizmo5 is doing. For $4/yr they let you set your Outgoing Caller ID. Setting the Caller ID to the home phone number is a must for the wife factor.

[dswartz]

John, one gotcha you may have missed: the outbound context MUST now be called voipo.com. I had been using VOIPO for outbound and VOIPO_in for inbound and even with all the other changes, still no joy. I noticed Ray had the outbound context as voipo.com and changed to that and was good to go.

[dswartz]

Well, this sucks. Just tried making a call, and it went through, but then I got an email from the script that alerts me when a trunk is down. Checked, and sure enough, no voipo. I have NOT changed anything...

Looking at 'sip show peers', codeblue is showing as unreachable, so maybe something's going on. I'll check again tomorrow.

Update this AM: still down. codeblue.voipo.com is still showing as UNREACHABLE. At least inbound still works

[fisamo]

Are you still down? I just made a test call to my mobile# from my Residential line, and it went through OK. I was also able to make a call a bit earlier (about 15 mins after you posted, just got called away from the PC and couldn't finish the message).

[dswartz]

Nope, now it's working

[VOIPoNorm]

I checked the logs and didn't see any major failures around the time you mentioned.

To anyone that may be monitoring this thread. In the ticket you open at http://support.voipo.com please include the calling number, the called number and the approximate time that the call was attempted. That will help us track down the call in the logs.

The suggestion about creating a template that requires these items before creating a support ticket is great.

Regards,
Norm

[dswartz]

Aughhh!!!!!!!! Now it's happening again! I'll update the ticket... If you want a copy of the wireshark trace, let me know...

[VOIPoDanielC]

I never got mine working again after troubleshooting for days.