sundance-communications.com/forum Forums TDM Business Telephone Systems Toshiba Telephones & Systems CIX40 IP Phone "Make Busy"

Hey all, I recently installed a CIX40 at a customers and they have one remote IP phone in addition to the four office digital phones. After struggling with the existing router to get a public IP working we replaced the router with a Draytek 2700VG model. This is programmed with the default ISP connection which provides a fixed IP that they use port forwarding on to route to their servers etc. I should also point out, in case it makes any difference, the Draytek router is being used to provide two VoIP lines connected to the phone system on PSTN ports.

This router also supports a second IP address for the router, which we have set up with a public range. This all appears to be working fine and there is no firewall active. The routers second IP address (public) is the first useable of the range, xxx.xxx.xxx.201 with a subnet of 255.255.255.248, the phone system I have set up as xxx.xxx.xxx.202 and the IPU card as xxx.xxx.xxx.203. I can get into system programming remotely no problem, I can ping the IPU card remotely no problem and the 2020 IP phone will log on no problems, but the screen of the phone shows Make Busy on the bottom line (top line shows extension name and number).

The phone is useless and will not work at all. When I first set this up I tested the phone on the internal network (with the IPU setup with an internal network address) and all worked fine, so I know the card and the phone are good.

Obviously there is something being blocked in the setup when the phone is running externally but I have no idea what or where to look. I have WireShark setup and running on my lappy with both it and the phone connected to my home network at the moment and can see lots of messages back and forth between the phone and the IPU, but I have no idea what to look for to see why its not working.

Anyone got any ideas to throw in?

Thanks in advance, Dave.

Does the router have SPI built in? I have had certain brands of routers that do, and will render an IP phone useless. Sometimes you can turn it off and it will work immediately.

I have always had luck with the TrendNet (https://www.trendnet.com) brand of routers.

Also, have you tried the IP phone at a different location, incase the ISP is blocking certain VoIP traffic ports? You can also try to setup the IPU with the public IP, then connect the IP phone to a DHCP switch.

Is there a chance the remote user plugged the handset cord into the headset jack,,,I had a few installs that worked fine on site but when we sent the phone to the remote they plug the handset into the headset jack

Thanks for the replies guys, I have the phone at home now to test, on a different ISP to the customers home and same problem. Just looked through the customers router and the firewall is pretty flexible, but according to the manual it only affects the NAT'ed section (the section running on DHCP). I have a seperate routed subnet running through it with an external IP address for both the procesor and the IPU. I can connect for programming fine, I can ping the IPU fine. Just to be sure I have gone through the firewall settings and the SPI can be turned off, and unfortunatley it already was (that I think was the last lot of playing I did - turned off every option int he firewall, including DoS prevention, SPI, content filters, IM blocking, P2P blocking, call filters and data filters). So everything is off, have now tried two totally different routers and tried the phone at two different locations on two different ISP's!

So, I guess either there is something wrong in my setup (although I had the phone working on an internal network originally to test it) or the ISP the phone system is connected to is blocking something. Might have another look at them and see if I can find anything.

I was looking aver a trace with Wireshark last night and I was not able to see any packets being sent from the phone not getting through, but then I was not really sure what I should be looking for. Is anyone any good with looking at a Wireshark trace? If so I can record one and PM it to you.

Going mad here!

You need to put your IPU on a static public IP, ahead of any firewall, routing or NAT - then you'll have a clean test. I usually have the customer get a 4 port hub, to plug in before all the internal network. NAT has always been a problem with the Toshiba IPUs.

I can look at the WS data, if you'd like - but I bet putting it ahead of the rest of the network will get your connectivity.

While I was taking a class at Toshiba, they were showing us how to get the IP card to work through a Sonicwall router. For some reason, we could not get 2 systems to connect when they were both behind a sonicwall, even tho the IP addresses were full routed though it.

As MacOSX said, if there is any NAT on the IPU side, it will not work. You have to have a public IP address (as oyou said you have). It should work through a router that passes the public IP address through it, but there still could be something in the router blocking it.

On the phone side, some routers will cause a problem, primarily with SPI firewall. Linksys WRT54G is a good example of one you do not want to use becasue on an issue with SPI firewall.

The phone got all the way past the registration part, but then gets stuck just before becoming operational. That tells me that the phone can see the card and register, but doesn't complete the final step.

Most of our setups are the same as MacOSX mentioned, putting a small data switch in from of the routers or firewalls ans exposing the IP card to the internet. If the router also connects the T1, then this may be a little diffcult.

With wireshark, one thing to look far is that there is an ACK for each TCP signal sent, and that all the UDP signals make it though. There are a few ports used in the setup process. Did you tap near the phone system? It looked like you sniffed on the phone side. If there is a signal sent from the phone that is blocked by your router you may not even know its being blocked. You may have to compare it to a phone that connects properly, or see if you can make another sniff on the other side to see what, if anything, gets blocked.

Port info has been posted in the past. Look here:
https://www.sundance-communications.../ubb/get_topic/f/11/t/003100.html#000003
Which is also on FYI, which you should have access to if you are working for a Toshiba dealer.

Ok, final update for anyone who was watching...

Firstly, turns out my version of eManager was to old and had changed the GIPU to an LIPU... anyways, got that sorted and the Make Busy problem went away.

Now we had one way speech, audio from the handset out was fine, but audoi from the system to the handset was being blocked.

After much searching with the local Toshiba support on the phone, turned out the 802.1p tagging was switched on for the GIPU card, and the Draytek 2700VG router currently in use at the customers site does not recognise the 802.1p tagging (and seems to have no way of turning it on) so was blocking the speech packets!!!

All now working so I can start growing my hair again

Thanks for the update!