Vodafone SIP Trunk Configuration Guide | UK

[KaterinaK_3CX]

This guide will walk you through creating and configuring a Vodafone SIP Trunk with 3CX.

Take note of the below special configuration requirements for Vodafone:

• Enter the main trunk number as E164.

Read the guide.

 

[NovaPixie]

Urgent Attention Required: Vodafone SIP Trunk Compatibility Issue

Dear Team,

I am writing to urgently request your assistance with an issue regarding the Vodafone SIP trunk service.

Upon thorough examination, I have determined that the fault does not lie with my SIP trunk provider, as the service operates faultlessly from my end. It appears that the dashboard provided by your service is somewhat basic, potentially obscuring more complex settings from the user's view. I have verified that there are no inherent technical issues with the SIP trunk itself. However, I have noted deviations in my configurations from the default settings on your dashboard. For example, I utilise 'bbvoice.vodafone.co.uk' as my Outbound Proxy, in contrast to the standard 'entvoice.vodafone.co.uk'. This suggests that modifications on your end might be necessary to address this issue, particularly as other default settings may also be misaligned.

I would be most grateful for your prompt response to this matter.

I should clarify that this message is not merely a request for support, but rather a call for enhancement and better compatibility with my Vodafone trunk settings.

The issue seems to stem from your dashboard; it is a systemic fault rather than a need for technical support.

For reference, the Vodafone SIP trunk functions impeccably on-premises with my current device configuration:

Grandstream HT801: https://ce.uk/HT801.pdf
DrayTek Vigor 2862ac: https://ce.uk/Vigor2862.pdf

Thank you for addressing this as promptly as possible.

 

[YiannisH_3CX]

Hello @NovaPixie

Can you please explain what issues you are facing though? You mention compatibility issues but in what area? Are you having issues registering? Are you having issues making calls? Do you have DTMF issues?
What issues exactly are you facing?

For example, I utilise 'bbvoice.vodafone.co.uk' as my Outbound Proxy, in contrast to the standard 'entvoice.vodafone.co.uk'.

bbvoice might be a different product entirely so consult with your provider regarding this. Also the proxy option is available for editing.

 

[NovaPixie]

@YiannisH_3CX Unable to register

 

[YiannisH_3CX]

Our team had a quick look and Vodafone is not replying to the registration messages we are sending them, Plus you should confirm that you do have the correct product which is supported by 3CX. You should definitely contact Vodafone regarding this.

 

[NovaPixie]

@YiannisH_3CX I must admit, Vodafone hasn't made this straightforward. I've managed to get it working on some devices, but not all, due to the complexity. Additionally, some devices lack the necessary options.

Below are the guides I've compiled and uploaded, which detail the requisite settings.

Grandstream HT801: https://ce.uk/HT801.pdf
DrayTek Vigor 2862ac: https://ce.uk/Vigor2862.pdf

SIP Transport Protocol: UDP, Port 5065
RTP Port: 10000
Mandatory use of Vodafone DNS for lookup: 90.255.255.91 / 90.255.255.255.255
DNS Mode: SRV

There are additional factors, some of which may be essential or simply implemented to emulate what they require, such as SIP User-Agent Vox 3.0, among others.

 

[YiannisH_3CX]

Now I definitely think you have the wrong product which is not compatible with 3CX SMB.

Also their UDP records indicate that they want traffic to port 5060 so I am not sure why you are using port 5065

 

[NovaPixie]

@YiannisH_3CX While I don't possess the complete technical understanding as to why I need to use the SIP port 5065, what I can assert with certainty is that my system is operational. This suggests that the network's configuration might extend beyond conventional parameters.

You've mentioned compatibility issues, yet the SIP Trunk in question is supplied by Vodafone, which, to my knowledge, is within the range of providers you accommodate. Could you clarify the nature of the incompatibility you're referencing?

 

[NovaPixie]

I can assure you that if you successfully implement this, you will attract a significant number of new customers. With BT phasing out the PTSN and providers pushing customers towards VoIP, there's a growing market of individuals keen to utilise their new digital landlines within the realm of VoIP. 3CX would be precisely what I, and evidently others, are seeking.

 

[YiannisH_3CX]

You've mentioned compatibility issues, yet the SIP Trunk in question is supplied by Vodafone, which, to my knowledge, is within the range of providers you accommodate. Could you clarify the nature of the incompatibility you're referencing?

We interop a specific product from Vodafone and we build a template for that specific product. When you select the Vodafone template from the list you are using a pre-configured set of settings hence the lack of configuration in the UI. We test and supply these templates so that trunks work out of the box.
If you are using a different product /SIP Trunk from Vodafone then this set of settings won't work for you.

 

[NovaPixie]

Ah, that's clear now. I reckon Vodafone is unlikely to be keen on collaborating in this matter, as it doesn't seem financially advantageous for them. It could be beneficial for 3CX, of course, but without Vodafone's backing, it would result in an unproven system vulnerable to changes by Vodafone, rendering it technically unfeasible. I've already been in touch with Vodafone, but you might want to have a look at this forum. It gives an insight into the users who are exploring ways to utilise Vodafone's VoIP service, especially now that traditional landlines have been phased out and users are essentially being compelled to use the Vodafone router, which many of us, myself included, are rather reluctant to do.

