Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Overlap with Ephone-dn and dial peer

I have a problem that is causing me much stress

I have a CUCME 8.1 with a PRI connection and a bank of DID's Now all of my DID's to this point have been in the 6820 - 6879 range.  I have the typical dial 9 to gain an outside line access and all my dial peers reflect this.  Now my client has ported a addtional DID over to my PRI of 9185.  No big deal right I add the ephone-=dn and assign it to a ephone, calls come into the line no problem and he can make outbound calls fine.

Now here is the problem.  When this site is attempting to call a San Diego Cell phone in the 858 area code they dial 9-1-858-XXX-XXXX but the CME is seeing 9-1-8-5 and dialing the internal ephone-dn

Is there ANY way around this?  I have tried to assign him a new ephone-dn and add a translatiopn rule like rule 2 /9158/ /6550/ and this worked that incoming calls seen the 9158 and translated it to 6550 all was good untill I made an outbound call and it appended the 6550 in the number so 9-1-858-xxx-xxxx became 165508xxxxxxx

I would change my secondary dial tone digit but it would just move the problem to another spot as we are utilizing 4 digit translations for other offices.

I can provide all my translation rules and dial peers if it will help?

voice translation-rule 1
rule 1 /(68..\)/ /602797\1/
rule 2 /(9185\)/ /602275\1/

!

voice translation-profile CALLER_ID

translate calling 1

translate called 1

!

!
dial-peer voice 1 pots
description **T1 PRI pots dial-peer**
destination-pattern 9[3469]11
port 0/0/0:23
forward-digits 3

!

dial-peer voice 2 pots
description **T1 PRI pots dial-peer**
translation-profile outgoing CALLER_ID
destination-pattern 9[2-9]..[2-9]......
port 0/0/0:23
!

dial-peer voice 3 pots
description ** T1 PRI pots dial-peer **
translation-profile outgoing CALLER_ID
destination-pattern 91[2-9]..[2-9]......
port 0/0/0:23
prefix 1
!

dial-peer voice 4 pots
description Incoming calls
translation-profile outgoing CALLER_ID
incoming called-number .
direct-inward-dial
port 0/0/0:23
!

!
dial-peer voice 5 pots
description ** T1 PRI pots dial-peer International**
translation-profile outgoing CALLER_ID
numbering-type unknown
destination-pattern 9011T
port 0/0/0:23
forward-digits all
prefix 011

!

dial-peer voice 6 pots ( this was a last ditch attempt. )

description SD

translation-profile outgoing CALLER_ID

destination-pattern 9185........

port 0/0/0:23

Everyone's tags (4)
4 REPLIES
Hall of Fame Super Gold

Overlap with Ephone-dn and dial peer

Having DNs like 91xx or even 9xxx will cause exactly this problem.

You should have you DNs starting with anything digit but 9.

Eg  158, 4518, all that would be fine and simple to handle with a minimal translation-rule.

Community Member

Overlap with Ephone-dn and dial peer

I aggree that number not starting with a 9 would be great but this is what it is.  The client has had this number for somew time and in not willing to give it up.  This is why I was trying to doa translation to a different number but then that same translation cause adverse reactions to outgoing calls

Hall of Fame Super Gold

Overlap with Ephone-dn and dial peer

That is typical and as with any poor numbering or design decision, has two possible outcomes:

Keep the mistake, fight it with workarounds, and possibly never solve it.

or

Correct it and live peacefully.

Community Member

Overlap with Ephone-dn and dial peer

I seem to have resolved this by creating an additional translation rule for only incoming . this the outgoing calls are not translated.  But thanks for the advice,  Sometimes we just have to work with what we are given.

529
Views
0
Helpful
4
Replies
CreatePlease to create content