I think this is a Kumaran question. In his use case it was a click-to-call use case. In all cases it should still pass the full callerid.
If the + is not being handled by the click to call portal, that's more likely a click-to-call issue, but I thought that had been fixed a long time ago. On Fri, Oct 14, 2011 at 11:58 AM, Douglas Hubler <[email protected]> wrote: > On Fri, Oct 14, 2011 at 8:19 AM, Tony Graziano > <[email protected]> wrote: > > I am going to suggest that: http://track.sipfoundry.org/browse/XX-5120 > > Should be rolled back. If the callerid is +(whatever), it's a valid e.164 > > format and should be dial-able. It should not be removed. It is correct > the > > caller is an outside caller. I think the JIRA case needs to be > revisitied. > > That issue was supposed to ignore chars only when reading back number > to user. Can you prove otherwise? > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
