<div dir="ltr"><br><div class="gmail_extra">Hi,<br><br><div class="gmail_quote">On Tue, Dec 10, 2013 at 5:16 PM, Karsten Horsmann <span dir="ltr"><<a href="mailto:khorsmann@gmail.com" target="_blank">khorsmann@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br>originate {sip_cid_type=rpid,origination_caller_id_name=400,origination_caller_id_number=400}sofia/example/<a href="mailto:300@foo.com" target="_blank">300@foo.com</a> &bridge({sip_cid_type=rpid,origination_caller_id_name=300,origination_caller_id_number=300}sofia/example/<a href="mailto:400@bar.com" target="_blank">400@bar.com</a>)<br>
</div></div></blockquote><div><br></div><div>I don't have a problem setting the CID name/number on either leg. The problem is with display name updates initiated by the remote endpoint. I don't know in advance what the display name update contains. Otherwise, what you suggest might be used as a workaround, but only in case the display name doesn't change during the call and only if it is known in advance. This isn't the case for example with display name updates that may be triggered by transfer happening outside of FS.</div>
</div><br></div><div class="gmail_extra">Best,</div><div class="gmail_extra">Hristo</div></div>