03-18-2010 09:08 AM - edited 03-15-2019 09:51 PM
My problem is not that calls will not work, but why they are working. I'm using an AS5300 for a gateway between our M6 (SIP) and DMS (PRI). Calls from the M6 are all prepended with a three digit Trunk Group ID such as 008. So the called number arriving at the 5300 would be 0085555550000 for example. But to send the call to the DMS, the Trunk Group ID needs to be stripped, sending just the 5555550000 to the DMS. On the flip side, when a call comes from the DMS to a number (ex: 5555550000), the 5300 needs to prepend the number with the Trunk Group ID before sending it to the M6. I think I know why the inbound to the M6 works, but cannot figure out why the outbound to the DMS works. Here are examples of my dial-peers and translation-rules. If anyone can tell me how the 008 is being stripped, I'd appreciate it.
dial-peer voice 100 voip
incoming called-number 008.T
destination-pattern 412.......
progress_ind setup enable 3
progress_ind progress enable 8
translate-outgoing called 412
voice-class codec 100
session protocol sipv2
session target ipv4:10.170.5.66
dtmf-relay rtp-nte
no vad
dial-peer voice 1 pots
description AS5300 TESTING TG1 FROM GATEWAY TO 4TH PRI
translation-profile outgoing ISDN
destination-pattern 008.T
translate-outgoing calling 20
translate-outgoing called 20
direct-inward-dial
port 3:D
translation-rule 1
Rule 1 ^9 0019
Rule 2 ^2 0012
!
!
translation-rule 20
Rule 1 ^1 1 unknown national
Rule 2 ^2 2 unknown national
Rule 3 ^3 3 unknown national
Rule 4 ^4 4 unknown national
Rule 5 ^5 5 unknown national
Rule 6 ^6 6 unknown national
Rule 7 ^7 7 unknown national
Rule 8 ^8 8 unknown national
Rule 9 ^9 9 unknown national
!
!
translation-rule 412
Rule 0 ^412....... 008412
!
!
translation-rule 30
Rule 0 011 011 unknown international
!
!
translation-rule 724
Rule 0 ^724....... 008724
!
!
translation-rule 878
Rule 0 ^878....... 008878
!
voice translation-rule 40
rule 1 // // type any national plan any isdn
!
!
voice translation-profile ISDN
translate redirect-called 40
!
Solved! Go to Solution.
03-19-2010 08:09 AM
Hi
Good to hear you're all sorted...
Ps.. please rate my posts if helpful; click the stars and mark as 'answered' if appropriate
Thanks
03-18-2010 12:30 PM
Hi
The portion of the destination-pattern string that is matched on the 'pots' dial peer is always stripped.
So a common one is
Destination-pattern 9T
You dial 9123412341234
Out goes 123412341234
Yours is
destination-pattern 008.T
So everything after the 008 goes out.
Regards
Aaron
Please rate helpful posts...
03-18-2010 12:49 PM
Aaron,
Thank you for the update. That was driving me crazy. It does bring up
another question though... for international calls. The same thing would
happen on the M6-DMS side as far as arriving at the 5300 prepended with
the 008. Here are the dial-peers and translation-rules I have setup.
After seeing your comment, it appears the 008011 piece of an international
call would be stripped, and would therefore not match translation-rule
30? However, my DMS guy said the call does come through, first without
the 011, to which he sends back an invalid call type... and then he said
I send him the call again with the 011? Is there anything in the config
that would cause the call to be resubmitted with 011?
!
dial-peer voice 5 pots
description CLEC BUS NTERNATIONAL FROM GATEWAY TO 4TH PRI
destination-pattern 008011T
translate-outgoing calling 20
translate-outgoing called 30
direct-inward-dial
port 3:D
!
dial-peer voice 6 pots
description CLEC BUS INTERNATIONAL FROM GATEWAY TO 3RD PRI
preference 1
destination-pattern 008011T
translate-outgoing calling 20
translate-outgoing called 30
direct-inward-dial
port 2:D
!
dial-peer voice 7 pots
description CLEC BUS INTERNATIONAL FROM GATEWAY TO 2ND PRI
preference 2
destination-pattern 008011T
translate-outgoing calling 20
translate-outgoing called 30
direct-inward-dial
port 1:D
!
dial-peer voice 8 pots
description CLEC BUS INTERNATIONAL FROM GATEWAY TO 1ST PRI
preference 3
destination-pattern 008011T
translate-outgoing calling 20
translate-outgoing called 30
direct-inward-dial
port 0:D
!
!
translation-rule 1
Rule 1 ^9 0019
Rule 2 ^2 0012
!
!
translation-rule 20
Rule 1 ^1 1 unknown national
Rule 2 ^2 2 unknown national
Rule 3 ^3 3 unknown national
Rule 4 ^4 4 unknown national
Rule 5 ^5 5 unknown national
Rule 6 ^6 6 unknown national
Rule 7 ^7 7 unknown national
Rule 8 ^8 8 unknown national
Rule 9 ^9 9 unknown national
!
!
translation-rule 412
Rule 0 ^412....... 008412
!
!
translation-rule 30
Rule 0 011 011 unknown international
!
!
translation-rule 724
Rule 0 ^724....... 008724
!
!
translation-rule 878
Rule 0 ^878....... 008878
!
From: aaronharrison
To: William Daw
Date: 03/18/2010 03:31 PM
Subject: New message: "Don't understand digit
William Daw,
A new message was posted in the Discussion thread "Don't understand digit
manipulation for dial-peer":
https://supportforums.cisco.com/message/3038008#3038008
Author : aaronharrison
Profile : https://supportforums.cisco.com/people/aaronharrison
Message:
03-18-2010 01:36 PM
Hi
Well - it's not clear what's going on there from the partial configs.
It sounds like he isn't recognizing the number without the 011, so is hairpinning it back to you. It must be hitting an inbound dial-peer on your kit that is translating it again and sending it back.
Make a test call whilst doing:
Debug voip dialpeer
Debug isdn q931
And hopefully we'll be able to see what's going on...
Regards
Aaron
Please rate helpful posts..
03-19-2010 07:09 AM
Here is the debug as requested. I'm also attaching the nearly complete
config. Thanks in advance.
Mar 19 09:56:42: Inside dpMatchCore:
Mar 19 09:56:42: destination pattn: 00801161396694916 expanded string:
00801161396694916
Mar 19 09:56:42: MatchNextPeer: Peer 100 matched
Mar 19 09:56:42: MatchNextPeer: Peer 101 matched
Mar 19 09:56:42: MatchNextPeer: Peer 102 matched
Mar 19 09:56:42: MatchNextPeer: Peer 103 matched
Mar 19 09:56:42: MatchNextPeer: Peer 104 matched
Mar 19 09:56:42: MatchNextPeer: Peer 105 matched
Mar 19 09:56:42: Inside dpMatchPeersMoreArg
Mar 19 09:56:42: dpMatchPeersMoreArg: Match Dest. pattern; called
(00801161396694916)
Mar 19 09:56:42: Inside dpMatchCore:
Mar 19 09:56:42: destination pattn: 00801161396694916 expanded string:
00801161396694916
Mar 19 09:56:42: MatchNextPeer: Peer 1 matched
Mar 19 09:56:42: MatchNextPeer: Peer 2 matched
Mar 19 09:56:42: MatchNextPeer: Peer 3 matched
Mar 19 09:56:42: MatchNextPeer: Peer 4 matched
Mar 19 09:56:42: MatchNextPeer: Peer 5 matched
Mar 19 09:56:42: MatchNextPeer: Peer 6 matched
Mar 19 09:56:42: MatchNextPeer: Peer 7 matched
Mar 19 09:56:42: MatchNextPeer: Peer 8 matched
Mar 19 09:56:42: dpMatchPeersMoreArg: Result=0 after MATCH_ORIGINATE
Mar 19 09:56:42: ISDN Se3:23 Q931: TX -> SETUP pd = 8 callref = 0x0095
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2180, '7247789508'
Plan:ISDN, Type:National
Called Party Number i = 0x91, '61396694916'
Plan:ISDN, Type:International
Mar 19 09:56:42: ISDN Se3:23 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x8095
Cause i = 0x809C - Invalid number format (incomplete number)
Mar 19 09:56:42: ISDN Se3:23 *ERROR*: call_cleared: VOICE ERROR: NULL
VDEV Common(0xFC): bchan -1, call id 0x801B
Mar 19 09:56:42: ISDN Se2:23 Q931: TX -> SETUP pd = 8 callref = 0x0096
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2180, '7247789508'
Plan:ISDN, Type:National
Called Party Number i = 0x91, '61396694916'
Plan:ISDN, Type:International
Mar 19 09:56:42: ISDN Se2:23 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x8096
Cause i = 0x809C - Invalid number format (incomplete number)
Mar 19 09:56:42: ISDN Se2:23 *ERROR*: call_cleared: VOICE ERROR: NULL
VDEV Common(0xFC): bchan -1, call id 0x801C
Mar 19 09:56:43: ISDN Se1:23 Q931: TX -> SETUP pd = 8 callref = 0x0097
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2180, '7247789508'
Plan:ISDN, Type:National
Called Party Number i = 0x91, '61396694916'
Plan:ISDN, Type:International
Mar 19 09:56:43: ISDN Se1:23 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x8097
Cause i = 0x809C - Invalid number format (incomplete number)
Mar 19 09:56:43: ISDN Se1:23 *ERROR*: call_cleared: VOICE ERROR: NULL
VDEV Common(0xFC): bchan -1, call id 0x801D
Mar 19 09:56:43: ISDN Se0:23 Q931: TX -> SETUP pd = 8 callref = 0x0098
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2180, '7247789508'
Plan:ISDN, Type:National
Called Party Number i = 0x91, '61396694916'
Plan:ISDN, Type:International
Mar 19 09:56:43: ISDN Se0:23 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x8098
Cause i = 0x809C - Invalid number format (incomplete number)
Mar 19 09:56:43: ISDN Se0:23 *ERROR*: call_cleared: VOICE ERROR: NULL
VDEV Common(0xFC): bchan -1, call id 0x801E
Mar 19 09:56:43: ISDN Se3:23 Q931: TX -> SETUP pd = 8 callref = 0x0099
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2180, '7247789508'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '01161396694916'
Plan:Unknown, Type:Unknown
Mar 19 09:56:43: ISDN Se3:23 Q931: RX <- CALL_PROC pd = 8 callref =
0x8099
Channel ID i = 0xA98397
Exclusive, Channel 23
Mar 19 09:56:47: ISDN Se3:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8099
Cause i = 0x82FF - Interworking error; unspecified
Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have
in-band info
Mar 19 09:56:48: ISDN Se3:23 Q931: RX <- CONNECT pd = 8 callref = 0x8099
Mar 19 09:56:48: %ISDN-6-CONNECT: Interface Serial3:22 is now connected to
01161396694916 N/A
Mar 19 09:56:48: ISDN Se3:23 Q931: TX -> CONNECT_ACK pd = 8 callref =
0x0099
Mar 19 09:56:53: %ISDN-6-DISCONNECT: Interface Serial3:22 disconnected
from 01161396694916 , call lasted 4 seconds
Mar 19 09:56:53: ISDN Se3:23 Q931: TX -> DISCONNECT pd = 8 callref =
0x0099
Cause i = 0x809C - Invalid number format (incomplete number)
Mar 19 09:56:53: ISDN Se3:23 Q931: RX <- RELEASE pd = 8 callref = 0x8099
Mar 19 09:56:53: ISDN Se3:23 Q931: TX -> RELEASE_COMP pd = 8 callref =
0x0099
03-19-2010 07:38 AM
Hi
So what's happening here is that dial-peers 5,6,7,8 also match the number you dialed.
These cause the leading/matched 6 digits to be stripped, and the call sent out.
The reject from the other end rolls the call to the next dial peer each time, until it's tried all four.
At this point, one of the less specific matches is used - e..g 1,2,3 or 4.
These only strip the first 3 digits, so they go through OK.
Suggestion - if the peers 5-8 should receive the full digit string without the 008, you can put in:
Prefix 011
This will re-insert the stripped digits to leave a nice formatted number.
Regards
Aaron
Please rate helpful posts...
03-19-2010 07:41 AM
Like this?
!
dial-peer voice 5 pots
description CLEC BUS NTERNATIONAL FROM GATEWAY TO 4TH PRI
destination-pattern 008011T
prefix 011
translate-outgoing calling 20
translate-outgoing called 30
direct-inward-dial
port 3:D
!
03-19-2010 07:58 AM
Hi
That's it.
Regards
03-19-2010 08:03 AM
Thank You. That worked perfectly. The only other change I had to make
was on translation-rule 30, which was setting the call type to
international. Apparently the DMS either wants 011 or international call
type, but not both. I set it to unknown and the debugs show the isdn
completing on the first pass. Thanks again. Very helpful!
From: aaronharrison
To: William Daw
Date: 03/19/2010 10:59 AM
Subject: New message: "Don't understand digit
William Daw,
A new message was posted in the Discussion thread "Don't understand digit
manipulation for dial-peer":
https://supportforums.cisco.com/message/3038617#3038617
Author : aaronharrison
Profile : https://supportforums.cisco.com/people/aaronharrison
Message:
03-19-2010 08:09 AM
Hi
Good to hear you're all sorted...
Ps.. please rate my posts if helpful; click the stars and mark as 'answered' if appropriate
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide