dslreports logo
uniqs
5
JeanInNepean
join:2012-09-19
Grenoble, FR

JeanInNepean to OzarkEdge

Member

to OzarkEdge

Re: [Voip.ms] calling sub-account SIP URI

I'm assuming that the voip.ms servers treat anonymous SIP calls differently than when they come from a registered user. If you are registered to washington.voip.ms, then you should dial 101@washington.voip.ms; not aaaaaa1@washington.voip.ms.

Dialing aaaaaa1@XXX.voip.ms should work as long as you're not registered on that server.
OzarkEdge
join:2014-02-23
USA

OzarkEdge

Member

Thanks! I did not find that in their Wiki.

So, internal SIP URI extension dialing: 101@washington.voip.ms (works).

And presumably, external SIP URI extension dialing: aaaaaa1@washington.voip.ms, where external means from outside VoIP.ms network. Dialing from another VoIP.ms server newyork to pop washington did not work.

External SIP URI extension dialing direct to an extension, bypassing call flow/filtering, gives back old meaning to Direct Inward Dialing.

OE
dmz
join:2006-07-12
canada

dmz to JeanInNepean

Member

to JeanInNepean
But what if you wanted to call a different voip.ms customer's extension? Dialling 101@washington.voip.ms doesn't mean anything in that context.

Why allow aaaaaa1@washington.voip.ms from other voip providers, and not internally?
JeanInNepean
join:2012-09-19
Grenoble, FR

JeanInNepean

Member

said by dmz:

Why allow aaaaaa1@washington.voip.ms from other voip providers, and not internally?

Because the asterisk server would not be able to differentiate between a call to the PSTN and a call to an account+extension that would match the same pattern (either NANPA or E.164).

voip.ms also has some SIP servers, namely sip.us1/2/3/4.voip.ms, that *might* work with such URIs.