Hi,<br><br>The case I'm working on is :<br>- a call comes from PSTN to a given extension (say 122)<br>- a user picks the call up (dialing *8122) from another extension (say 240) using a SIP hardphone<br>- the hardphone (he one with 240 extension) displays the dialed string (here *8122) instead of original caller-id.
<br><br>This is logical but I would like to change this default behaviour so that original caller-id is displayed along or instead of dialed string.<br><br>SIP hardphone vendor says it could be either done with :<br>1. SIP MESSAGE
<br>2. SIP P-asserted-identity<br>(Unfortunately both way are not supported yet by this phone vendor but that's another story).<br><br>Anyway, I tried to understand what SIP P-asserted-identity is and how it relates to my case.
<br>I can't see any relation.<br><br>Can anyone explain ?<br><br>My thoughts are :<br>- when replying 200 OK to SIP INVITE (from 240 extension), Asterisk server has to add a field P-Asserted-Identity in SIP header filled with original caller-id (using SipAddHeader ?)
<br>- when receiving such SIP message, P-Asserted-Identity-enabled SIP phone would display P-Asserted-Identity field data instead of what it uses to display<br>- is this correct ?<br>- and what if phone also supports caller-name display (phone has embedded directory and when caller-id matches with a directory entry, it replaces caller-id with caller-name) ? Shall I understand it will use P-Asserted-Identity data for directory lookup instead of other SIP header field ?
<br><br><br>Regards<br>
<br><br><br>