I am not sure what you are trying to do. Your description is too brief to understand. Can you send me complete call flow?Thank you.On Sat, Mar 2, 2013 at 2:18 PM, Prakash N <prakash.n@tevatel.com> wrote:
Hi Muhammad,Thanks for your mailActually we are trying to do load balance with one Kamailio with multiple Asterisk serverNow if call Queue,IVR to Kamailio it routing to asterisk with ramdam strategy load balance ( first call on one and second to other server )If i call extension to extension it is landing to all Asterisk ( I have use all Asterisk feature for that i want to route all call to asterisk ) on the same time ,How to do load balance for extension calling alsoWe are not sure what we are tiring doi is right or wrongPlease advice and correct us if anything wrongWith RegardsN.PrakashOn Sat, Mar 2, 2013 at 6:30 PM, Muhammad Shahzad <shaheryarkh@gmail.com> wrote:
Why are you forwarding instead of relaying the message to selected destination? Forward is stateless and therefore likely to have NAT issues, specially if destination server is behind NAT or client is behind NAT and destination server is unable to handle NAT etc. etc.Also typically dispatcher is used to load balance calls between two or more upstream server, not for load balancing extensions within one server, though with some tweaking that might also be achieved but better to do this kind of thing on destination server rather then on kamailio.Thank you.--On Sat, Mar 2, 2013 at 10:31 AM, Prakash N <prakash.n@tevatel.com> wrote:
Hi,Can you please advice for the below issueWith RegardsN.PrakashOn Fri, Mar 1, 2013 at 9:32 AM, Prakash N <prakash.n@tevatel.com> wrote:
Hi All,We have finished the Kamailio & Asterisk real time integration and load balancing also done using dispatcher module.Queue and voice mails are load balancing as well.When we are calling extension to extension it is showing in all the servers.It seems extension are not load balancing as per our knowledge.I have attached the kamailio.cfg for your reference,Find my coding below as mentioned.# -- dispatcher params for DB support --modparam("dispatcher","db_url", "mysql://openser:openserrw@192.168.1.170/openser")modparam("dispatcher", "table_name", "dispatcher")modparam("dispatcher", "setid_col", "setid")modparam("dispatcher", "destination_col", "destination")modparam("dispatcher", "flags_col", "flags")modparam("dispatcher", "priority_col", "priority")-----------------------------------------------------------------------------------------# Dispatch requestsroute[DISPATCH] {if ( method=="INVITE" ) {# dst_select( "GROUP", "HASH METHOD")ds_select_dst("1","4");sl_send_reply("100","Trying");forward();#uri:host, uri:port);exit();}}Kindly suggest the solution for the same.Thanks in advance.Regards,N.Prakash
Muhammad Shahzad
-----------------------------------
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN: shari_786pk@hotmail.com
Email: shaheryarkh@googlemail.com--
Muhammad Shahzad
-----------------------------------
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN: shari_786pk@hotmail.com
Email: shaheryarkh@googlemail.com