Using plivo in India

[madmax]

Hi everyone,

   I am trying to install plivo and conect it to a DID number. I did follow the documentation and install freeswitch and plivo on amazon EC2, What do I do after that? If I want to handle calls from a physical DID number (eg.-080-67452367), what do I have to do? A few pointers to clear some jargons like softswitch, PRI line,etc and where do they exactly fit in would be of great help to me.

Thanks,

Madmax

[Venky]

When connecting freeswitch/plivo via a pri line it cannot be on amazon cloud. it needs to be on same hardware server physically connected to a pri line. think of priline as lan cable but for telephony..

[digvija...@gmail.com]

An alternate will be to use Amazon VPC to host Plivo in cloud and connect to a SIP to PRI gateway in a datacenter (Asterisk/FreeSWITCH/Avaya SIP Enablement Services/Any other)when you need to call out/in.

Regards
Digvijay

[Venky]

gatewaying a call from landline to sip to a server outside the country is in grey area and not recommended. plus virtual machines for telephony is a no for voice call quality.

[digvija...@gmail.com]

Yes, I should have mentioned that :

1) one should either have an IPLC
2) or should have ONLY the SIP to PRI gateway in India and no other trunks (international and local India trunks together shouldn't be setup on this box to route international-to-to local and vice versa)

to operate within the rules of DoT.

Voice quality can be a bit tricky for sure and needs to be tested case to case basis.

Regards

[Mitul Limbani]

Getting IPLC just kills all the advantages of Amazon's amazing pricing :P

Instead just host the boxes in India in same DC or premise where you are terminating the PRI Circuits.

Any one needing such hosting in India, can ping us off the list.

Regards,
Mitul Limbani,
Chief Architech & Founder,
Enterux Solutions Pvt. Ltd.
110 Reena Complex, Opp. Nathani Steel,
Vidyavihar (W), Mumbai - 400 086. India
http://www.enterux.com/
http://www.entvoice.com/
email: mi...@enterux.in
DID: +91-22-71967121
Cell: +91-9820332422

[Eli Finkelman]

Hi,

Speaking of India, does anyone have a resource for Indian based DID's. I understand VOIP is still not completely legal in India, but are DID providers that you can recommend?

Thank You,

Eli Finkelman

Co-Founder TelAPI.com

[Mitul Limbani]

Hey Eli,

DID hosting is still a 100% NO NO in India, however we can provide Hosted IVR where by your application box resides within the same infrastructure, and that you wont be allowed to pass the voice calls over to SIP / IP network.

Regards,
Mitul Limbani,
Chief Architech & Founder,
Enterux Solutions Pvt. Ltd.
110 Reena Complex, Opp. Nathani Steel,
Vidyavihar (W), Mumbai - 400 086. India
http://www.enterux.com/
http://www.entvoice.com/
email: mi...@enterux.in
DID: +91-22-71967121
Cell: +91-9820332422

[A E G]

On Tue, Sep 4, 2012 at 11:46 PM, Venky <ve...@plivo.com> wrote:

gatewaying a call from landline to sip to a server outside the country is in grey area and not recommended. plus virtual machines for telephony is a no for voice call quality.

that's interesting. I was under the impression that Plivo does run on AWS/EC2. Are your telephony services not running on a virtualized infrastructure and using a hybrid kind of a cloud connected to EC2 (or some other public cloud) via something like VPC / Direct Connect or whatever it's called in Amazon?

I'm still hoping you will get around to replying to my other mail about your architecture and network design choices.

[Digvijay Sinha]

Hello AEG,

Not sure if this question was for Venky, excuse me if I jumped in unexpectedly to answer. Since you have marked it to the group here are few quick inputs:

Plivo Open Source definitely runs awesome on AWS and OpenStack (tested for about 200 cps on a high cpu medium instance). Also Using VPC with Direct Connect (if you are in the US) to reserve bandwidth if you plan to handle very high volumes is an extremely good idea.

Digvijay

[A E G]

On Fri, Sep 7, 2012 at 4:37 AM, Digvijay Sinha <digvija...@gmail.com> wrote:

Hello AEG,

Not sure if this question was for Venky, excuse me if I jumped in unexpectedly to answer. Since you have marked it to the group here are few quick inputs:

Plivo Open Source definitely runs awesome on AWS and OpenStack (tested for about 200 cps on a high cpu medium instance). Also Using VPC with Direct Connect (if you are in the US) to reserve bandwidth if you plan to handle very high volumes is an extremely good idea.

Digvijay

Digvijay,

Yes, it was implicitly intended for Venky but it's always good to have discussions like these in the relevant group as it gives others in the community a chance to chime in and share their research and experience, just like you did. So thanks for sharing that.

Ok, so your test setup is a hybrid then, with a private cloud built on Openstack and also using AWS? Would you be able to share a little more detail as to what components are running on which cloud? I have not downloaded/installed Plivo as yet so I am not sure how it all comes down, so some of what I ask/say might sound stupid, but assuming the above setup, I'd think you can install whichever piece you want wherever you want?

Also, For a more capacity setup, can one install several servers as a "telephony farm" running Plivo layer + Freeswitch fronted by some open-source sip router like openser, opensips etc for security, load-balancing and HA etc?

Any input from the Plivo team with this will also be appreciated :)

