You will need:

WIFI / GPRS Internet Connection

iconnecthere / deltathree username (8 digits) and password (4 digits).

On your Nokia phone go to Setting > Connection >SIP Setting

1. Create a new profile: iconnecthere
2. Service profile - leave on default: IETF
3. Default access point - a previously defined wifi or gprs internet connection
4. Public user name: {username}@deltathree.com
5. Use compression: No
6. Registration: Always On
7. Use security: No
8. Proxy server - leave on defaults - no proxy server needed
9. Registrar server address: natrelay.deltathree.com
10. Relam: deltathree.com
11. User name: {username}@deltathree.com
12. Password: 4 digit account password
13. Transport type: Auto
14. Port: 5060

And thats it, you are ready to make VoIP calls from your mobile, enjoy.

ISP1 doesn’t allow SMTP (weird, eh?) and is *very* slow, and with frequent disconects.  ISP2 doesn’t allow VoIP and SSH sessions cannot last more than a few minutes.

We needed a solution where we could route certain type of traffic to the correct ISP.  This post is about how we made it.

1. First, we need a Linux machine (Fedora 10) with three network cards. We needed to buy two of them, but they’re very cheap and very straightforward to install. One of them will go to the LAN (eth2) and the other two will go to the WAN (Cablemodem and DSL) routers. Let’s call them eth0 and eth1.
2. We need to set the kernel to manage routing by having the line:

   net.ipv4.ip_forward = 1

   in the /etc/sysctl.conf file

3. Next, we need to create two independent routing tables, one for each WAN network interface, with their respective default gateway. This default gateway is assigned by the WAN modem/router.  We modify the file /etc/iproute2/rt_tables and add the following lines at the end of the file.

   200 T1

   201 T2

4. Let’s assume that our network configuration is as follows:
   • The LAN is on the 192.168.0.0/16 with a default gateway 192.168.3.1 (also being the address of the Linux machine, because this machine will work as a default gateway for the LAN).
   • WAN1 is on the 10.0.0.0/24 network with 10.0.0.1 as a default gateway and we have the IP address 10.0.0.2 assigned in the eth0 card.
   • WAN2 is on the 172.16.0.0/16 with 172.16.0.1 as a default gateway. The IP assigned to the eth1 card is 172.16.1.33
5. The following script will create the routing tables and NAT configuration so the local network can access the internet.  HTTP, HTTPS, FTP and SMTP will go through WAN1 and SSH, Torrent, and VoIP through WAN2.

   #Default gateway:

   export DEFAULT=eth0

   #Erase the route

   ip route flush cache

   ip route flush table T1

   ip route flush table T2

   ip route del default

   #Erase the firewall rules

   iptables -F

   iptables -X

   iptables -Z

   iptables -t nat -F

   #Interfaces

   export LAN_IF=eth2

   #eth0 = motorola

   export WAN1_IF=eth0

   #eth1 = 2wire

   export WAN2_IF=eth1

   #IP addresses

   export LAN_IP=192.168.3.1

   export WAN_IP1=10.0.0.2

   export WAN_IP2=172.16.1.33

   #Gateways

   export GW1=10.0.0.1

   export GW2=172.16.0.1

   #Networks

   export LAN_NET=192.168.0.0/16

   export WAN1_NET=10.0.0.0/24

   export WAN2_NET=172.16.0.0/16

   if [ $DEFAULT == "eth0" ]

   then

     export DEFAULTGW=$GW1

     export DEFAULTIF=$WAN1_IF

   else

     export DEFAULTGW=$GW2

     export DEFAULTIF=$WAN2_IF

   fi

   #Main routing table

   ip route add $WAN1_NET dev $WAN1_IF src $WAN_IP1 table T1

   ip route add default via $GW1 table T1

   ip route add $WAN2_NET dev $WAN2_IF src $WAN_IP2 table T2

   ip route add default via $GW2 table T2

   #Default gateway

   ip route add default via $DEFAULTGW

   #Or maybe we want to have one packet to each to be sent in round-robin to each interface

   #ip route add default scope global nexthop via $GW1 dev $WAN1_IF weight 1 nexthop via $GW2 dev $WAN2_IF weight 1

   #Routing rules. Choose a routing table

   ip rule add from $WAN_IP1 table T1

   ip rule add from $WAN_IP2 table T2

   #Other recomended rules

   ip route add $LAN_NET     dev $LAN_IF table T1

   ip route add $WAN2_NET     dev $WAN2_IF table T1

   ip route add 127.0.0.0/8 dev lo   table T1

   ip route add $LAN_NET     dev $LAN_IF table T2

   ip route add $WAN1_NET     dev $WAN1_IF table T2

   ip route add 127.0.0.0/8 dev lo   table T2

   #At this point we can see the tables with the command ip route show table T1 (or T2 or main)

   #Firewall marks

   ip rule add fwmark 1 table T1

   ip rule add fwmark 2 table T2

   #Setup default policies to handle unmatched traffic

   iptables -P INPUT ACCEPT

   iptables -P OUTPUT ACCEPT

   iptables -P FORWARD DROP

   #Then we lock our services so they only work from the LAN

   iptables -I INPUT 1 -i ${LAN_IF} -j ACCEPT

   iptables -I INPUT 1 -i lo -j ACCEPT

   iptables -A INPUT -p UDP --dport bootps -i ! ${LAN_IF} -j REJECT

   iptables -A INPUT -p UDP --dport domain -i ! ${LAN_IF} -j REJECT

   #(Optional) Allow access to our ssh server from the WAN1_IF

   iptables -A INPUT -p TCP --dport ssh -i ${WAN1_IF} -j ACCEPT

   iptables -A INPUT -p TCP --dport ssh -i ${WAN2_IF} -j ACCEPT

   #Drop TCP / UDP packets to privileged ports

   iptables -A INPUT -p TCP -i ! ${LAN_IF} -d 0/0 --dport 0:1023 -j DROP

   iptables -A INPUT -p UDP -i ! ${LAN_IF} -d 0/0 --dport 0:1023 -j DROP

   #We add the rules for NAT

   iptables -I FORWARD -i ${LAN_IF} -d ${LAN_NET} -j DROP

   iptables -A FORWARD -i ${LAN_IF} -s ${LAN_NET} -j ACCEPT

   iptables -A FORWARD -i ${WAN1_IF} -d ${LAN_NET} -j ACCEPT

   iptables -A FORWARD -i ${WAN2_IF} -d ${LAN_NET} -j ACCEPT

   iptables -t nat -A POSTROUTING -o ${WAN1_IF} -j MASQUERADE

   iptables -t nat -A POSTROUTING -o ${WAN2_IF} -j MASQUERADE

   #Finally, we make the rules to redirect the traffic to the appropriate interface

   #HTTP and HTTPS via Motorola

   iptables -t mangle -A PREROUTING -p tcp --dport http  -s ${LAN_NET} -j MARK --set-mark 1

   iptables -t mangle -A PREROUTING -p tcp --dport https -s ${LAN_NET} -j MARK --set-mark 1

   #FTP via Motorola

   iptables -t mangle -A PREROUTING -p tcp --dport ftp  -s ${LAN_NET} -j MARK --set-mark 1

   #SMTP via Motorola

   iptables -t mangle -A PREROUTING -p tcp --dport smtp  -s ${LAN_NET} -j MARK --set-mark 1

   #SSH via 2Wire

   iptables -t mangle -A PREROUTING -p tcp --dport ssh  -s ${LAN_NET} -j MARK --set-mark 2

   #Torrent via 2Wire

   iptables -t mangle -A PREROUTING -p tcp --dport 50000:60000  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p udp --dport 50000:60000  -s ${LAN_NET} -j MARK --set-mark 2

   #IConnectHere via 2Wire

   iptables -t mangle -A PREROUTING -p tcp --dport 5060:5063  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p udp --dport 5060:5063  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p tcp --dport 16384:16400  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p udp --dport 16384:16400  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p tcp --dport 5723  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p udp --dport 5723  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p tcp --dport 69  -s ${LAN_NET} -j MARK --set-mark 2

   iptables -t mangle -A PREROUTING -p udp --dport 69  -s ${LAN_NET} -j MARK --set-mark 2

