SIP-trunking with Routit (Broadsoft/Broadworks) part 2

This week I've implemented a SIP-trunk at a customer site. This trunk is connected to a Cisco UC540. I could use almost all settings which I used in my lab setup. Before configuring the trunk I wasn't sure if the line setup would work with the CUE (VM-module) embedded in the UC540.

The customer has a simple IP-VPN connection with Routit, this means Routit supports a single IP-sgement with a maximum of 255 hosts and no routing of other customer IP-segments. I wasn't to sure if this was enough or if I had to use NAT because the embeded CUE lives on a different IP-segment. This UC500 was manually configured instead of with CCA. This meant some commands which CCA injects were missing. The following commands made the CUE work with the SIP-trunk without NAT:

voice service voip
 no supplementary-service sip moved-temporarily
 no supplementary-service sip refer

The ACME SBC, which Routit uses, apparently does not support SIP REFER of MOVED-TEMPORARILY (302). 

Next the Dial-peer for the CUE

dial-peer voice 999 voip
 description *** VOICEMAIL ***
 destination-pattern 999
 b2bua
 session protocol sipv2
 session target ipv4:10.0.0.1
 voice-class sip outbound-proxy ipv4:10.0.0.1 
 dtmf-relay sip-notify
 codec g711ulaw
 no vad
!

The Dial-peer has to have it's own outbound-proxy otherwise it will try to contact the proxy defined in the Voice Serve Voip > SIP section. The B2BUA statement is needed so the UC540 uses it's own address for communication with the ISP SBC instead of the IP-address of the CUE (which in this case will result in no connection because the IP-segment of the CUE can not be routed towards the SBC of the ISP.

The trunk is directly connected to the Voice VLAN of the customer. If routing is needed, you have to upgraded the line to a IP VPN Plus.