remote domain must be "anonymous.invalid" instead of "anonymous@anonymous.invalid" or you need to activate on via inbound routingswinstation wrote:hi
I faced your problem recently did you solve your problem?
actually I created external gateway and in its remote sip domain I define anonymous@anonymous.invalid but after creatation my I could not call to my extension.please share your experience.
sip incomming from public operator
Re: sip incomming from public operator
Re: sip incomming from public operator
I think instead of adding a extra ext gateway with remote domain name anonymous.invalid it should also possible to use the option System\Other System\Sip Parameters Via Header_ Inbound Calls Routing set to true. This option is available in R10 didn´t check the latest patch in R9.1. I didn´t test is so far but I think it should work.
Re: sip incomming from public operator
yes as already suggested "or you need to activate on via inbound routing"MrAnMo wrote:I think instead of adding a extra ext gateway with remote domain name anonymous.invalid it should also possible to use the option System\Other System\Sip Parameters Via Header_ Inbound Calls Routing set to true. This option is available in R10 didn´t check the latest patch in R9.1. I didn´t test is so far but I think it should work.
Re: sip incomming from public operator
I define anonymous@anonymous.invalid in sip ext gw .
there was a problem about sip configuration in system about my trunk group I delete my configuration and create it again and it works fine
there was a problem about sip configuration in system about my trunk group I delete my configuration and create it again and it works fine