Posted: Wed May 20, 2009 2:03 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
I've posed this question in person to people with some frequency over
the last few years, and the answer has always been "No, I don't know
of such a service." but I'll try on the list and see what I get.
I think it would be a great asset to the Asterisk community to have a
service provider (let's call them "SP-A") who is a mobile carrier who
offered the following method: if I register a SIP entity with their
servers, they would then register with the HLR of my mobile carrier
("SP-B") and act as if I was roaming into a mobile network operated
by SP-A. SP-B would then take all calls and text messages destined
for my mobile device and send them to SP-A. SP-A in turn would then
relay those calls and messages to my Asterisk server, via SIP and/or
XMPP.
I would have pre-registered my mobile number with SP-B and
authenticated that I was the owner of that mobile number. SP-A would
hopefully charge very little for the calls - perhaps a slight premium
on what I'd expect for a SIP carrier.
This would, I believe, quickly make Asterisk a roaming-capable
solution for mobile devices. Local Asterisk servers would be able to
(as an example) detect dual-mode devices and then route calls in the
office in the appropriate manner. Bluetooth could be used as the
"trigger" for non-dual-mode phones. I have faith that Asterisk
developers and administrators would descend upon this type of service
like locusts. The trick would be to make it purchase-able by
individuals, and not as some large-scale process that involved sales
contracts and NDAs and the like. This needs to be a web form, a
credit card/paypal account, and some good documentation.
Potential problems: what if my mobile phone is registered with SP-A or
some other provider already? Who gets the messages? How do HLRs
manage multi-registration conflicts?
JT
---
John Todd email:jtodd@digium.com
Digium, Inc. | Asterisk Open Source Community Director
445 Jan Davis Drive NW - Huntsville AL 35806 - USA
direct: +1-256-428-6083 http://www.digium.com/
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Wed May 20, 2009 3:51 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
On Wed, 2009-05-20 at 11:00 -0400, John Todd wrote:
Quote:
I've posed this question in person to people with some frequency over
the last few years, and the answer has always been "No, I don't know
of such a service." but I'll try on the list and see what I get.
I think it would be a great asset to the Asterisk community to have a
service provider (let's call them "SP-A") who is a mobile carrier who
offered the following method: if I register a SIP entity with their
servers, they would then register with the HLR of my mobile carrier
("SP-B") and act as if I was roaming into a mobile network operated
by SP-A.
so similar to truphone.com except that you have to get the number from
them (or port in) and they become your carrier, when you have GSM
service you use that, when you have SIP it goes that way, and they even
do a hot handoff of a live call or something. I havent used them just
heard about them.
truphone may bring some "bad blood" into the discussion since it uses
freeswitch.org and there are some on this list that get livid when that
is mentioned, but they have been doing this for several years now on a
freeswitch platform.
As for registering the roaming stuff, that becomes more difficult, you
have to have SS7 connectivity with a SS7 stack with the MAP extensions.
You also have to have a roaming agreement and honestly there is no
incentive for the mobile carriers to allow this, so its a hard sell. It
also screws up their fraud detection algorithms in that you have
multiple phones registered on the same account, sure they could change
this, but why change it to allow competition? Its easier to do it the
other way around, which is what truphone does.
truphone is geared more towards a mobile phone, use sip when its
available otherwise use the GSM network, and not "give priority to a sip
registered device otherwise failover to the mobile phone".
Quote:
This would, I believe, quickly make Asterisk a roaming-capable
solution for mobile devices.
except that without realtime routing updates it can get into a confused
state. What if your expire time is 3600 seconds, which seems common for
many devices, although NAT can lower that to 20 seconds if the device
does keepalives in a way that works.
you could also make it 'roaming' by giving out 1 number that goes to
your asterisk box that then concurrently rings your sip device and your
mobile and whomever answers first gets the call. The trick is that your
outbound caller id would be wrong if you did not first call your
asterisk box to place the call, although GSM uses a modified Q.931 stack
which might allow a clever person a way around this.
Quote:
I have faith that Asterisk
developers and administrators would descend upon this type of service
like locusts.
do you have faith in the mobile carriers to allow this? To interconnect
their SS7 networks when they dont have to? To modify their fraud
detection algorithms to not freak out and lock the account when there
are 2 registered devices?
Quote:
Potential problems: what if my mobile phone is registered with SP-A or
some other provider already? Who gets the messages? How do HLRs
manage multi-registration conflicts?
generally they say "ut oh this cant happen so it must be a cloned phone"
and a trigger is fired off to lock the account. Many HLR
implementations also do not allow for multiple registrations by
different devices since in theory that should never happen. How
companies like tmobile that does a sip handoff deal with it is to do it
in the routing part and not in the HLR part, so that when a call is
placed to your number they see that you are registered via SIP and give
that priority, failing over to the actual mobile.
Posted: Wed May 20, 2009 4:56 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
John -
Naturally, if you find such a service, I am eager to know about.
To address your closing questions, the mechanics of standard GSM
roaming are something like this:
* SP-B assigns your MSISDN E.164 when you are provisioned. All calls
placed to the MSISDN get routed to SP-B's HLR and then forwarded from
there to a hidden temporary E.164 called the MSRN, which is assigned
by a VLR somewhere. (More on the VLR next.)
* Where ever you roam, even within SP-B's own network, you never deal
with the HLR directly. Instead, you deal with VLRs. When you
register with a network, the VLR assigns you an MSRN and reports the
{MSRN,ISMI} pairing to SP-B's HLR so that inbound calls are routed
correctly. Note that all calls are routed as roaming calls through
VLRs, even when you are within your home network.
* In the proposed service, when you "roam" to SP-A, SP-A assigns you
a local MRSN. SP-A then contacts SP-B's HLR and reports the
{MSRN,IMSI} pairing. To do this, SP-A needs to appear to SP-B's HLR
as a VLR. From an implementation standpoint, this probably means
operating a full-featured SIP-GSM/MAP gateway and having peering
agreements with GSM carriers.
* As long as SP-A's roaming registration is in effect, all calls
placed to your MSISDN get forwarded to SP-A's MRSN by SP-B's HLR,
then, presumably, terminated in whatever device or third-party
network you have registered with SP-A.
* The most recent {MSRN,IMSI} registration is effective. To my
knowledge there is no mechanism for conflicts.
[That's a slight simplification, but any real GSM operator is welcome
to correct any of that if I got it wrong or left our something really
important for this discussion. I've punted on the SMS part of the
question, which includes a whole extra layer of routing among the
SMSCs, but has a similar theme to it.]
You only need one GSM carrier to step forward and act as SP-A,
assuming it doesn't get them black-balled from the GSM Association.
The ideal candidate would be a company that already operates both
VoIP routing services and a PLMN-connected GSM VLR. It could be a
valuable service. If I weren't neck deep in a lawsuit with Martone
Radio Technology, I might be out raising capital to do this myself,
since we will eventually need a service like this to act as a roaming
clearinghouse for OpenBTS systems.
-- David
On May 20, 2009, at 8:00 AM, John Todd wrote:
Quote:
I've posed this question in person to people with some frequency over
the last few years, and the answer has always been "No, I don't know
of such a service." but I'll try on the list and see what I get.
I think it would be a great asset to the Asterisk community to have a
service provider (let's call them "SP-A") who is a mobile carrier who
offered the following method: if I register a SIP entity with their
servers, they would then register with the HLR of my mobile carrier
("SP-B") and act as if I was roaming into a mobile network operated
by SP-A. SP-B would then take all calls and text messages destined
for my mobile device and send them to SP-A. SP-A in turn would then
relay those calls and messages to my Asterisk server, via SIP and/or
XMPP.
I would have pre-registered my mobile number with SP-B and
authenticated that I was the owner of that mobile number. SP-A would
hopefully charge very little for the calls - perhaps a slight premium
on what I'd expect for a SIP carrier.
This would, I believe, quickly make Asterisk a roaming-capable
solution for mobile devices. Local Asterisk servers would be able to
(as an example) detect dual-mode devices and then route calls in the
office in the appropriate manner. Bluetooth could be used as the
"trigger" for non-dual-mode phones. I have faith that Asterisk
developers and administrators would descend upon this type of service
like locusts. The trick would be to make it purchase-able by
individuals, and not as some large-scale process that involved sales
contracts and NDAs and the like. This needs to be a web form, a
credit card/paypal account, and some good documentation.
Potential problems: what if my mobile phone is registered with SP-A or
some other provider already? Who gets the messages? How do HLRs
manage multi-registration conflicts?
JT
---
John Todd email:jtodd@digium.com
Digium, Inc. | Asterisk Open Source Community Director
445 Jan Davis Drive NW - Huntsville AL 35806 - USA
direct: +1-256-428-6083 http://www.digium.com/
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Wed May 20, 2009 5:11 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
Good points. Fully agreed on the likely hostility of conventional
GSM carriers to this idea. The preferred approach would be to be a
subscriber of the "hybrid" carrier, SP-A, and then roam into SP-B's
service when needed. This would be more likely to fly with SP-B as a
business model.
Also, agreed that it is important that your devices not send in too
many registration requests from different VLRs too quickly, since
that is likely to trigger some kind of fraud detection. The GSM
design assumes that one IMSI is assigned to one device, and if you
appear to be in two places at once, an alert operator will notice and
take action. Again, if your HLR is operated by SP-A, they will have
a different notion of "normal" registration behavior and there is
less likely to be a problem.
On May 20, 2009, at 9:48 AM, Trixter aka Bret McDanel wrote:
Quote:
As for registering the roaming stuff, that becomes more difficult, you
have to have SS7 connectivity with a SS7 stack with the MAP
extensions.
You also have to have a roaming agreement and honestly there is no
incentive for the mobile carriers to allow this, so its a hard
sell. It
also screws up their fraud detection algorithms in that you have
multiple phones registered on the same account, sure they could change
this, but why change it to allow competition? Its easier to do it the
other way around, which is what truphone does.
Posted: Wed May 20, 2009 5:14 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
On May 20, 2009, at 12:48 PM, Trixter aka Bret McDanel wrote:
Quote:
On Wed, 2009-05-20 at 11:00 -0400, John Todd wrote:
> I've posed this question in person to people with some frequency over
> the last few years, and the answer has always been "No, I don't know
> of such a service." but I'll try on the list and see what I get.
>
> I think it would be a great asset to the Asterisk community to have a
> service provider (let's call them "SP-A") who is a mobile carrier who
> offered the following method: if I register a SIP entity with their
> servers, they would then register with the HLR of my mobile carrier
> ("SP-B") and act as if I was roaming into a mobile network operated
> by SP-A.
so similar to truphone.com except that you have to get the number from
them (or port in) and they become your carrier, when you have GSM
service you use that, when you have SIP it goes that way, and they
even
do a hot handoff of a live call or something. I havent used them just
heard about them.
I'm looking for something that doesn't require porting or obtaining a
new number - it "just works" with existing devices after a quick one-
time authentication/authorization step. TruPhone does this as a
bundled solution, which is I'm sure quite nice for their customer base
who is looking for an all-in-one product. I'd like to see people un-
bundle the components to allow more innovation and creation of new
services by clever developers and administrators.
Quote:
truphone may bring some "bad blood" into the discussion since it uses
freeswitch.org and there are some on this list that get livid when
that
is mentioned, but they have been doing this for several years now on a
freeswitch platform.
I'm not particularly concerned what platform anyone currently uses for
their particular flavor as long as the service is available in some
form to Asterisk users. Any type of flexible back-end could be used
for interfacing with this service; but of course I think Asterisk
would be the most widely used at this point because of the huge number
of connection methods and pre-existing platforms that are supported by
the project.
Quote:
As for registering the roaming stuff, that becomes more difficult, you
have to have SS7 connectivity with a SS7 stack with the MAP
extensions.
You also have to have a roaming agreement and honestly there is no
incentive for the mobile carriers to allow this, so its a hard
sell. It
also screws up their fraud detection algorithms in that you have
multiple phones registered on the same account, sure they could change
this, but why change it to allow competition? Its easier to do it the
other way around, which is what truphone does.
I'd say there is a big incentive for a small, clever mobile carrier to
offer this service. They suddenly get a small roaming fee from
thousands of users that they would not have ordinarily, and without
the cost of any additional RF infrastructure. First to market wins big.
Quote:
truphone is geared more towards a mobile phone, use sip when its
available otherwise use the GSM network, and not "give priority to a
sip
registered device otherwise failover to the mobile phone".
> This would, I believe, quickly make Asterisk a roaming-capable
> solution for mobile devices.
except that without realtime routing updates it can get into a
confused
state. What if your expire time is 3600 seconds, which seems common
for
many devices, although NAT can lower that to 20 seconds if the device
does keepalives in a way that works.
The service provider could reject expire times over a minimum number
of seconds. Users would have to understand that registration
intervals would be shorter due to potential conflict. Just part of
the technical terms and conditions. Plus, Asterisk can be man-in-the-
middle, as usual. Whatever local authentication/notification
(bluetooth?) is used to trigger a registration can have extremely
short keepalives - 5 seconds? 20 seconds? and then the upstream
service provider can get an un-register at the moment the local device
vanishes. Remember that SIP can proactively remove a registration as
well as time one out. Anyway, this is getting really into the
details. I'm certain that many of the issues have a technical
solution. The business and political issues are just as big, as you
note below.
Quote:
you could also make it 'roaming' by giving out 1 number that goes to
your asterisk box that then concurrently rings your sip device and
your
mobile and whomever answers first gets the call. The trick is that
your
outbound caller id would be wrong if you did not first call your
asterisk box to place the call, although GSM uses a modified Q.931
stack
which might allow a clever person a way around this.
Yes, that's been done many times, including by TalkPlus (which many of
you are getting tired of hearing that I co-founded.) The net result
is that it's a hack that apparently is not that popular, or everyone
would be doing it. Only with the most mighty marketing (Google) will
this become even marginally acceptable. Customer resistance to
porting or getting a new number is extremely high. Perhaps people in
Europe are less whiny about this because their roaming costs and
mobile costs are so unrealistically prohibitively high. But in North
America the savings vs. hassle value doesn't justify customers to go
through the headaches.
Quote:
> I have faith that Asterisk
> developers and administrators would descend upon this type of service
> like locusts.
do you have faith in the mobile carriers to allow this? To
interconnect
their SS7 networks when they dont have to? To modify their fraud
detection algorithms to not freak out and lock the account when there
are 2 registered devices?
I have no faith in mobile carriers as a population; they tend to be a
sluggish and closed-minded bunch (though they talk a good game.)
However, if it is possible for a single mobile carrier to innovate
with this service and capture the market, then I think someone might
consider it. The fraud issue may be a deal-breaker; it may not.
Don't know until someone tries and builds a compatibility list. I'm
trying to encourage new services delivered via IP, not come up with
reasons they won't work.
Quote:
> Potential problems: what if my mobile phone is registered with SP-A
> or
> some other provider already? Who gets the messages? How do HLRs
> manage multi-registration conflicts?
>
generally they say "ut oh this cant happen so it must be a cloned
phone"
and a trigger is fired off to lock the account. Many HLR
implementations also do not allow for multiple registrations by
different devices since in theory that should never happen. How
companies like tmobile that does a sip handoff deal with it is to do
it
in the routing part and not in the HLR part, so that when a call is
placed to your number they see that you are registered via SIP and
give
that priority, failing over to the actual mobile.
Yes, I've considered the fraud issue, but I have no direct
experimental evidence to say how carriers implement that kind of
blocking. Certianly, the existing dual-mode carriers (T-mobile, for
instance) are trying desperately to keep users locked inside the garden.
Even in the worst case: This would work for, as an example, people
who live outside of normal cell phone coverage. Or oil rigs. Or
entire populations that live outside of normal cell phone coverage
areas. Still a pretty big market, even if the dual-registration block
exists.
PS: There are ways that this can work where dual-registration never
happens. See the OpenBTS discussions of a while back - grab the
radio, and you by default prevent dual-registrations.
JT
---
John Todd email:jtodd@digium.com
Digium, Inc. | Asterisk Open Source Community Director
445 Jan Davis Drive NW - Huntsville AL 35806 - USA
direct: +1-256-428-6083 http://www.digium.com/
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Wed May 20, 2009 6:01 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
On Wed, 2009-05-20 at 14:11 -0400, John Todd wrote:
Quote:
I'm not particularly concerned what platform anyone currently uses for
their particular flavor as long as the service is available in some
form to Asterisk users. Any type of flexible back-end could be used
for interfacing with this service; but of course I think Asterisk
would be the most widely used at this point because of the huge number
of connection methods and pre-existing platforms that are supported by
the project.
I would argue that asterisk supports 1 platform, linux (ok, it can be on
multiple hardware platforms), and anything else is kinda "well gee it
works". I think this has been the digium policy for quite some time to
not officially support any other platforms. As for connection methods,
I do not know of one that exists in asterisk that doesnt exist in say
freeswitch. Freeswitch has the bonus of actually working to port and
support multiple platforms, including telco grade hardware like
telcobridges.com. Perhaps you meant pre-existing installations, on that
I would agree that asterisk has more.
Quote:
I'd say there is a big incentive for a small, clever mobile carrier to
offer this service. They suddenly get a small roaming fee from
thousands of users that they would not have ordinarily, and without
the cost of any additional RF infrastructure. First to market wins big.
The roaming fee is the home carriers fee plus the network that you are
roaming on, so if you have provider X and you are roaming on provider Y,
X bills you, and pays Y some fee. If the carriers dont like you very
much they can charge you higher roaming fees than they offer to a
company they do like, as a result it may not be a small roaming fee.
There is also extra overhead associated with roaming, there is the
settlement issues that come up, some risk because if a customer does not
pay their bill, you still have to pay the roaming fees, and other things
that come into it.
If you do not allow roaming but do negotiate to lease tower space in the
same way that Cingular/Tmobile do (they each have about half the US48 in
coverage, and lease space on each others towers to make it more
complete) that avoids some of the FCC fees that you would have to pay,
like frequency auction extortion er I mean fees. You would still have
to register as a CMRS provider and that can lead you into a regulatory
quagmire.
Intercarrier compensation for terminating calls can also be problematic
since CMRS stuff is done based on the MTA and not on the ratecenter as
POTS lines are. As a result many carriers were sending phantom traffic
rather than actually dealing with this in a grown up fashion. You could
try to do bill and keep and avoid this, but most carriers will only do
bill and keep if the traffic is near symmetric or if they are going to
be advantaged by it, see the pacbell default interconnection agreement
for their "if we send you more traffic its bill and keep if you send us
more traffic then we charge you" type clauses.
Getting interconnected also can take months if not over a year and
honestly I do not know offhand whether or not CMRS providers are allowed
to traffic across LATAs (they should be since MTAs in many markets cross
LATAs).
The carrier side of things is by no means a trivial undertaking,
requiring federal and state filings, approval, permits, and private
contracts with every carrier you are going to talk to. The SS7-MAP
stuff is not cheap either, afaik no one has made a cost effective
solution to that. So its a lot of time, money, and a bit of know how,
and if you cant build the customer base you are likely to run out of
money and leave your customers out to dry (or get bought out for
virtually no money to show for it).
Quote:
PS: There are ways that this can work where dual-registration never
happens. See the OpenBTS discussions of a while back - grab the
radio, and you by default prevent dual-registrations.
I am well aware of it, while developing my own GSM tracking, monitoring
(A5 rainbow tables do exist), and proxy software (MITM attack so the MS
is a pbx extension but can still talk to the mobile network) I came
across this, before you could officially get the code, the SF CVS web
page let you get it (and I got some of the pre-gpl code as a result :).
I personally dont like C++ though and there are some limitations in
openBTS that made it unsuitable for my needs.
The problem with this is that its not foolproof and the stock USRP radio
boards are 200mw for 900Mhz, and 100mW if you are doing 1800MHz. This
means that larger offices or RF noisy environments will not see much
coverage without multiple $1000 units. If they flap back and forth it
can cause some problems.
further if you are not careful such a device would run afoul of 18 USC
1029 ("scanning receiver") and for indictment purposes intent to defraud
is assumed and you basically have to prove that isnt the case, and there
may be some FCC issues with running it as well. Your neighbors may
experience harmful interference as a result of using this.
under 18 USC 1029 a scanning receiver is something that can get an
access device, and an access device is anything used by itself or in
conjunction with another access device to gain access to something.
ESN/MIN pairs were mentioned because of the time it was written (analog
AMPS system), however the way that its defined the IMSI/TMSI would also
qualify, technically the way its written an email address is an access
device because when used with a password it gives access to an email
account. Sigh. But it is the law, and people should be really careful
if they are going to be doing this stuff on their own. My stuff was
exempt because I was originally propositioned by a government to write
my software, and I was not in the US at that time, later it became
something else :)
Posted: Fri May 29, 2009 12:57 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
I've had a few conversations in the last week with mobile carriers and
equipment vendors who have expressed interest in this concept. Some
of you have contacted me as potential consumers of such a service.
But the scale of interest is in question, and as I am not actually
developing this product I have only what is discussed on this list (at
the moment) as valid data to give to some organization who might be
considering such a service.
If it were possible to selectively and temporarily re-map a mobile
device so that inbound calls and SMS messages ended up on your
Asterisk server, delivered via SIP and/or other IP-based transmission
mechanisms, would you buy such a service? Assume it would be secure,
and authenticated both from the server perspective and from the end
device owner.
Private replies welcome.
JT
On May 20, 2009, at 11:00 AM, John Todd wrote:
Quote:
I've posed this question in person to people with some frequency over
the last few years, and the answer has always been "No, I don't know
of such a service." but I'll try on the list and see what I get.
I think it would be a great asset to the Asterisk community to have a
service provider (let's call them "SP-A") who is a mobile carrier who
offered the following method: if I register a SIP entity with their
servers, they would then register with the HLR of my mobile carrier
("SP-B") and act as if I was roaming into a mobile network operated
by SP-A. SP-B would then take all calls and text messages destined
for my mobile device and send them to SP-A. SP-A in turn would then
relay those calls and messages to my Asterisk server, via SIP and/or
XMPP.
I would have pre-registered my mobile number with SP-B and
authenticated that I was the owner of that mobile number. SP-A would
hopefully charge very little for the calls - perhaps a slight premium
on what I'd expect for a SIP carrier.
This would, I believe, quickly make Asterisk a roaming-capable
solution for mobile devices. Local Asterisk servers would be able to
(as an example) detect dual-mode devices and then route calls in the
office in the appropriate manner. Bluetooth could be used as the
"trigger" for non-dual-mode phones. I have faith that Asterisk
developers and administrators would descend upon this type of service
like locusts. The trick would be to make it purchase-able by
individuals, and not as some large-scale process that involved sales
contracts and NDAs and the like. This needs to be a web form, a
credit card/paypal account, and some good documentation.
Potential problems: what if my mobile phone is registered with SP-A or
some other provider already? Who gets the messages? How do HLRs
manage multi-registration conflicts?
JT
---
John Todd email:jtodd@digium.com
Digium, Inc. | Asterisk Open Source Community Director
445 Jan Davis Drive NW - Huntsville AL 35806 - USA
direct: +1-256-428-6083 http://www.digium.com/
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Fri May 29, 2009 2:08 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
Hi!
Quote:
If it were possible to selectively and temporarily re-map a mobile
device so that inbound calls and SMS messages ended up on your
Asterisk server, delivered via SIP and/or other IP-based transmission
mechanisms
The mobile carrier (reseller) solomo.de does that already for quite a
while.
Philipp
--
| aixvox GmbH
| Philipp von Klitzing
| Beratung und Technologie
|
| Monheimsallee 22
| 52062 Aachen · Germany
|
| T: +49.241.4133 141
| F: +49.241.4133 222
| E: mailto:pk@aixvox.com
|
| http://www.voice-compass.com
| http://www.aixvox.com
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Fri May 29, 2009 2:59 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
Philipp -
Sounds promising, but I'm afraid that German is not a language I
speak or understand, and various translation systems are not quite at
the level where they are able to adequately interpret technical or
marketing documentation. Do you have any idea where details might be
found on their service, described in English?
JT
On May 29, 2009, at 11:05 AM, Philipp von Klitzing wrote:
Quote:
Hi!
> If it were possible to selectively and temporarily re-map a mobile
> device so that inbound calls and SMS messages ended up on your
> Asterisk server, delivered via SIP and/or other IP-based transmission
> mechanisms
The mobile carrier (reseller) solomo.de does that already for quite a
while.
Philipp
--
| aixvox GmbH
| Philipp von Klitzing
| Beratung und Technologie
|
| Monheimsallee 22
| 52062 Aachen · Germany
|
| T: +49.241.4133 141
| F: +49.241.4133 222
| E: mailto:pk@aixvox.com
|
| http://www.voice-compass.com
| http://www.aixvox.com
---
John Todd email:jtodd@digium.com
Digium, Inc. | Asterisk Open Source Community Director
445 Jan Davis Drive NW - Huntsville AL 35806 - USA
direct: +1-256-428-6083 http://www.digium.com/
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Fri May 29, 2009 3:13 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
On Fri, 2009-05-29 at 11:56 -0400, John Todd wrote:
Quote:
Philipp -
Sounds promising, but I'm afraid that German is not a language I
speak or understand, and various translation systems are not quite at
the level where they are able to adequately interpret technical or
marketing documentation. Do you have any idea where details might be
found on their service, described in English?
Posted: Fri May 29, 2009 4:05 pm Post subject: [asterisk-biz] Mobile extensions from Asterisk - HLR registr
Hi John!
Quote:
Sounds promising, but I'm afraid that German is not a language I
speak or understand, and various translation systems are not quite at
the level where they are able to adequately interpret technical or
marketing documentation. Do you have any idea where details might be
found on their service, described in English?
I knew you'd ask for that, but it appears they simply don't have an
Englisch version of their web site. So apart from using the Google
translation service your option is to learn the language that once was
the scientific lingua franca. ;->
About their VoIP service: If you register with a SIP UA then calls
directed to your mobile number will ring on your VoIP phone; you un-
register and your mobile rings again (at least that's why I have
understood, didn't try their offering). This is a nice way to avoid
international roaming charges - despite the current efforts of the EU
commission those are still too high in Europe (and of course the rest of
the world, but that is outside the scope of the EC).
Quote:
>> If it were possible to selectively and temporarily re-map a mobile
>> device so that inbound calls and SMS messages ended up on your Asterisk
>> server, delivered via SIP and/or other IP-based transmission mechanisms
>
> The mobile carrier (reseller) solomo.de does that already for quite a
> while.
Philipp
--
| aixvox GmbH
| Philipp von Klitzing
| Beratung und Technologie
|
| Monheimsallee 22
| 52062 Aachen · Germany
|
| T: +49.241.4133 141
| F: +49.241.4133 222
| E: mailto:pk@aixvox.com
|
| http://www.voice-compass.com
| http://www.aixvox.com
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
