search for: forward_context

...Asterisk is wrong. At the moment there is a bristuffed Asterisk 1.2.18 running with bristuff-0.3.0-PRE-1y-g. Here is my dialplan, I simplified it a bit: [default] exten => 0123456789,1,Macro(dialpstn,${EXTEN}) [macro-dialpstn] exten => s,1,Set(TRANSFER_CONTEXT=transfer) exten => s,2,Set(FORWARD_CONTEXT=transfer) exten => s,3,Set(CIDNUMORIG=${CALLERID(num)}) ; save callerid-num exten => s,4,Set(CALLERID(num)=98765) ; dial out using msn 98765 exten => s,5,Dial(Zap/g1/${ARG1}|30|t) exten => h,1,Set(CALLERID(num)=${CIDNUMORIG}) restore callerid-num for CDR [transfer] exten => _X.,1,S...

...candidate of Asterisk 1.4.26. Asterisk 1.4.26-rc2 is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ This release fixes some issues reported by the community since the first release candidate. The most significant issues resolved include: * Treat an empty FORWARD_CONTEXT channel variable the same way we treat a non-existant one (issue #15056). * If using a deprecated musiconhold.conf format, reloading the module would cause the class to disappear (issue #14759). * Creation of generic call forward API, ast_call_forward() which is used to resolve a potenti...

...candidate of Asterisk 1.4.26. Asterisk 1.4.26-rc2 is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ This release fixes some issues reported by the community since the first release candidate. The most significant issues resolved include: * Treat an empty FORWARD_CONTEXT channel variable the same way we treat a non-existant one (issue #15056). * If using a deprecated musiconhold.conf format, reloading the module would cause the class to disappear (issue #14759). * Creation of generic call forward API, ast_call_forward() which is used to resolve a potenti...

...number Then there is no early media while the forward-to number is ringing. Our server is Asterisk 1.6 and theirs is 1.8. I tried promiscredir=yes and then the calls fail altogether because rather than using the local channel, it makes a SIP call that is not allowed. I don't think that the FORWARD_CONTEXT variable is used in these versions, because setting it doesn't impact the channel selection at all. -- Carlos Alvarez TelEvolve 602-889-3003 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/2013050...

I'm confused. What does Asterisk do when it gets a 302 with a new number to forward to? Is there anything I have to do in the dialplan to make this work? I can't find any clear documentation on this issue.

On Thu, March 5, 2015 09:56, Ruben R?gels wrote: > > Hi again, > > I'm glad to hear that I provided a somehow useful answer. > > Unfortunatelly, I don't know these details. > If you wasn't lucky consulting the snom docs, maybe the snom support > can be helpful with information about the exact implementation > details. > > You also could use "sip