On Aug 15, 2016, at 3:08 PM, Mario G <mario_fs@mgtech.com> wrote:

I did it multiple ways, including the brackets first (I mentioned that in the jira), it always truncates at the colon no matter what. I also saw this in a couple of other places but didn’t want to go further until this is fixed. All of these get truncated:

      <param name="MWI-Account" value=“100@[$${local_ip_v6}]”/> < I set local_ip_address in vars without brackets

      <param name="MWI-Account" value="100@$${local_ip_v6}”/>

      <param name="MWI-Account" value=“100@[IP6ADDRESS]"/>

      <param name="MWI-Account" value=“100@IP6ADDRESS"/>

On Aug 15, 2016, at 11:47 AM, Michael Jerris <mike@jerris.com> wrote:

how are you setting the ipv6 address when you set Message-Account?  if you are setting full v6 addr put it in [ ]

On Aug 15, 2016, at 1:55 PM, Mario G <mario_fs@mgtech.com> wrote:

No problem with IPV4 for years. Changed Yealink and Bria phones to IPV6, they still work fine including getting VM. But with IPV6 FS only sends a NOTIFY 1 out of ten times so the phones don't set MWI. A sip trace during registration shows everything identical between MWI and non-MWI working except that when MWI does work a NOTIFY is sent to the phone. The NOTIFY, and only the NOTIFY, references IPV4 addresses in “From, To, Message-Account” and I wonder if that may be the cause. I tried to change Message-Account to IPV6 but it gets truncated at the first colon, I opened jira FS-9428 for that. I am wondering if this problem is one for Jira too or a config issue? Anyone run into this or have a suggestion? Thanks.

Mario G