[asterisk-dev] DNID and RDNIS are not carried across IAX2

Nir Simionovich nir.simionovich at gmail.com
Mon Dec 28 07:00:15 CST 2009


  I strongly disagree with this - mainly due to the fact that Asterisk 
does forward CallerID
information. In my view, CallerID, DNID and RDNIS aren't all that 
different and should be
carried forward from one server to another, unless explicitly removed or 
changed on the

  Think about the Dial application, that automatically carries the 
CallerID from the inbound
call to the outbound call. If that information isn't carried across, 
interconnecting multiple Asterisk
servers into a single mesh will become a horid mess, and I'm confident 
no one wants that.


Benny Amorsen wrote:
> Nir Simionovich <nir.simionovich at gmail.com> writes:
>>   I know the easy way is to use SIP across the board, but I believe this 
>> should also be carried across with IAX2.
> I think you would have the same issue with SIP. Asterisk is not a SIP
> proxy. If you want headers carried on to the second call you need
> something like
> SIPAddHeader(X-My-Header: ${SIP_HEADER(X-My-Header)})
> I believe the syntax in IAX is something like
> Set(IAXVAR(X-My-Header)=${SIP_HEADER(X-My-Header)})
> but I don't use IAX, so that's a bit of a guess.
> /Benny
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev

More information about the asterisk-dev mailing list