PSTN calls over SIP Line

[farispv]

Dear Team, 
Am facing an issue related to out going call over SIP Line. 
I have SIP Trunk configured on our CUCM and the ISP Allowed range of SIP Direct line 7720 to 7730. [30 Extension]
When we place the call from the extension number which fall in that series the outgoing calls works fine to external number 

the outgoing number is showing in SIP range. 
However, if I call from the extension which starts the after the SIP range [7731], the outgoing calls are not getting placed and its failed with an error "cause=28" incomplete number. sure the call may disconnected as its out of range. 

In order to facilitate the PSTN calls i have tried adding an translation rule like below, but the calls are not getting placed and the rule not matching it. 
Kindly advise & guide me where i have mistaken in the configuration. 

Thank you. 

Requirement :- All the calls need to worked even the out of SIP range, the outgoing call number for out of SIP range extension should be 8597700

====Translation Rule added==== Attached current run config. 

Existing works...

voice translation-rule 3
rule 1 /\(^77..\)/ /859\1/

Newly added to make it work- but not working as expected. 
rule 2 /\(^78..\)/ /859\1/
rule 3 /^78../ /8597700/
rule 4 /^7800/ /8597700/

 

 

[Nithin Eluvathingal]

Hope your DID range is 7720 to 7729. [10 Extension]

voice translation-rule 3
rule 1 /\(^772.\)/ /859\1/

rule 2 /^77../ /8597700/
rule 3 /^78../ /8597700/

Test result for above configuration.

jlrvg#test voice translation-rule 3 7720
Matched with rule 1
Original number: 7720 Translated number: 8597720
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

jlrvg#test voice translation-rule 3 7730
Matched with rule 2
Original number: 7730 Translated number: 8597700
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

jlrvg#test voice translation-rule 3 7830
Matched with rule 3
Original number: 7830 Translated number: 8597700
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

[farispv]

DID range is 7700 to 7729. 

The rule 2,3,4 in translation rule 3 added for testing. when do the test, 7731 not matching the rules, its matching rule 1.

can you please advise what changes to be make in below translation rule as per DID

====Current Config is below. 

voice translation-rule 1
rule 1 /^\*\(\)/ /\1/
!
voice translation-rule 2
rule 1 /^8597700/ /5000/
rule 2 /0138597700/ /5000/
rule 4 /^859\(77..\)/ /\1/
rule 5 /^013859\(77..\)/ /\1/
rule 6 /^13859\(77..\)/ /\1/
!
voice translation-rule 3
rule 1 /\(^77..\)/ /859\1/
rule 2 /\(^78..\)/ /859\1/
rule 3 /^78../ /8597700/
rule 4 /^7800/ /8597700/

=============================================================================

below is the result

KMM-VG1#test voice translation-rule 3 7720
Matched with rule 1
Original number: 7720 Translated number: 8397720
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

KMM-VG1-VG1#test voice translation-rule 3 7730
Matched with rule 1
Original number: 7730 Translated number: 8397730
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

SITCO-DMM-VG1#test voice translation-rule 3 7731
Matched with rule 1
Original number: 7731 Translated number: 8397731
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

[Nithin Eluvathingal · Accepted solution]

Change the rule as mentioned below

voice translation-rule 3
rule 1 /\(^77[012].\)/ /859\1/

rule 2 /^77[3-9]./ /8597700/
rule 3 /\(^78..\)/ /859\1/
rule 4 /^78../ /8597700/
rule 5 /^7800/ /8597700/

Test Result.

jlrvg#sh run | sec voice tran

voice translation-rule 3

 rule 1 /\(^77[012].\)/ /859\1/

 rule 2 /^77[3-9]./ /8597700/

 rule 3 /\(^78..\)/ /859\1/

 rule 4 /^78../ /8597700/

 rule 5 /^7800/ /8597700/

voice translation-profile 1

jlrvg#test voice tran

jlrvg#test voice translation-rule 3 7700

Matched with rule 1

Original number: 7700 Translated number: 8597700

Original number type: none Translated number type: none

Original number plan: none Translated number plan: none

jlrvg#test voice translation-rule 3 7711

Matched with rule 1

Original number: 7711 Translated number: 8597711

Original number type: none Translated number type: none

Original number plan: none Translated number plan: none

jlrvg#test voice translation-rule 3 7729

Matched with rule 1

Original number: 7729 Translated number: 8597729

Original number type: none Translated number type: none

Original number plan: none Translated number plan: none

jlrvg#test voice translation-rule 3 7730

Matched with rule 2

Original number: 7730 Translated number: 8597700

Original number type: none Translated number type: none

Original number plan: none Translated number plan: none

jlrvg#test voice translation-rule 3 7731

Matched with rule 2

Original number: 7731 Translated number: 8597700

Original number type: none Translated number type: none

Original number plan: none Translated number plan: none

[Roger Kallberg · Accepted solution]

You need to have a more specific rule, that is ordered before your rule for the in range numbers, to match the out of range numbers. As an example you could create something like this. This is because translation rules are top down processing and stops as soon as there is a match.

voice translation-rule 3
rule 1 /^773.$/ /8597700/
rule 2 /\(^77..$\)/ /859\1/

