May I add that, to me, I would expect Asterisk to use CALLERID vlaues (name
and num) to set P-Asserted-Id.
Maybe in a couple of days, I'll report my findings here if can find some
time to experiment with Asterisk 17 or Asterisk 18 and compare behaviours..
Le mar. 8 déc. 2020 à 16:41, Olivier a écrit :
> Hello,
>
> With Debian Buster's Asterisk 16.2.1, please consider the following
> dialplan
> ;Case A
> ;exten = 29,1,Dial(PJSIP/${EXTEN})
> ;Case B
> ;exten = 29,1,Gosub(foo,${EXTEN},1)
> ;Case C
> exten = 29,1,Gosub(bar,s,1(${EXTEN}))
>
> [foo]
> exten = _X.,1,Dial(PJSIP/${EXTEN})
> same = n,Return()
>
> [bar]
> exten = s,1,Set(TGT=${ARG1})
> same = n,Dial(PJSIP/${TGT})
> same = n,Return()
>
> When running case A et B, dialing phone gets a Ringing signal from
> Asterisk with a P-Asserted-Id
> header set to 29: this is expected.
>
> When running case C, dialing phone gets a Ringing signal from Asterisk
> with a P-Asserted-Id
> header set to s: this is not what I expected.
>
>
> Thoughts ?
> Is there a way to work around this without using pattern B above ?
>
> Best regards
>
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
https://wiki.asterisk.org/wiki/display/AST/Getting+Started
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
