Hello,
Yes, That was my mistake. now my asterisk fail over mechanism is working
fine.
Thanks a lot for helping me.
-urmi
On Tue, Aug 4, 2009 at 5:28 PM, Saúl Ibarra wrote:
> It's OPTIONS, not OPTION :)
>
>
> --
> Saúl -- "Nunca subestimes el ancho de banda de un camión lleno de
> disketes."
>
It's OPTIONS, not OPTION :)
--
Saúl -- "Nunca subestimes el ancho de banda de un camión lleno de disketes."
http://www.saghul.net/
___
Users mailing list
Users@lists.opensips.org
http://
Hello Alex,
First of all Thanks for ur Attention and quick response.
If I use the OPTION then on Asterisk I m getting following:
[Aug 4 17:15:32] NOTICE[7765]: chan_sip.c:14958 handle_request: Unknown SIP
command 'OPTION' from '192.168.1.30'
Even when that Asterisk Comes up, opensips is not s
urmi lakkad wrote:
> modparam("dispatcher", "ds_ping_method", "INFO")
Asterisk does not respond to these. Try using the OPTIONS method instead.
--
Alex Balashov
Evariste Systems
Web: http://www.evaristesys.com/
Tel: (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678)
Hello,
I am using Opensips and Asterisk for my call flow.
I am using 3 Asterisks for call forwarding. Opensips's dispatcher module is
doing the task of load balancing among all 3 Asterisk servers in a round
robin fashion. i. e.
1st call to 1st Asterisk
2nd call to 2nd Asterisk
3rd call to 3rd As