Page tree
Skip to end of metadata
Go to start of metadata

Last update: 17 November 2010

Broadvoice.com

Dialplan Codec Selection

  • Incoming and Outgoing calls work with UDP only.
  • As of 12 February 2008 Broadvoice is not RFC 3261 compliant. Broadvoice does not support the usage of TCP within their SIP stack. This means you have to set the absolute_codec_string channel variable to PCMU.
  • Chris 11:24, 31 January 2008 (EST) It was brought up on the IRC channel, Broadvoice apparently isn't following the SIP specifications for MTU packet sizes.

DNS SRV and Broadvoice

Broadvoice uses DNS SRV records to provide failover to redundant geographically disparate SIP proxy servers located across the US. FreeSWITCH supports  DNS SRV records.

The use of DNS SRV for failover seems to occur many times during the course of each day, presumably as part of a load balancing function within the Broadvoice network. Having initially attempted to follow the DNS "fix" documented below I kept getting registration errors at regular intervals each time broadvoice failover mechanism kicked in.

The following configuration seems to work reliably. The proxy should use the nearest broadvoice server to you:

Note that you MUST use the SRV record which contain a dash within the host name. These DNS SRV records are not directly "pingable" but can be resolved by performing an "nslookup" with a 'set type = SRV' first.

Alternative DNS method

  • The following method is suggested IF you experience difficulty using DNS SRV. It is a work around that seems to cause frequent registration errors.

  • Broadvoice has a funny DNS situation, use the following fix. (Broadvoice kept on returning 403 Forbidden messages until I modified my DNS entries within the hosts file)