6. We also need to configure the DHCP, SAMBA and DNS services so the users of the LAN will get a full experience.

Because of yalla ya!’s extensive experience with web 2.0 technologies, creating social networks and working on Internet communities, yalla ya! was able to build a prototype model for y-spot that provided them with the technological solutions for the challenges this particular project faced. yalla ya! successfully tracked wifi markets, usage and cultural information for Mexico City, where the first y-spot communities are planned to be launched.

By understanding the needs of start up projects and businesses, yalla ya! is able to structure functioning prototypes with a strong code base allowing for future growth. One of yalla ya!’s highest areas of expertise is in web development owning to yalla ya!’s intimate knowledge of internet business. Because of yalla ya!’s understanding of the Internet and how businesses ultimately interact and use the Internet, our clients get more than just development. yalla ya! clients receive expertise regarding social networks, security, SEO, technologies, hosting, user interface programs and web development based on only the closest understanding of Internet users.

• Our Details:

• Iztaccihuatl 36-203
• Hipodromo Condesa, Mexico DF
• 06170, MEXICO
• Telephone:(in Mexico) +52 55 5553 8152
• Telephone:(in Israel) +972 2 640 9369
• Email:info[the at sign]yalla-ya.com

This technology is very similar to known web 2.0 technologies, adapted to mobile application development. Nokia has preseted their new SDK version of the WRT 1.1 which allows interaction with the phone system and data.

During the code camp, Nokia reserved some time to a code competition - opening opportunity to the invited to participate and win two Nokia E71 phones. yalla ya! team on the spot decided to participate.

As experienced web developers, yalla ya! team easily adapted to this techonolgy and developed a Widget Application; MyIM - a mobile application that allows the user to logon to his Windows Live Messenger, Yahoo!, Gmail accounts and import his buddy lists to the phone address book.

as a result of this code camp, yalla ya! and Nokia is examining new opportuinites.

yes we have an amazing view; fountain, tree tops and just infront of the round about where we can watch people walk their dogs, ride bike or just having their walk in the park moment.

yalla ya! developed and integrated several aspects regarding the El Greco Hotel website and administration system. With factors that integrate for easy use, an internal reservation system was developed for the hotel. The system provided by yalla ya! also included integration for Credit Card processing with Banamex. Work such as this is an excellent example of the professional quality and servcies provided by yalla ya!

The API interface created for Producteev.com was developed in a dynamic way, allowing for the use of different integration formats (RESTful, JSON and RSS), all while the main site was still being developed. yalla ya! developed the API so it could be adjusted according to the needs of producteev.com over time, and was developed quickly and efficiently in order for it to be fully functional by the time the site was launched.

yalla ya! implemented a CRM system for GREENLANDER. This multifaceted process, mediated by a set of information technologies focuses on creating two-way exchanges with customers so that firms have an intimate knowledge of customer needs, wants, and buying patterns. In this way, the CRM developed for GREENLANDER maintains the company’s internal control and sales. This provides GREENLANDER with better organization and higher productivity in being able to anticipate the needs of current and potential customers. In addition to this, yalla ya! developed the company’s website which links an online catalog to GREENLANDER’S CRM, automatically updating information on the site about product availability for customers.