...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Asterisk Codec Module Configuration
...
When Host A (remote to server with transcoder) requires a transcoding session from the remote transcoder in Host B, it will require to know how to route to the transcoder's internal vocallo module (ex. 10.1.1.151). Since the vocallo module IP is unknown to Host A, a route must be added in the Host A's routing table. To add a route to the routing table in Host A, type the following in the Linux CLI:
-> route add -net 10.1.1.0 netmask 255.255.255.0 gw <LAN IP of Host B> dev <ethX> , where "ethX" represents the ethernet device of Host A's main LAN
---> Multiple routes can be added in Host A if you have multiple connections to the network and want more than one access point for transcoding requests. Simply add a new route with the ethX of the next ethernet interface to configure
---> Perform the above step for all Asterisk serversA route in Host B's routing table will NOT be required because when the returning transcoded RTP stream from the vocallo module cannot find its destination through Host B's routing table (i.e. rtpip=Host A) it will route to Host B's default gateway, which will know about Host A and send the stream back to Host A.
* If you are certain that your default gateway does not know about Host A, then you will require to add the route:
-> route add -net <first 3 octets of Host A. 0> netmask 255.255.255.0 gw <gateway> dev <ethX> ,where "ethX" represents the ethernet device of Host B's main LAN