for those of you who experience this problem, what is your registration interval setting? With some ITSP's who have given me this headache, I found lowering my setting (sometimes 180) really reduced the problem (voxitas, etc.).
On Thu, Feb 9, 2012 at 7:43 AM, Tony Graziano <[email protected]> wrote: > On Thu, Feb 9, 2012 at 7:13 AM, Gerald Drouillard > <[email protected]> wrote: >> On 2/8/2012 10:48 PM, Philippe Laurent wrote: >> >> Gerald - >> >> After repeated hours and iterations, and I'm at the point where I know I'm >> missing something. >> >> I'll swallow my pride and say that I don't quite get how to do what you've >> proposed (IP Auth with Voip.ms + SIP URI + what you've done on the firewall >> to make it happen). I looked back at the list, and although I see you >> mention this in a previous voip.ms discussion, I guess I missed the part >> about how it works. >> >> Can you describe for me (us?) what you did where (sipx, firewall, voip.ms) >> to make IP Auth to work? My clients have become very accustomed to voip.ms >> rates, and if I can get their on-again off-again on-again service to behave >> a bit better (what has changed??), then it's a win-win. >> >> Many thanks in advance for your time and efforts. >> >> Philippe >> >> In your voip.ms account: >> >> DID Numbers >> >> SIP URI's >> >> Create a new SIP URI >> >> The SIP URI can be {DID}@yourhostname.com:5080 or {DID}@yourIPaddress:5080 >> >> >> Manage DID(s) >> >> Edit each DID and Change Routing from SIP/AIX to SIP URI and pick the SIP >> URI you created above. >> At this point your inbound calls are not dependent on your registration >> status. Most people say the inbound calls actually connect (first ring) >> faster than through registration. >> >> Sub Accounts >> >> You may have been registering with the main account in which case you will >> not have any sub accounts. You will have to create one. >> If you already have sub accounts you have the choice to change the existing >> sub account or create a new one. >> >> Create Sub Account >> >> Authentication type: Static IP >> IP Address: Your static Public IP >> Username: whatever you want (I don't think it matters) >> Device Type: Asterisk, .... >> NAT: yes (unless your server is configured with a public static IP) >> > If your firewall is configured correctly, why would NAT be set to YES. > Normally it would be set to NO if sipXbridge is in use and advertising > a public IP address (behind NAT). It has always been suggested to have > the provider DISABLE or TURN OFF NAT when using sipxbridge. In the > instances where it does not work for someone, I have always found the > outbound NAT type and/or STATIC port nat were not set properly before > creating the NAT entries, creating a dependency on NAT=YES at the > ITSP. This could potentially lead to the alarms? I never have them, so > I'm just saying... >> >> Manage Sub Accounts >> >> Edit the account you want to switch. See "Create Sub Account" >> >> >> In your Sipxecs Server >> >> Devices >> >> Gateways >> >> Edit Your Voip.ms account >> Under "ITSP Account" >> >> Show Advanced Settings >> Uncheck "Register on initialization" >> >> Sipx will now say it has to restart some things.... go ahead and do that. >> Sit back and enjoy your registration free connection. >> >> -- >> Regards >> -------------------------------------- >> Gerald Drouillard >> Technology Architect >> Drouillard & Associates, Inc. >> http://www.Drouillard.biz >> >> >> _______________________________________________ >> 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 > ~~~~~~~~~~~~~~~~~~ > 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! -- 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 _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
