CUBE Sip trunk registration with global outbound proxy

[Marcel Tempelman]

Hello,

One ISP we use a lot for SIP trunking requires the SIP trunks to be authenticated. For this we have a working config. The only thing that nags a bit is that the registration does not work without putting an outbound proxy under voice service voice > sip.

This is basically the config:

voice service voip
 sip
  localhost dns:customer.ourname.voipit.nl
  outbound-proxy ipv4:89.146.63.251
!
dial-peer voice 1 voip
 description Uitgaand SIP Trunk
 translation-profile outgoing SIP-Uitgaand
 destination-pattern 0T
 session protocol sipv2
 session target ipv4:89.146.63.251
 voice-class codec 1
 dtmf-relay rtp-nte
 no vad
!
dial-peer voice 100 voip
 description Inkomend SIP Trunk
 translation-profile outgoing SIP-Inkomend
 destination-pattern ^123456[1-4].$
 b2bua
 session protocol sipv2
 session target ipv4:192.168.0.20
 voice-class codec 1
 voice-class sip outbound-proxy ipv4:192.168.0.20
 dtmf-relay rtp-nte
 no vad
!
sip-ua
 credentials number 1234578 username ThisUser password ThisPassword realm customer.ourname.voipit.nl
 authentication username ThisUser password ThisPassword
 registrar dns:customer.ourname.voipit.nl:5060 expires 3600
 sip-server dns:customer.ourname.voipit.nl:5060
 connection-reuse
 host-registrar
!

Drawback of this config is that I have to add an outbound proxy setting in every dial-peer facing the Callmanager nodes. The dial-peer config in this example has to be updated to look a bit more like best practice but it works.

I found some examples but these were also using the 2 step dial-peer design, I do not know if this is a requirement when you want to drop the global setting for the outbound proxy.

Any ideas ?

Regards,

Marcel.

[Slavik Bialik]

Hi,

You don't have to put it in the "voice service voip" section, you can configure it per dial-peer.

Here's an example from one of my gateways:

dial-peer voice 1000 voip
 description OUTBOUND DP to PSTN
 session protocol sipv2
 session target ipv4:<sip-registrar-ip>
 session transport udp
 destination e164-pattern-map 1000
 voice-class codec 1  
 voice-class sip associate registered-number <sip-username>
 voice-class sip outbound-proxy ipv4:<sip-registrar-ip>
 voice-class sip bind control source-interface GigabitEthernet0/1
 voice-class sip bind media source-interface GigabitEthernet0/1
 dtmf-relay rtp-nte sip-notify
 no vad


sip-ua    
 credentials username <sip-username> password 7 <pass hash> realm <realm-name>
 registrar ipv4:<sip-registrar-ip> expires 60 auth-realm <realm-name>

[Marcel Tempelman]

Hello Slavik,

thank you for the example ! I am going to try this.

With kind regards,

Marcel Tempelman.

[Marcel Tempelman]

Hello Slavik,

too badd, it did not work. If you do not configure the outbound proxy at global level no attempt at registering is coming from the cube. See also this discussion:

https://supportforums.cisco.com/t5/ip-telephony/cube-alternative-outbound-proxy/td-p/2454543

I'll try this in the CUCM facing dial-peers:

 no voice-class sip outbound-proxy

Regards,

Marcel.

[Slavik Bialik]

Strange, in all my configurations (I have few gateways with SIP registration) I'm not putting it in the global level of sip. Can you please share your whole GW configuration?

[Marcel Tempelman]

Hi,

I found the multi-tenant option in the cube docs. This was the key to the solution. I move the outbound proxy settings to the voice class tenant config

voice class tenant 1
 localhost dns:customer.ourname.voipit.nl
  outbound-proxy ipv4:89.146.63.251
!
dial-peer voice 1 voip

 voice-class sip tenant 1

!

The docs talk about an 'authenticate' command but 16.6.1 does nt include this command. For this the authentication part had to stay at the SIP-UA part (normally you would put them under the tenant config).

Regards,

Marcel.

[itsupport0172]

Dear Marcel Tempelman,

Can you please share complete configuration of your cube

[itsupport0172]

Dear Slavik Bialik,

Can you please share complete configuration of your cube