02-11-2016 02:29 AM - edited 03-17-2019 05:50 AM
Hi,
I am trying to mask all outgoing calls on a voice gateway to display the same number when dialing out. At the moment all outgoing calls either display the wrong number or come up as private.
We have an H323 voice gateway with 4 ISDN2 lines. These lines are setup in a round robin trunk group. I believe that the number currently being displayed is either the trunk group / hunt group number or channel number for one of the ISDN2's.
Currently any outbound call will either display the number +35316618886 or just come up as Private Number. I would like for all outbound calls to display 0035316344850. This number is a DDI associated to the ISDN2 lines.
Attached is the current config for the voice gateway. Any help with this would be very much appreciated.
Thanks
S
Solved! Go to Solution.
02-11-2016 03:01 AM
In current configuration, I can not see any translation being applied for outbound PSTN calls. Since you are using trunk group, you can create translation rules and profile, and apply to trunk group in outbound direction.
voice translation-rule 10
rule 1 // /0035316344850/
voice translation-profile 10
translate calling 10
trunk group BRI-TG
translation-profile outgoing 10
Verify the same using debug isdn q931.
- Vivek
02-11-2016 03:01 AM
In current configuration, I can not see any translation being applied for outbound PSTN calls. Since you are using trunk group, you can create translation rules and profile, and apply to trunk group in outbound direction.
voice translation-rule 10
rule 1 // /0035316344850/
voice translation-profile 10
translate calling 10
trunk group BRI-TG
translation-profile outgoing 10
Verify the same using debug isdn q931.
- Vivek
02-11-2016 03:03 AM
You can easily achieve this by setting the mask at the route list/Route group level..
Set external mask to ON and then enter the number as the calling mask..0035316344850
To do this, Go to Route list, then select the route group associated with the RL,
Under calling party transformation>
02-11-2016 03:55 AM
Thanks for the replies. I've tried both methods that you have listed an I am still seeing the same results unfortunately.
I had initially tried to do this on the interfaces themselves by using "ISDN Calling-Number" as shown below.
Also below is the Debug ISDN Q931 which seems to show the correct number being sent out but that is not the number that is being displayed. I spoke to the carrier Eircomm and they are insisting the problem is with us.
Any ideas?
interface BRI0/0/0 no ip address isdn switch-type basic-net3 isdn tei-negotiation first-call isdn point-to-point-setup isdn incoming-voice voice isdn calling-number 0035316344850 isdn sending-complete isdn static-tei 0 trunk-group BRI-TG 1 ! interface BRI0/0/1 no ip address isdn switch-type basic-net3 isdn tei-negotiation first-call isdn point-to-point-setup isdn incoming-voice voice isdn calling-number 0035316344850 isdn sending-complete isdn static-tei 0 trunk-group BRI-TG 2 ! interface BRI0/1/0 no ip address isdn switch-type basic-net3 isdn tei-negotiation first-call isdn point-to-point-setup isdn incoming-voice voice isdn calling-number 0035316344850 isdn sending-complete isdn static-tei 0 trunk-group BRI-TG 3 ! interface BRI0/1/1 no ip address isdn switch-type basic-net3 isdn tei-negotiation first-call isdn point-to-point-setup isdn incoming-voice voice isdn calling-number 0035316344850 isdn sending-complete isdn static-tei 0 trunk-group BRI-TG 4 !
DUB-2921#debug isdn q931
debug isdn q931 is ON.
DUB-2921#term mon
DUB-2921#
Feb 11 11:44:57.902: ISDN BR0/0/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 0035316344850
Feb 11 11:44:57.902: ISDN BR0/0/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive
DUB-2921#
Feb 11 11:44:57.954: %LINK-3-UPDOWN: Interface BRI0/0/0, changed state to up
DUB-2921#
Feb 11 11:44:58.914: ISDN BR0/0/0 Q931: Sending SETUP callref = 0x0028 callID = 0x8039 switch = basic-net3 interface = User
Feb 11 11:44:58.914: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8 callref = 0x28
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x0081, '0035316344850'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '00442072094365'
Plan:Unknown, Type:Unknown
Sending Complete
Feb 11 11:44:59.142: ISDN BR0/0/0 Q931: RX <- CALL_PROC pd = 8 callref = 0xA8
Channel ID i = 0x89
Exclusive, B1
DUB-2921#
Feb 11 11:45:00.786: ISDN BR0/0/0 Q931: RX <- ALERTING pd = 8 callref = 0xA8
Progress Ind i = 0x8488 - In-band info or appropriate now available
DUB-2921#
Feb 11 11:45:04.202: ISDN BR0/0/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x28
Cause i = 0x8090 - Normal call clearing
Feb 11 11:45:04.334: ISDN BR0/0/0 Q931: RX <- RELEASE pd = 8 callref = 0xA8
Feb 11 11:45:04.338: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x28
DUB-2921#
Feb 11 11:45:12.958: ISDN BR0/0/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 0035316344850
Feb 11 11:45:12.958: ISDN BR0/0/1 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive
DUB-2921#
Feb 11 11:45:13.010: %LINK-3-UPDOWN: Interface BRI0/0/1, changed state to up
DUB-2921#
Feb 11 11:45:13.966: ISDN BR0/0/1 Q931: Sending SETUP callref = 0x0029 callID = 0x803A switch = basic-net3 interface = User
Feb 11 11:45:13.970: ISDN BR0/0/1 Q931: TX -> SETUP pd = 8 callref = 0x29
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x0081, '0035316344850'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '00447786251277'
Plan:Unknown, Type:Unknown
Sending Complete
Feb 11 11:45:14.210: ISDN BR0/0/1 Q931: RX <- CALL_PROC pd = 8 callref = 0xA9
Channel ID i = 0x89
Exclusive, B1
DUB-2921#
Feb 11 11:45:18.422: ISDN BR0/0/1 Q931: RX <- ALERTING pd = 8 callref = 0xA9
Progress Ind i = 0x8A88 - In-band info or appropriate now available
Progress Ind i = 0x8A81 - Call not end-to-end ISDN, may have in-band info
Feb 11 11:45:19.342: ISDN BR0/0/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2
DUB-2921#
Feb 11 11:45:22.286: ISDN BR0/0/1 Q931: TX -> DISCONNECT pd = 8 callref = 0x29
Cause i = 0x8090 - Normal call clearing
Feb 11 11:45:22.414: ISDN BR0/0/1 Q931: RX <- RELEASE pd = 8 callref = 0xA9
Feb 11 11:45:22.414: ISDN BR0/0/1 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x29
DUB-2921#
Feb 11 11:45:37.346: ISDN BR0/0/1 Q931: Ux_DLRelInd: DL_REL_IND received from L2
DUB-2921#
Feb 11 11:45:49.910: ISDN BR0/0/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3
DUB-2921#
Feb 11 11:45:49.962: %LINK-3-UPDOWN: Interface BRI0/0/0, changed state to down
DUB-2921#
Feb 11 11:46:07.905: ISDN BR0/0/1 Q931: L3_ShutDown: Shutting down ISDN Layer 3
DUB-2921#
Feb 11 11:46:07.957: %LINK-3-UPDOWN: Interface BRI0/0/1, changed state to down
DUB-2921#
Feb 11 11:47:58.980: ISDN BR0/1/1 Q931: TX -> DISCONNECT pd = 8 callref = 0x27
Cause i = 0x8090 - Normal call clearing
Feb 11 11:47:59.120: ISDN BR0/1/1 Q931: RX <- RELEASE pd = 8 callref = 0xA7
Feb 11 11:47:59.120: ISDN BR0/1/1 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x27
DUB-2921#
Feb 11 11:48:14.080: ISDN BR0/1/1 Q931: Ux_DLRelInd: DL_REL_IND received from L2
DUB-2921#
Feb 11 11:48:44.651: ISDN BR0/1/1 Q931: L3_ShutDown: Shutting down ISDN Layer 3
DUB-2921#
Feb 11 11:48:44.703: %LINK-3-UPDOWN: Interface BRI0/1/1, changed state to down
DUB-2921#
02-11-2016 04:14 AM
Telcos are hard nuts and you need to crack them most times. What you need is to send them your isdn logs. The logs clearly show the number you are sending to them. As long as this number is part of your DDI, then they should present it. Go back and "SHOUT" at them, sometimes they need some whipping to get them to listen
Feb 11 11:44:58.914: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8 callref = 0x28
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x0081, '0035316344850'
02-11-2016 06:08 AM
Thanks for the help and advice all. I went back to our Telco provider and this time they have "escalated it to their 2nd line team" and requested the logs.
Have to wait and see what they come back with now.
02-11-2016 04:18 AM
Seems your method is also working as expected and gateway is sending desired ANI in setup message, but that ANI is not being entertained by your provider. You have two choices now;
1. You can try by changing isdn plan/type in accordance with your provider requirement.
2. You need to verify the DID number (ANI) you are sending is correct otherwise need to check with your operator.
- Vivek
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