Some SIP providers prefer to work with INVITE field, while CISCO CUBE traditionally works with From: and To: fields.
Let’s take MSN provider as an example.
An incoming call header looks like this:
In this case, login is 48879800, and it is contained in INVITE field only.
Cisco translation-profile and translation-rule can only operate with numbers, and the complex header in To: field complicates the situation.
You can use sip-profiles to copy the number from INVITE field to To: field.
The structure should be the following:
voice service voip
sip
sip-profiles inbound
!
voice class sip-profiles 10
request INVITE sip-header SIP-Req-URI copy "sip:(.*)@" u01
request INVITE sip-header To modify ".*@(.*)" "To: voice translation-rule 10
rule 1 /^48879800$/ /1401/
!
voice translation-rule 20
rule 1 /^8\(..........$\)/ /+7\1/
!
!
voice translation-profile ITSP_Incoming
translate calling 20
translate called 10
!
dial-peer voice 1 voip
description incoming from MCN-1
translation-profile incoming ITSP_Incoming
session protocol sipv2
session target sip-server
incoming called-number 48879800
voice-class codec 1
voice-class sip profiles 10 inbound
voice-class sip bind control source-interface GigabitEthernet0/0/0.300
voice-class sip bind media source-interface GigabitEthernet0/0/0.300
dtmf-relay rtp-nte digit-drop
no vad
!
dial-peer voice 500115 voip
description To CUCM
preference 5
destination-pattern 48879800
session protocol sipv2
session target ipv4:10.7.20.251
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0/1.200
voice-class sip bind media source-interface GigabitEthernet0/0/1.200
dtmf-relay rtp-nte digit-drop
ip qos dscp cs3 signaling
no vad
!
Then the number 48879800 can be sent to CUCM.
In the end, the call will look like this:
Lets talk.