Callcentric issues
hwittenb:
Quote from: VOIPisGreat on October 25, 2012, 12:37:29 pm
For voip.ms, do you need to have a DID to be able to receive call thru SIP URI? If not what does the URI address look like?
VOIPisGreat,
You can call your voip.ms sub-account phone with the following sip uri format.
nnnnnnx@servername.voip.ms
where nnnnnn is your voip master account number, x is your voip.ms sub-account number and servername is the voip.ms server where you have your adapter registered. Actually your proper sip uri is shown on the "Manage Sub Accounts" web page when you move your cursor over circle i next to your sub account extension number.
When I try a test call using this sip uri it works when used as a forwarding number at IPKall. You cannot "manage" this incoming sip uri as you would a regular voip.ms DID where you forward it at the voip.ms account level, route to ring group, etc.
If you wish to setup a regular incoming DID as a sip uri, voip.ms has an option for that also. They call it a Virtual DID. The advantage here is that you can manage the sip uri like a regular DID. Voip.ms has a fee for this option, currently 25 cents per month with a per minute incoming call charge of one tenth of a cent per minute.
Ostracus:
User834 great explanation. Unfortunately I bet the Obihais aren't the only one with this problem. I wonder if a DNS proxy between the two would remedy the situation?
Johnny:
While I'm sure user834's response was a great response, could someone translate that response into plain language for us technically challenged types?
I have an OBI 110 and I had CC set up on SP2 until the rebooting problems started and then I deleted it and the rebooting stopped.
Other than porting my number out of CC, is there a way to get CC working with the OBI 110 without all the rebooting issues? Something simple hopefully.
Can a number from CC be ported to Google Voice?
Again, thank you user834 for that lengthy explanation, I just wish I understood it.
Thanks
tome:
Quote from: Johnny on October 28, 2012, 06:54:36 am
While I'm sure user834's response was a great response, could someone translate that response into plain language for us technically challenged types?
I have an OBI 110 and I had CC set up on SP2 until the rebooting problems started and then I deleted it and the rebooting stopped.
Other than porting my number out of CC, is there a way to get CC working with the OBI 110 without all the rebooting issues? Something simple hopefully.
Can a number from CC be ported to Google Voice?
Again, thank you user834 for that lengthy explanation, I just wish I understood it.
Thanks
In a nutshell Obi needs to fix the bug they have which causes the box to reboot every time they get a truncated dns response or in processing SRV records, whatever it is.
Tom
Johnny:
Quote from: tome on October 28, 2012, 08:55:53 am
Quote from: Johnny on October 28, 2012, 06:54:36 am
While I'm sure user834's response was a great response, could someone translate that response into plain language for us technically challenged types?
I have an OBI 110 and I had CC set up on SP2 until the rebooting problems started and then I deleted it and the rebooting stopped.
Other than porting my number out of CC, is there a way to get CC working with the OBI 110 without all the rebooting issues? Something simple hopefully.
Can a number from CC be ported to Google Voice?
Again, thank you user834 for that lengthy explanation, I just wish I understood it.
Thanks
In a nutshell Obi needs to fix the bug they have which causes the box to reboot every time they get a truncated dns response or in processing SRV records, whatever it is.
Tom
Thanks Tom.
Any idea if the OBI team is working on this fix? Maybe a new firmware upgrade soon?
I really liked CC, but it just doesn't work anymore with my OBI and I'm not buying another ata.
So, if OBI doesn't come up with a fix for this bug I will probably port my CC number to Voip.ms.
Do you know if CC is working with OBI to come up with this fix? Hopefully they are.
Thanks again..
Navigation
[0] Message Index
[#] Next page
[*] Previous page