private FXO line

zahid77 · ‎11-04-2008

Hi expert,

i have CME where PRI and 1 FXO line is terminated, i want to make FXO line as a private line for one xtension let say 606, i configured it and it was wroking fine but i want to use this line only for international dialing and local and national calls should go thru PRI

ephone-dn 1

number 606

trunk 82

voice-port 0/1/0

connection plar opx 606

dial-peer voice 1 pots

destination-pattern 82

Port 0/1/0

i llappreciate if somebody suggest any solution

allan.thomas · ‎11-04-2008

You can specify the trunk directly on the ephone-dn which is specifically tied to a pots dial-peer. Simply configure your digit length on the dial-peer after the trunk access.

ephone-dn 1

trunk 82

!

dial-peer voice 10 pots

destination-pattern ^82....T

port x/y

!

HTH

Allan.

zahid77 · ‎11-04-2008

i have done this config but if i want to use PRI line then what shuld i do i have already madde so many dial-peers for COR list where normal users are making calls as per their privilages

now this particular port should be used as private line as well as this users should ve a access to PRI line as well

please suggest

allan.thomas · ‎11-04-2008

The only solution around this would be to configure translation rules, which translates the called number using a prefix or recognises an international call and then adds the 82 prefix.

The call will route out of the appropriate outgoing port base on the prefix dialled by the private line user.

voice translation-rule 1

rule 1 /^900/ /8200/

rule 2 /^9/ /9/

!

voice translation-profile User1

translate called 1

!

ephone-dn-template 1

translation-profile outgoing User1

!

ephone-dn 1

number 606

ephone-dn-template 1

!

dial-peer voice 1 pots

destination-pattern 82T

port 0/1/0

!

I have assumed that you are using 9 outside line, so the translation depends on how your PRI dial-peers are configured.

In this example if extension 606 dialled an International call starting 900, it will be translated to 82 and therefore match the outgoing dial-peer 1.

Every other call starting with 9 made from extension 606 will be routed with only 9 as the prefix and should therefore match your other dial-peers.

HTH

Allan.

zahid77 · ‎11-04-2008

thanks then let me try this solution i ll update tomorrow morning

zahid77 · ‎11-05-2008

ok i applied the solution find my config below

voice translation-rule 82

rule 1 /^900/ /8200/

rule 2 /^9/ /9/

!

voice translation-profile User606

translate called 82

!

ephone-dn-template 1

translation-profile outgoing User606

!

ephone-dn 64 dual-line

number 606

pickup-group 123

label MANAGER

name manager

corlist incoming call-International

corlist outgoing call-International

ephone-dn-template 1

!

dial-peer voice 204 pots

destination-pattern 82T

port 0/1/0

after applying this configuration i am getting cointinous tone

please suggest

allan.thomas · ‎11-05-2008

When you dial an international call 900.... from extension 606 can you enable 'debug voice ccapi inout'.

This will determine which dial-peer is used, and what the expected ani and called number is.

Have you tried a test call with the corlists on the ephone-dn?

Can you post the reset of your configuration, so that we can see your other dial-peers and how they are configured. This is incase there are overlapping ones.

Thanks

Allan.

zahid77 · ‎11-05-2008

please find enclosed configurations

allan.thomas · ‎11-05-2008

The debugs indicate that the correct outgoing dial-peer is selected, however the called number is only 82?

What number is being dialled exactly from extension 606, it should be 900........ in order to match the appropriate translation-rule.

What I neglected to ask is whether 82 should be dropped from the outgoing call? Otherwise the call will routed as 00....... which is what I would ordinarily expect.

Allan.

zahid77 · ‎11-05-2008

yes after applying tis config, i dialed 900......... or any international complete number like 900923214001096

but the continous ring is coming even when i dial any national number

i saw in the debig that it is not forwarding in digit at destination

allan.thomas · ‎11-05-2008

Although I cannot see what this would affect the behaviour, try changing the voice translation rule to be more specific. Both ways achieve the same net result.

voice translation-rule 82

rule 1 /^900\(.+\)/ /8200\1/

rule 2 /^9\(.+\)/ /9\1/

Allan.

allan.thomas · ‎11-05-2008

Hi Zahid, I believe the issue is that the translation-profile should be applied to the incoming call-leg on the ephone-dn-template and not the outgoing.

ephone-dn-template 1

no translation-profile outgoing User606

translation-profile incoming User606

When the translation profile was applied to the outgoing call-leg I received fast-busy as soon as 9 was dialled.

When applied to the inbound call-leg I was able to dial the full number.

I have tested this using a VoIP dial-peer with a destination-pattern 82T and the following setup:-

voice translation-rule 6

rule 1 /^900\(.+\)/ /8200\1/

!

voice translation-profile Test

translate called 6

dial-peer voice 1001 voip

destination-pattern 82T

session target ipv4:192.168.0.6

!

ephone-dn-template 1

translation-profile incoming Test

!

ephone-dn 1

number 1003

ephone-dn-template 1

Below is the debug, you will see that called number is 8200123456789, this is because it is a VoIP dial-peer, 82 will be stripped by the POTs dial-peer in your case:-

