Belgacom BBox2 – VoIP Support
Small rant (and solution) about the Belgacom B-Box2 routers their VoIP Support. Please note that this post has nothing to do with the FXS ports on the device itself. I will explain how to implement VoIP support on the LAN network.
By default the Belgacom BBox2 modem will filter UDP 5060 on the LAN so registrations will pass but RTP traffic will not be forwarded leading in uni-directional voice audio. This behavior is for the SIP server in the device itself to make the two FXS ports connect to a VoIP provider; only for those two FXS ports.
This is an understandable default setting from the ISP’s point of view; but really sucks for an Enterprise / B2B customer using VoIP on the LAN.
All you need to do is change the SIP port in “Advanced Settings” – “Telephone” from 5060 to another port. I changed it to 5080 and rebooted the device.
After this small modification SIP registrations and RTP audio will be correctly forwarded.
| tags: 
[...] Here is the original: Belgacom BBox2 – VoIP Support | Geert's blog – Casu Consulto [...]
[...] Original post: Belgacom BBox2 – VoIP Support | Geert's blog – Casu Consulto [...]
[...] Belgacom BBox2 – VoIP Support: Small rant (and solution) about the Belgacom B-Box2 routers their VoIP Support. [...]
Thank you so much! You really helped us a lot. We had problems with this for a long time.
[...] Belgacom BBox2 – VoIP Support | Geert’s blog – Casu Consulto [...]
So are you supposed to change all ports to 5080? Does that mean you can no longer use the FXS ports with providers that expect to be contacted at 5060?
It means for the outbound SIP source port; aka YOUR_IP:5080 if you have multiple devices that will become YOUR_IP:5081 YOUR_IP:5082 etc…
You still need to register to YOUR_PROVIDER:5060 and it works as expected. I have successfully tested this up to 6 devices by just changing that one setting.
Please excuse my ignorance, but I have been fighting over this phenomenon for over 6 months. So in “advanced” “telephone” there are several possibilities to change ports:
1) upper right: port default which shows 5060
2) outbound proxy port which shows 5060
3) rigistrar/sip domain port which shows 5060
which ones do I have to change?
I tried changing just the sip domain port but it would always default back to 5060 after the reboot.
Geert:
Is this what I have to do, in order to get my VOIP working. I have not been able to use my ATA 2100 Link system, and it is reall frustrating leaving the computer on to receive phone calls.
I really do not understand all the technical jargon, but if I understand you correctly this is all I have to do to get VOIP?
During more that one year it worked so for me since 2 days, when I change the port 5060 on the bbox 2 and I reboot, the bbox2 reconfig her self on 5060 after reboot…why ??? firware update ??? My dream is that cisco made a router wirking with BGC VDSL and BGC TV….to replace this shi…. bbox2!
i have changed only the upper right: port default which shows 5060 into 5070 ore another value and it works fine thanks !!!
Hi,
wondering if you can help me too with a VOIP issue.
I just swapped to vdsl2 and b-box2 with Belgacom ; before that I was using normal phone plugged in a linksys spa3012 (fixed ip )to connect to eutelia voip provider, though a cisco 800 adsl router lan port.
I have been playing with the config of the b-box since several days, and now I am finally able to start calls from my phone, but still cannot receive any.
The spa is connected to pc port 2 and has fixed ip 192.168.1.6 (tried .10, .100 and .200 too)
so far I have tried the following :
- disabling b-box2 telephony and changing sip ports to 4080
- disabling vlan 20 (voip)
- put the spa fixed ip in dmz
- set port triggering rules
- set lan servers to open the ports to my spa fixed ip (UDP 5060, range for UDP for rtp, UDP 8000 for rtpc and also 3745 for eutelia stun server)
- set the static ip on the lan bridge for my spa (weird it always reports as expired, as the lease is marked to end on 1970/01/01 00:00:00)
all these alone or combined…still, I cannot receive any call. It seems to me that lan server or dmz still do not open any ports : if I test with any web port scan from outside, all the ports are still closed….
Do you have any suggestion before I quit the task and move to set the B-box in bridge mode in front of my old cisco router (thus losing wireless) ?
Thank you in advance, Stefano