Do you have more info for this ? How you check the header (Packet capture) ? Do you have the capture for the SIP message for firmware 7.1.0 and 7.0.2 ? Can you share here ?
Changes make in “running” firmware (system boot up firmware) will not apply to the second firmware partition. Configuration migration only happen upon firmware upgrade, hence any configuration change after the firmware upgrade for the “running” firmware (system boot up firmware) will not apply to the second firmware partition when you reverted the firmware.
2 Likes
After an unexpected reboot of our 580, this line was in the SIP header…
So the question is would it normally be removed or added…?
Authorization: Digest username=“rddigiumg100two”, realm=“asterisk”, algorithm=MD5, uri="sip:[email protected]", nonce=“13bafca3”, response=“296e113423344acd27bb3b30967de0ea”
I think the question that I am asking is something like this.
My SIP traffic is internal to the network created by the peplink routers.
So sending the SIP traffic out a SF tunnel would that be considered NAT’d if the WAN port is not?
Or
Having an outbound policy that has a WAN port and a SF tunnel could one be considered NAT’d and the other one not?
Thanks for the explanation of the configuration. Can you upload a configuration from 7.1 to a device running 7.0.2?