Likely you would also need to have a SIP profile to rewrite the SDP. Have a look at this excellent document for details on how to do this. https://www.cisco.com/c/en/us/support/docs/voice/ip-telephony-voice-over-ip-voip/211306-In-Depth-Explanation-of-Cisco-IOS-and-IO.html

[farispv]

Thank for the reply and refer links, let me go through it. 

[farispv]

hello, 
I have modified as per the provided, when we do test on VG, below is output but when we place the call in the series of extension 7733. the call failed, with cause code 28 [484 Address Incomplete ], is there any to do from ISP or CUCM ?

=========================================Test=========================

KMM-VG1#test voice translation-rule 3 7721
Matched with rule 1
Original number: 7721 Translated number: 8597721
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

SITCO-DMM-VG1#test voice translation-rule 3 7733
Matched with rule 2
Original number: 7733 Translated number: 8597700
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none

==============================

RTMT log output below.
RTMT-Log
Message In Log File
2020/12/27 11:58:39.938|SIPL|0|TCP|IN|192.168.60.20|5060|SEP00451D6B6530|192.168.40.165|51373|1,100,14,4831904.7^192.168.40.165^*|433877297|00451d6b-65300019-19a62772-6152615f@192.168.40.165|INVITE
2020/12/27 11:58:39.939|SIPL|0|TCP|OUT|192.168.60.20|5060|SEP00451D6B6530|192.168.40.165|51373|1,100,14,4831904.7^192.168.40.165^*|433877298|00451d6b-65300019-19a62772-6152615f@192.168.40.165|100 Trying
2020/12/27 11:58:39.945|CC|SETUP|24794828|24794829|8397733|*0500405253|*05005058586 2020/12/27 11:58:39.964|CC|OFFERED|24794828|24794829|8397733|*0500405253|*0500405253|SEP00451D6B6530|KMM-SIP-Trunk
2020/12/27 11:58:39.965|SIPT|24794829|TCP|OUT|192.168.60.20|5060|KMM-SIP-Trunk|10.12.11.1|5060|1,100,14,1335696.1466396^192.168.60.20^MTP_2|433877301|b4cf8f00-fe814cbf-54d81f-a37a8c0@192.168.60.20|INVITE
2020/12/27 11:58:40.008|SIPT|24794829|TCP|IN|1192.168.60.20|5060|KMM-SIP-Trunk|10.12.11.1|5060|1,100,14,4558005.90205^10.12.11.1^*|433877302|b4cf8f00-fe814cbf-54d81f-a37a8c0@192.168.60.20|100 Trying
2020/12/27 11:58:40.096|SIPT|24794829|TCP|IN|192.168.60.20|5060|KMM-SIP-Trunk|10.12.11.1|5060|1,100,14,4558005.90206^10.12.11.1^*|433877305|b4cf8f00-fe814cbf-54d81f-a37a8c0@192.168.60.20|484 Address Incomplete

[Nithin Eluvathingal]

whats your calling and called number.

your called number and calling is as expected by ISP ?

[farispv]

Hello, 
Thanks for your reply. 

called number is 7733
calling number 0538691670

ISP would expect the outgoing call in SIP range or 0138597700,

I have opened a ticket with SIP provider to confirm the expected numbers. 

[Roger Kallberg]

Likely you might have mixed called and calling numbers up in your reply.

Shouldn’t it be 

calling number is 7733 -> translated to 0138597700
called number is 0538691670

[Roger Kallberg]

The output of the test indicates that you don’t have the rules in the order I wrote. However it does look like you have the rules as @Nithin Eluvathingal suggested and that should also work. Quite likely your problem derives from content in the SDP. You would need to rewrite that also to allow calls from out of range numbers. Often you need to include a Diversion header for this to be accepted by the service provider.

[farispv]

Many thanks for pointing into to root cause, could you please advise and guide me where should  modify to rewrite that to allow calls from out of range numbers & Diversion header 
I couldn't find such config on Voice gateway. 
Thank you once again for your reply. 

[Nithin Eluvathingal]

Have a look on below document.

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-sip-param-mod.html

[farispv]

Hello, 

Thank for the link, I haven't seen any vice class sip profile on the CUBE at this moment in order to modify it. 
However during the trouble shoot process noticed in RTMT log, all the extension from the subjected extension range or in DID range is starts with 859 as preceding number eg. 8597721 & 8597733 etc... once it receive to the CUBE its getting reject. 
so i have added another translation rule by  rule 3 /^85973.../ /8597700/
Unfortunately my SIP link is down, will check functionality once it up. 

What will be the configuration made on CUCM by having the extension comes with 859 in the beginning of all extension

====RTMTLog===============

2020/12/29 09:56:03.989|CC|OFFERED|24804165|24804166|8597733|*0538691670|*0538691670|SEP00451D6B6530|KMM-SIP-Trunk

[Roger Kallberg · Accepted solution]

There are a few options for that. Listed below are a few, but not to be seen as an absolute guarantee that it’s complete.

• Calling transformation patterns
• Transformation of calling number on route pattern.
• Transformation of calling number on route list/route group level.
• Translation pattern(s).
• Transformation of calling number on trunk level.

The obvious question would be have you checked that the actual directory numbers don’t start with these numbers?