Search found 14 matches
- Thu May 09, 2013 5:53 am
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request
Sorry, I should have started a new thread for the "Device Type" question. I did not mean to imply that it had anything to do with the "400 Bad Request". Despite my friendly queries, VoIP.MS has no inclination to investigate the matter. I consider the problem solved even though VoIP.MS has failed to ...
- Thu May 02, 2013 10:48 pm
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request
The little documentation I have found on VoIP.ms Device-Type: ATA: use options similar to "Nat keep alive" or "Nat mapping", set these options to YES or Enable. (ALL your DID calls use the account number in the invite string) PBX: add qualify=yes and nat=yes in your configuration trunk. (destination...
- Thu May 02, 2013 9:36 pm
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request
In the VoIP.MS account settings the "Device type" can be a) Asterisk, IP PBX, Gateway or VoIP Switch b) ATA device, IP Phone or Softphone I have always used setting (b) because I have always viewed sipsorcery as replacing an ATA device with sip providers, but of course SIPSorcery is a voip-switch. I...
- Thu May 02, 2013 5:27 pm
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request (solved)
Turning NAT on in the VOIP.ms advanced account settings resolved the problem. Not sure why it went from working to not working. I was under the impression the sipsorcery ip4 was direct to the net, which was reinforced by everything working with the NAT setting off. Somehow the path from sipsorcery t...
- Thu May 02, 2013 4:48 pm
- Forum: Feature Requests
- Topic: email notice upon loss of registration with provider
- Replies: 5
- Views: 12198
Re: email notice upon loss of registration with provider
An option to trigger a dial plan upon loss of registration with a provider would be useful.
- Thu May 02, 2013 4:38 pm
- Forum: Feature Requests
- Topic: email notice upon loss of registration with provider
- Replies: 5
- Views: 12198
email notice upon loss of registration with provider
Feature request:
Option for e-mail notification upon loss provider registration.
Thanks,
Jay
Option for e-mail notification upon loss provider registration.
Thanks,
Jay
- Thu May 02, 2013 4:18 pm
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request
Thanks Aaron
As usual, your support is wonderful.
As usual, your support is wonderful.
- Thu May 02, 2013 3:58 am
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request
Aaron, By the way just noticed on rereading your reply: I do NOT use a Register Contact scheme of (voipms.username@sipsorcery.com) and was registering fine on the seattle.voip.ms server at the time. So I assume there is at least one other having this problem. By just moving my successful registratio...
- Thu May 02, 2013 3:46 am
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request
I see a message like this often in the console: "DNS Manager does not currently have an entry for sip:losangeles.voip.ms, delaying next attempt by 10s." It usually registers on the next attempt. But renewing registration seems to go through the same process. I see this message with other providers a...
- Tue Apr 30, 2013 9:00 pm
- Forum: Technical Support
- Topic: VOIP.MS 400 Bad Request
- Replies: 11
- Views: 2216
Re: VOIP.MS 400 Bad Request
Thanks Aaron. I agree the problem is at the Voip.ms end. But I have not changed any settings at Voip.ms and I have no problem registering on their Seattle server. Am accepting suggestions here and waiting on response from Voip.ms customer support. I would think that considering I am receiving a "400...