search for: i2next

...; from '"Anonymous" <sip:XXXXXXXXXX at anonymous.invalid>;tag=as67d9024d' This same peer works fine in Asterisk 1.6.2.X so I guess something need to be modified for 1.8? So far it has failed in all 1.8.X versions. Here is the sip.conf definition: [protel-out] fromdomain=i2next.com.mx defaultuser=123456789 secret=secret fromuser=123456789 type=peer host=i2next.com.mx qualify=no insecure=port,invite directmedia=no disallow=all allow=g729 allow=ulaw This same peer works when used from a dial command in the dial plan. I guess the problem has something to do that originate...

...handle_response_invite: Received response: "Forbidden" from '"Anonymous" <sip:XXXXXXXXXX at anonymous.invalid>;tag=as79fffc8d' Here is the sip.conf entry for that line: [protel-out] defaultuser=XXXXXXXXXX secret=XXXXXXXX fromuser=XXXXXXXXXX type=peer fromdomain=i2next.com.mx host=i2next.com.mx disallowed_methods = UPDATE nat=no qualify=no insecure=port,invite directmedia=no disallow=all allow=g729 context=entrada trustrpid=yes sendrpid=yes As I mentioned it works if I dial from a phone. CLI or AMI fails. -- Telecomunicaciones Abiertas de M?xico S.A. de C.V....