Tomislav Parcina wrote:
Eric "ManxPower" Wieling wrote:
I believe that if Asterisk receives a 302 back from a device when
sending a call to it (i.e. the SIP device has Call Forwarding set)
Asterisk will do the right thing. This may only work for redirects to
locations on the same Asterisk server. This is NOT the case with
registrations, only call setup.
Well, this happens when I try to make outgoing call through Voipbuster
SIP provider. I register fine, but sometimes when I try to call someone
I receive that message (probably they redirect me to some server with
lower usage) and I can't establish phone call.
But, as far as I have understand you, this should work. Right?
Yes. My only experience with 302s are when I enable call forwarding on
a Polycom or Cisco phone. The phone sends Asterisk a 302 and Asterisk
then uses chan_local to process the call thru the dialplan as though the
call was dialed locally. I vaguely recall Olle adding the 302 support
several years ago and mentioning that there were security implications
with supporting 302s to destinations outside of Asterisk. <goes to
look> Look at this in sip.conf.sample:
;promiscredir = no ; If yes, allows 302 or REDIR to
non-local SIP address
; Note that promiscredir when redirects
are made to the
; local system will cause loops since
SIP is incapable
; of performing a "hairpin" call.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
