Talk:SIP URI - VoIP.ms Wiki

Talk:SIP URI

From VoIP.ms Wiki

Jump to: navigation, search

Some things could use some clarification.

STRESS that unless one has a DID, SIP dialing TO voip.ms does not work. (This caught me, and I've been around for awhile!)

Using JohnSmith@ is perhaps a misnomer for this article / voip.ms - try 123456@ instead.

Perhaps give examples / show difference of calling an account, and a subaccount, where subaccount mentioned. e.g. 123456@ vs 1234567@ vs 123456_subaccount name.

Stress / split out use of SIP URI settings as phone book settings vs other uses, and IN PARTICULAR, that the voip.ms sip uri is entered on the OTHER system.

"Please note SIP URI is only functional through an external source, it is not intended to be used internally with VoIP.ms." - this isn't quite true, so split it out. e.g. Phone book. Note that SIP URIs are noted on portal page and in 'i' of subaccount management.

"You can route incoming calls to your DID numbers using a SIP URI address from other companies. You will need to create a string like youraccount@yourip to which you can route the DID(s). " add ... on the other company's system. Again, youraccount@ is a misnomer for voip.ms use, to which this wiki pertains. Use 123456@voip.ms instead. The quote also mixes from's and to's. Perhaps rephrase to: From other companies you can dial your DID numbers using a SIP URI address, such as 123456@voip.ms. You will need to create such a string at the other company.


" Creating a new SIP URI

To make a SIP URI that can be used with multiple DIDs, use the {DID} tag. The {DID} expression will be replaced automatically by the DID number as it is listed in the "Manage DID section". " is confusing.

Split out phone book use from non. Move phone book use up to this point in article. i.e. calling out. Then separately deal with calling in separately.

"use the {DID} tag" is a bit mystifying. Perhaps use an example first, e.g. 8005551212@voip.ms. Then move on to show how using {DID}@voip.ms would automatically substitute in the 8005551212 for you.

" 1{DID}@128.144.122.12

   12143221234@128.144.122.12 
   some_extension_name@128.144.122.12:5080 
   other_extension_name@voip.example.com 
   extension_name@123456_subaccount 
   {DID}@123456_subaccount (This produces the same result as routing the call directly to the sub account.) "

is confusing, probably because of the mix of incoming and outgoing in the same section.

The implication is that one can make up a random SIP URI, put it in the phone book, and external callers will automatically be routed. Yet that seems unlikely / is not confirmed / by example.

"{DID}@123456_subaccount" is particularly perplexing, as other references would say that it should be 123456_subaccount@toronto3.voip.ms - the implication here is that 18005551212@123456_subaccount@voip.ms is a viable address.

"Dialing out a SIP URI or using a SIP URI as forwarding does not generate cost (Outgoing call)." - this does not address incoming call. Moreover, as far as I know, default SIP URIs are auto-generated. And users cannot create their own. Else, what happens with two voip.ms John Smith users when they each try to create JohnSmith@voip.ms.

Thanks for listening.

-- Bill BillS 12:08, 17 February 2015 (EST)

On Rev.: "We have been notified that SIP Broker service is not working correctly."

Received the notice of page change, upon addition of "We have been notified that SIP Broker service is not working correctly.", etc.

In checking it out I observed the "This format of SIP address is used by services such as wikipedia:SIP Broker as a means to reach voip.ms subscribers." text.

Clicking on the wikipedia link, I got "This page has been deleted."

The (wikipedia) link should probably be substituted with something else.

-- BillS 09:15, 18 October 2016 (EDT)

Personal tools
Namespaces
Variants
Actions
VoIP.ms Wiki
Configuration
Guides (English)
Guides (Français)
Guías (Español)
Toolbox