Just wanted to post here as it may help users who have or will be upgrading to the new v18 MR1 rls, basically i updated a clients V18 yesterday with the mr1 sig file and everything was fine as usual but in the middle of the day at 1130am I was just starting a config change on this XG instance which wasn't anything relating to SIP only a new Int port setup and a new DHCP server for that new network. But all of sudden i got a phone call from the client as they had just lost there SIP trunk from there onpremise Avaya IPOFFICE 500 which i dropped what i was doing to troubleshoot this new issue, first thing i did was rolled back all the changes i had made on the XG instance which didnt resolve the problem as we still were unable to get successful Sip registration. Next i contacted there Sip trunk provider who had a look there end and called me back to say there wasn't anything wrong there end and no other had changed recently either so it came back to an on premise issue, well 3 hours later i finally got round to checking the XG console menu 4 to check the logs there and settings. Well i got to the system-modules including the SIP helper module id always kept disabled as it had created problems in the past so that was how it had stayed and hadnt changed in anyway since v16 well to my surprise it had enabled itself somehow how ive no idea as it certainly wasn't from our end so all i can put it down to would be the MR1 update just under 24hrs previously even though the office did have SIP access from 0800 - 1130 so it had to been self enabled via the mr1 update and then a config change must of tripped the old problems we had ages ago using that helper but i can only guess as to this for certain. Like i say i only thought it may be related as not once has any change or update since v16 caused the same thing which is to change the helper modules preset setting.
But I just thought I post here in case any users updated or updating to the new v18 MR1 rls might suddenly find they see SIP related issues with connectivity type errors to check there XG instances Admin Console menu 4 and check your SIP Helper Module is still in its last known set state and if its not change it back and see if that fixes your SIP issue??
Also if Sophos staff read this could this be looked into pls and let us know if this SIP helper module does re enable itself after updating with the latest v18 MR1 sig file id be much obliged to know one way or the other if my guess here was infact related to this update or it was caused somewhere else it would certainly answer my questions at least.
But glad to see MR1 back! keep up the good work Sophos.
Thanks
KL
This thread was automatically locked due to age.