Thanks

aeg

[A E G]

On Wed, Sep 5, 2012 at 12:27 AM, Mitul Limbani <mi...@enterux.in> wrote:

...<snip>

Instead just host the boxes in India in same DC or premise where you are terminating the PRI Circuits.

From what I am reading,

PSTN -> PRI -> SIP -> IP-IP Gateway in India (India-based International Carrier)  -> IP-PSTN gateway Outside India (belonging to Same Indian International Carrier) -> PSTN (int'l)

 

is illegal?

[Digvijay Sinha]

No, its not.

[Digvijay Sinha]

AEG, I am a solutions architect with focus on unified communications, web 2.0 and telecom equipments/applications. I suggest or use Plivo Open Source as much as I use other platforms like Adhearsion, Telegraph (sometimes Twilio, Tropo, Mayo, Aculabs, Callfire and many others) as needed. Or I simply do some development on FreeSWITCH/Asterisk with my team to handle custom needs and then testing, benchmarking, support...

Having said that, tell us exactly what you need to achieve using Plivo and I will try to answer (or we will seek an answer from more experienced group members Mike or Venky).

To answer your question in the 2nd paragraph of your email, try the following:

Suggestion 1: Use DNSSrv for setting up a failover 'availability zone' on AWS for highly available frontend. Setup failover acoss various AWS regions.

Use 2 OpenSIPS instances (Active - Passive) and setup HA configuration and load balancing for all FreeSWITCH instances you want to run. Any custom development can be done on OpenSIPS in this case.

Suggestion 2: In the same setup as as above use AWS Elastic Load Balancer with a custom script which launches a machine image with freeswitch and all pre-requisites as soon as the load on another freeswitch instance reaches specified threshold and modifies the openSIPS load-balancing module setting to include the newly launched FS instance in the LB cluster. In this way AWS will handle load balancing and you may run very large volume of calls with auto scaling.

Suggestion 3: Use FreeSWITCH as SBC and OpenSER (not sure about FreeSWITCH's LCR module hence suggesting OpenSER for high volumes and huge routing tables) as the routing engine. You can setup AWS ELB script to load balance many Plivo+FS instances or one Plivo with many FS instances (not tested).

You will need to test in your requirement scenario and may be able to use some of the traditional telephony equipments which can not be virtualized as well as some billing server, provisioning server, RADIUS etc virtualized using OpenStack.

Regards

[A E G]

On Sat, Sep 8, 2012 at 5:52 AM, Digvijay Sinha <digvija...@gmail.com> wrote:

No, its not.

>> Cool. Ok, so they're not too crazy over there I guess because that would make no sense if VoIP traffic transits out of India over a licensed carrier despite the laws as outlined in the various messages in this thread.

[Digvijay Sinha]

Inbound directly over an Indian public IP isn't legal though. Also, there shouldn't be another gateway on your box hosted in India that lets you bridge/transfer an international line with/to an Indian phone line and vice versa.

Regards
-Sent from mobile, please excuse my brevity.

[A E G]

On Sat, Sep 8, 2012 at 7:40 PM, Digvijay Sinha <digvija...@gmail.com> wrote:

Inbound directly over an Indian public IP isn't legal though. Also, there shouldn't be another gateway on your box hosted in India that lets you bridge/transfer an international line with/to an Indian phone line and vice versa.

>> Understood. Which is why I mentioned the call flow in the previous message. All termination of traffic whether domestically or internationally is being handled by a licensed indian carrier unless even these carriers aren't allowed to move voice traffic over IP outside of the country.