Link to Vodafone Forum Discussion

 

[YiannisH_3CX]

We are in constant touch with Vodafone and we are working with them to improve the offering .We just support a specific product. We have communication with all our supported providers so we can resolve issues and maintain interoperability.

 

[NovaPixie]

Brilliant, let me know when you can connect to Vodafone's Digital Voice service

https://support.vodafone.co.uk/Broadband/Pro-Broadband/1751006322/What-is-Digital-Voice.htm

 

[NovaPixie]

For guidance, the following settings can be employed with Vodafone's Digital Voice on a Grandstream HT801, particularly when using a dynamic IP. These configurations can also serve as a point of reference for different devices and arrangements.

Open Ports: 5065 (UDP), 10000 (UDP)
Disable ALG (Application Layer Gateway)

STUN server is: stun.l.google.com:19302
Primary SIP Server: resvoip.vodafone.co.uk
Outbound Proxy: xbn.Z4.bbvoice.vodafone.co.uk
NAT Traversal: STUN
SIP User ID: voi001234567
Authenticate ID: voi001234567
Authenticate Password: xxx
DNS Mode: SRV
Primary IP: 90.255.255.91
Backup IP1: 90.255.255.255
Unregister On Reboot: Instance
Outgoing Call without Registration: No
Registration Expiration: 1 (minutes)
SIP Registration Failure Retry Wait Time upon 403 Forbidden: 180 (seconds)
Local SIP Port: 5065
Local RTP Port: 10000
Transfer on Conference Hangup: Yes
Remove OBP from Route Header: Yes
Allow Incoming SIP Messages: Yes (no direct IP calling if Yes)
Use P-Access-Network-Info Header: No
Maximum Number of SIP Request Retries: 4
SIP User-Agent: Vox 3.0
Disable Reminder Ring for DND: No
MWI Tone: Special Proceed Indication Tone
Dial Plan: { 10[015] | 11[129] | 999 | 11[68]xxx | 1[45]7[1-2] | 08001111 | 0845464x | 0[1235789]xxxxxxxxx | 1410[1235789]xxxxxxxxx | 14700[1235789]xxxxxxxxx | 00xxx. | x+ | \+x+ | *x+ | *xx*x+ }
Enable 100rel: Yes
Add Auth Header On Initial REGISTER: Yes
Preferred Vocoder: PCMA, G729, G729
SLIC Setting: UK
Caller ID Scheme: SIN 227 - BT

 

[NovaPixie]

Now I definitely think you have the wrong product which is not compatible with 3CX SMB.

Also their UDP records indicate that they want traffic to port 5060 so I am not sure why you are using port 5065
View attachment 39377

For anyone else reading this thread, to clarify the usage of port 5065, there appears to be a mix-up between the local SIP port and the provider's SIP port.

In my previous note, I mentioned "SIP Transport Protocol: UDP, Port 5065". This typically refers to the local SIP port. It implies that our device or system uses UDP for SIP communications and is configured to listen on port 5065 for incoming SIP messages.

The specification of a particular port, such as 5065, usually pertains to local configuration, not the provider's settings. Standard provider SIP ports, like 5060 or 5061, are often outlined in their service documentation or indicated in SRV records, rather than in our local settings.

Local SIP Port: Our setup, as instructed by Vodafone, utilises port 5065. This is the port where our device expects to receive incoming SIP messages. It's vital to ensure this port is correctly configured and open on our router to enable successful SIP traffic handling.

Provider's SIP Port (SRV Record): Typically, this is port 5060 or 5061. The SRV record in the DNS specifies the correct port for our SIP client to connect with the provider's server.

 

[TechyTim]

For anyone else reading this thread, to clarify the usage of port 5065, there appears to be a mix-up between the local SIP port and the provider's SIP port.

In my previous note, I mentioned "SIP Transport Protocol: UDP, Port 5065". This typically refers to the local SIP port. It implies that our device or system uses UDP for SIP communications and is configured to listen on port 5065 for incoming SIP messages.

The specification of a particular port, such as 5065, usually pertains to local configuration, not the provider's settings. Standard provider SIP ports, like 5060 or 5061, are often outlined in their service documentation or indicated in SRV records, rather than in our local settings.

Local SIP Port: Our setup, as instructed by Vodafone, utilises port 5065. This is the port where our device expects to receive incoming SIP messages. It's vital to ensure this port is correctly configured and open on our router to enable successful SIP traffic handling.

Provider's SIP Port (SRV Record): Typically, this is port 5060 or 5061. The SRV record in the DNS specifies the correct port for our SIP client to connect with the provider's server.

Hi NovaPixie,

I know this is an old thread, but you're talking about Vodafone's Broadband Voice Proposition and not their Enterprise offering for voice.

entvoice.vodafone.co.uk
bbvoice.vodafone.co.uk

are not the same thing and this is where you would have been having problems as 3CX has been implemented with Vodafone's Enterprise Voice solution for a few years.

Hope this helps others that come across this post.