This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Choking on external sip connection

We have an ASG running 7.506 ( waiting for 7.507 until Friday night).

In network, we have a 3Com V3000/NBX running sip and v6.5.22. We also have some 3Com 3108 802.11 wireless VOIP phones that work fine in network.

If we try to take them on the road, we get stuck on "registering".

Sip server is correctly pointed at the 3Com, clients that are correctly identified, We have an external IP that is pointed to the 3Com, port 5060UDP is open, passwords are checked, etc.

Are we missing anything? We have figured out everything else so far reviewing this forum. The 3Com forum hasn't been able to help.

thanks astaro.

This thread was automatically locked due to age.

Parents

0 BAlfson over 15 years ago

Hi, mswann60, and welcome to the User BB!

Although we do see folks from Astaro here on a regular basis, each one does so on his/her own time - no Astaro employee is paid to participate here.

Not sure what your situation is, but I would suggest going to 7.507 this morning.

What is new here? NBX? Wireless phones? Astaro?

"We have an external IP that is pointed to the 3Com" - by that, do you mean that you have a DNAT rule in place? Please show a picture of it.

Is there anything in the Packet Filter log or the Intrusion Prevention log that might help understand what's happening?

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 RFCat_vk_01 over 15 years ago in reply to BAlfson

Hi,
re do your sip service to cover both TCP and UDP. Some devices and servers use TCP rather than UDP.

Regards

Ian M
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 RFCat_vk_01 over 15 years ago in reply to BAlfson

Hi,
re do your sip service to cover both TCP and UDP. Some devices and servers use TCP rather than UDP.

Regards

Ian M
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data