AVPs are not dialog persistent, but you can use dialog module with dialog persistent vars to store the displayname from the original INVITE and apply it in all sequential requests.
If you are not familiar with how to use the dialog support, just let me know. Regards, Bogdan Erik Versaevel - InfoPact Netwerkdiensten wrote: > Hi Bogdan, > > Hmm, that would be just as confusing i think, i might be able to pull it off > by storing the original displayname in an AVP ? > > Regards, > > Erik > > > Op 8-7-2010 9:55, Bogdan-Andrei Iancu schreef: > >> Hi Erik, >> >> by design, the display name is not restored at all as it is not relevant >> from SIP point of view in the sequential requests. To avoid confusions, >> a simple hack I do in script, is, for sequential requests, to completely >> remove the display name part (also with uac_replace_from). >> >> Regards, >> Bogdan >> >> E. Versaevel wrote: >> >>> Hi all, >>> >>> Is there a reason why uac_replace_from() is not restoring the displayname >>> back to the sipclient? >>> >>> i'm doing a uac_replace_from() to mange the displayname/uri so my asterisk >>> machine wil use the correct >>> sip peer, however packages back to the sipclient only have their URI >>> restored and keep the displayname set with the uac_replace_from() >>> Is this expected behaviour? It's confusing for both me and the end users >>> because you suddenly recieve packages with another displayname. >>> >>> Kind regards, >>> >>> Erik >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >> > > > > Erik Versaevel > > -- Bogdan-Andrei Iancu OpenSIPS Bootcamp 20 - 24 September 2010, Frankfurt, Germany www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
