thanks for the answer.
is this something new in 1.2?
if so, where is it documented, and what is the point of autocreatepeer=yes if this is the case?
-yair
On 2/5/06, C. Zerbo [EMAIL PROTECTED] wrote:
you need to setup a asterisk peer at port 5070 in sip.conf to get the callreplying correctly
hi all,
I keep asking the question and getting no replies, so i'll keep asking :-)
In asterisk 1.09, with autocreatepeer=yes, if i send asterisk a SIP request from SER, specifically
rewritehostport(myIP:5070); (asterisk running on port 5070) asterisk picks up the request and matches it to the
In asterisk 1.2 asterisk completely ignores the request (even at most
verbose level) and an ngrep shows a not found returned to SER.
anyone have any idea why this is happening, bug/feature, or how to get
it to work the way it did in 1.09? I want to upgrade but I don't want
to lose this
Hi Jean-Michel,
have you tried upgrading? can you confirm this behavior? It seems to me this is a major issue for those of us running SER + asterisk, and who dont want to configure each SIP client in SER and asterisk separately.
-yair
On 2/5/06, Jean-Michel Hiver [EMAIL PROTECTED] wrote:
In
you need to setup a asterisk peer at port 5070 in sip.conf to get the callreplying correctly to ser.
Cheick Zerbo
Corbimas.com
[EMAIL PROTECTED]
From: Yair Hakak [EMAIL PROTECTED]Reply-To: Asterisk Users Mailing List - Non-Commercial Discussionasterisk-users@lists.digium.comTo: Asterisk Users