In: Calling Number=1003(TON=Unknown, NPI=Unknown, Screening=Not Screened, Pre

sentation=Allowed)

*Mar 2 08:18:01.195: //15/CF850FFE8034/CCAPI/ccCheckClipClir:

Out: Calling Number=1003(TON=Unknown, NPI=Unknown, Screening=Not Screened, Pr

esentation=Allowed)

*Mar 2 08:18:01.195: //15/CF850FFE8034/CCAPI/ccCallSetupRequest:

Destination Pattern=82T, Called Number=8200123456789, Digit Strip=FALSE

*Mar 2 08:18:01.195: //15/CF850FFE8034/CCAPI/ccCallSetupRequest:

Calling Number=1003(TON=Unknown, NPI=Unknown, Screening=Not Screened, Present

ation=Allowed),

Called Number=8200123456789(TON=Unknown, NPI=Unknown),

Redirect Number=, Display Info=

Account Number=, Final Destination Flag=FALSE,

Guid=CF850FFE-2CEC-11D6-8034-C987658569E3, Outgoing Dial-peer=1001

*Mar 2 08:18:01.195: //15/CF850FFE8034/CCAPI/cc_api_display_ie_subfields:

ccCallSetupRequest:

cisco-username=

----- ccCallInfo IE subfields -----

cisco-ani=1003

cisco-anitype=0

cisco-aniplan=0

cisco-anipi=0

cisco-anisi=0

dest=8200123456789

cisco-desttype=0

cisco-destplan=0

cisco-rdie=FFFFFFFF

cisco-rdn=

cisco-rdntype=0

cisco-rdnplan=0

cisco-rdnpi=0

cisco-rdnsi=0

cisco-redirectreason=0 fwd_final_type =0

final_redirectNumber =

hunt_group_timeout =0

*Mar 2 08:18:01.195: //15/CF850FFE8034/CCAPI/ccIFCallSetupRequestPrivate:

Interface=0x66B8BB40, Interface Type=1, Destination=, Mode=0x0,

Call Params(Calling Number=1003,(Calling Name=)(TON=Unknown, NPI=Unknown, Scr

eening=Not Screened, Presentation=Allowed),

Called Number=8200123456789(TON=Unknown, NPI=Unknown), Calling Translated=FAL

SE,

Subscriber Type Str=RegularLine, FinalDestinationFlag=FALSE, Outgoing Dial-pe

er=1001, Call Count On=FALSE,

Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Appl

ication Call Id=)

*Mar 2 08:18:01.195: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Mar 2 08:18:01.195: :cc_get_feature_vsa malloc success

*Mar 2 08:18:01.195: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Mar 2 08:18:01.195: cc_get_feature_vsa count is 2

*Mar 2 08:18:01.195: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Mar 2 08:18:01.195: :FEATURE_VSA attributes are: feature_name:0,fearture_time:

1724962032,feature_id:16

*Mar 2 08:18:01.199: //16/CF850FFE8034/CCAPI/ccIFCallSetupRequestPrivate:

SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1

HTH

Allan

zahid77 · ‎11-05-2008

Thanks a lot Allan

i l try it tomorrow morning

i think this ll help me a lt

i really appreciate your time and effort to help me

God bless you

Zahid fayyaz

zahid77 · ‎11-05-2008

sorry Allan again

now i have additionally create a VOIP dial peer with 82T destination pattern

then what about my POTS dial-peer

it seems my config will like that

voice translation-rule 6

rule 1 /^900\(.+\)/ /8200\1/

!

voice translation-profile Test

translate called 6

dial-peer voice 1001 voip

destination-pattern 82T

session target ipv4:192.168.0.6

dial-peer voice 1002 pots

detsination-pattern 82T

port 0/1/0

!

ephone-dn-template 1

translation-profile incoming Test

!

ephone-dn 1

number 1003

trunk 82

ephone-dn-template 1

allan.thomas · ‎11-05-2008

Hi Zahid, you do not need to add additional dial-peers, the voip dial-peer I referred to was to simply test the concept of the translation-profile.

You will only need to change the ephone-dn-template translation-profile to incoming. I also noticed that trunk 82 is under the ephone-dn, this is not need as we are using translations.

Below is the config that you need:-

voice translation-rule 82

rule 1 /^900\(.+\)/ /8200\1/

rule 2 /^9\(.+\)/ /9\1/

!

voice translation-profile User606

translate called 82

!

dial-peer voice 204 pots

corlist outgoing call-International

destination-pattern 82T

incoming called-number .

port 0/1/0

!

ephone-dn-template 1

no translation-profile outgoing User606

translation-profile incoming User606

!

ephone-dn 64 dual-line

number 606

pickup-group 123

label MANAGER

name manager

corlist incoming call-International

corlist outgoing call-International

no trunk 82

ephone-dn-template 1

!

Essentially, when extension 606 dials 900...... it will be translated to 8200..... and then match the outbound dial-peer 204 and route the call out of port 0/1/0. 82 will be stripped leaving 00...... as the called number, this is the nature of POTs dial-peers.

When 606 dials 90123456789 or 9123456 for example it will remain unchanged, and therefore match one of your PRI outbound dial-peers for national, local calls etc.

HTH

Allan.