Issues with MWEB SIP

[acidrain]

Hi Guys,

Is anyone able to confirm if there are issues with MWEBs SIP?

Only way I can tell it's mweb is the provider we get it through setup the system and when I do a dns lookup on the ip it comes up with sip.voip.mweb.net.

Now at the moment the pbx is registering the destination as unreachable yet the provider is saying everything is working... which I am not so convinced seeing as pinging the IP i get nothing... and when i do get a response its 2000ms+

 

[breedenet]

When we tested MWEB, they told us to ping the IP 196.28.95.20, as sip.mweb.net blocks ping requests. So give that a try to test the latency. On my connection the pings are between 45ms and 125ms.

 

[acidrain]

OK that ip pings fine but then here is something interesting.

 10   312 ms   340 ms   334 ms  tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
 11   370 ms   376 ms   419 ms  vl-11.vic-hscore-1.mweb.co.za [197.80.5.237]
 12   269 ms   302 ms   330 ms  197-80-96-54.jhb.mweb.co.za [197.80.96.54]
 13   363 ms   387 ms   382 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 14   441 ms   368 ms   333 ms  197-81-229-17.jhb.mweb.co.za [197.81.229.17]
 15  1849 ms     *        *     sip.voip.mweb.net [196.28.95.12]
 16  1970 ms  1986 ms  ^C

Shouldn't that 196.28.95.20 ip be in the trace if its relevant to the SIP? Kinda pointless pinging an IP thats seperate from the sips network.

Im going to wait for the line to come up again and see if the ping still responds the same but for now, there looks like a problem.

Also here is a screenshot from my line status:

Now this issue has been coming and going for the passed week or 2 and have just switched to another ISP, and still the problem persists.

 

[vitchie]

Do you connect through a router that NAT's? If so, manually try and reset the connection in your firewall. If you can't find that, reboot the router. SIP and NAT over dynamic IP doesn't play well together, especially on a Mikrotik router. If only MWEB can offer IAX2 trunks.

 

[acidrain]

Ok I see what you mean.

Ye the Tik handles the internet and all internal IP's are nat'd through. Ok so basically SIP prefers to actually have the pbx directly connected to the internet?

Thats going to suck the big one if thats the case.

 

[vitchie]

Got my working through a tik, works well. Disabled the SIP helper, some manual firewall rules and a script that monitors the ADSL connection and flushes all the firewall connections to mweb's sip server when the ADSL ip/connection state changes.

 

[acidrain]

Cool thanks for the info. So far it seems my isp account allows for multiple sessions so I'm able to just have the PBX dial out directly and avoid any nasty natting.

 

[breedenet]

With mikrotik's they sometimes hold a session op port 5060, then changing the port to 5061, or 5062 fixed the problem.

 

[acidrain]

Thanks for the advice breedenet.

Currently my dsl account allows for more than one connection so I've got the tik handling the internet part of the office and then ive setup another pppoe on the pbx which will handle purely voip.

For now this seems to be working out quite nicely.