Originate via CLI - how to avoid 'private number' appearing on caller ID on phone?


(D E) #1

Currently using this

asterisk -rx 'channel originate local/401@from-internal extension 403@from-internal'

to get ext 401 to ring, then when it’s answered it dials 403. Works great. And for me so much quicker to setup than a call file.

Anyway to avoid “private number” appearing on extension 401 though? Would be great if it could say something useful. No big deal though, it’s a trivial detail.

Cheers!


(Communication Technologies) #2

(D E) #3

Thanks - doesn’t look like it can be done


(Daniel Friedman) #4

Hi @dan_ce,

Of course it can be done. You will need to send the originated call to another context, and there you would be able to set the correct CLI.

Thank you,

Daniel Friedman
Trixton LTD.


(Lorne Gaetz) #5

The conventional way of doing this is to use the Asterisk AMI, which supports doing Originate with a caller ID string.

*CLI> manager show command Originate
[Syntax]
Action: Originate
[ActionID:] <value>
Channel: <value>
[Exten:] <value>
[Context:] <value>
[Priority:] <value>
[Application:] <value>
[Data:] <value>
[Timeout:] <value>
[CallerID:] <value>         <--- This one

#6

and it is not a coincidence thar exactly those arguments (bar the ActionID of course) can also be used in a call-file if that is more convenient


(system) closed #7

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.