Community discussions

MUM Europe 2020

Search found 5 matches

by ntwkedout
Sat Aug 10, 2013 4:58 am
Forum: General
Topic: v6.2 released
Replies: 247
Views: 90679

Re: v6.2 released

SIP connections don't work in 6.0 and 6.1 and 6.2

They work good in 5.25
Did you do what I said worked for me in my last post? I am guessing you did not. I spent the last 2 days troubleshooting why sip would not work on 6.2 and it was the service ports. Disable them.
by ntwkedout
Sat Aug 10, 2013 2:42 am
Forum: General
Topic: v6.2 released
Replies: 247
Views: 90679

Re: v6.2 released

IPSEC Mikrotik RB493G to cisco ASA 5520 v5.25 everything is working Upgraded to 6.2 and SIP phones stopped registering but all other traffic seems to be working. Downgraded back to 5.25 everything started working again. I have been troubleshooting after hours and cant see why the phones stopped wor...
by ntwkedout
Mon Aug 05, 2013 1:33 am
Forum: General
Topic: v6.2 released
Replies: 247
Views: 90679

Re: v6.2 released

IPSEC Mikrotik RB493G to cisco ASA 5520 v5.25 everything is working Upgraded to 6.2 and SIP phones stopped registering but all other traffic seems to be working. Downgraded back to 5.25 everything started working again. I have been troubleshooting after hours and cant see why the phones stopped work...
by ntwkedout
Sun Aug 04, 2013 12:44 am
Forum: General
Topic: v6.2 released
Replies: 247
Views: 90679

Re: v6.2 released

IPSEC Mikrotik to Cisco ASA Working fine on 5.25, Upgraded to 6.2, Became very excited thinking everything was working fine, Then Noticed SIP phones were down. Downgraded back to 5.25 everything is back up and working. Other than that it seemed from the IPSEC debug in the log that it was working fine.
by ntwkedout
Sun Aug 04, 2013 12:35 am
Forum: General
Topic: v6.2 released
Replies: 247
Views: 90679

Re: v6.2 released

IPSEC Mikrotik to Cisco ASA Working fine on 5.25, Upgraded to 6.2, Became very excited thinking everything was working fine, Then Noticed SIP phones were down, Ran a torch on WAN interface to find that return traffic was being processed under the WAN IP and not returning network ip. Almost like the ...