Tony makes a good point. Make sure your sub-accounts register to different switches. IE subaccount one to Chicago, subaccount two to Montreal, etc.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tony Graziano Sent: Tuesday, January 24, 2012 11:05 PM To: [email protected]; Discussion list for users of sipXecs software Subject: Re: [sipx-users] Voip.ms 403 Forbidden Errors after registered for several hours what the trace does not show is if any of your accounts/subaccounts are registered to the same pop with the provider. (i.e. more than one registration to the same pop from the same sipx system). On Tue, Jan 24, 2012 at 10:30 PM, Tim Ingalls <[email protected]> wrote: > Hi. I wonder if anyone has seen this. I have a voip.ms account with a > few sub-accounts. I am using sipxecs 4.4. I have the voip.ms NAT > setting for the sub-accounts set for "yes" and I have ports 5060 and > 5080 forwarded to the same (symmetrical) ports on my sipXecs server. > All of the sipxbridge gateway settings for this SIP trunk are the > defaults except for the choice of registration server. > > What happens is that after several hours, usually overnight, the > voip.ms portal still shows that I am registered, but I cannot pass any > calls. I get a 403 Forbidden message back and hear a fast busy. I have > tried lots of different settings, but the only thing that seems to > solve things is to switch the voip.ms portal's NAT setting to "no," > wait a minute, switch it back to "yes," and then restart my sipXecs > services to re-register. I have to do that every day. > > If I put the the voip.ms NAT setting to "no" I cannot register. > > On the Internet Calling > NAT traversal page I have both check-boxes > checked. What is frustrating is that I cannot change something and > immediately test it. I have to wait overnight to see if I have the > same problem in the morning. I am attaching two sipviewer trace files. > One is of a call to the 4443 echo test that fails, and the other is of > the same call that succeeds after toggling the NAT from yes to no to yes. > > Does anyone have a clue on this one? > > -- > Thanks, > > Tim Ingalls > Shared Communications, Inc. > 801-618-2102 Office > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
