On Wed, 2010-01-20 at 12:45 -0500, Dale Worley wrote:
> On Wed, 2010-01-20 at 12:42 -0500, M. Ranganathan wrote:
> > I would suspect that it is a sipxconfig limitation. The From header
> > display name is obtained from the dial plan and is presented to
> > sipxbridge in the INVITE. SipXbridge simply forwards that INVITE.
> > Looking at it through wireshark, do you see the correct display name
> > in From before INVITE is seen by sipxbridge?
>
> The display name is broken before it reaches sipXbridge. The odd part
> is that the proxy forwards it correctly to the registrar, but
> incorrectly to sipXbridge.
Actually, I think that's an illusion. I've looked more closely and
repeated the unit test of the C++ Url class and it seems to work.
I think the illusion is created when the logs are merged - the first
message that shows as incorrect is the one sent from the proxy to the
bridge. That message appears in both logs, but only one of those copies
is put into the siptrace xml file. The frameid element for that message
is:
<frameId>11 sipxbridge.xml:16965 sipxbridge.xml:17015 sipXproxy.xml:655481
sipXproxy.xml:655496</frameId>
my guess is that the order there implies that the copy actually used is
the one from the sipxbridge.xml file.
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
