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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Caller ID / ISDN Issues on H323 Gateway

We use Sprint as a switched long distance provider. Sprint is configured to prompt for a long distance access code when certain numbers dial long distance, and not prompt for others.


Until I migrated from MGCP to H323, this worked fine. Post migration, all numbers are getting prompted for long distance access codes. This is problematic for certain numbers (fax machines) that are getting prompted to enter a long distance code.


Sprint: Call traces say that when the call comes in, they are seeing the BTN (Billing telephone number) instead of the DID (calling party number) that I should be passing along.


XO (Telco provider): They say that everything should work. I've made sure that my PRI settings match what they were previously (ISDN switch type = NI2, etc).


When I view ISDN q931 debugs, I see the calling party number as it should be.


Here is a test call with q931 debugging enabled (I intentionally replaced area codes with X):


Jun  7 08:32:19: ISDN Se2/0:23 Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type 13

Jun  7 08:32:19: ISDN Se2/0:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num XXX9463091

Jun  7 08:32:19: ISDN Se2/0:23 Q931: Sending SETUP  callref = 0x0B30 callID = 0x8E85 switch = primary-ni interface = User

Jun  7 08:32:19: ISDN Se2/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0B30

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9838B

                Exclusive, Channel 11

        Calling Party Number i = 0x2181, 'XXX9463091'

                Plan:

CLV-MDF-RTR-02#ISDN, Type:National

        Called Party Number i = 0x80, '1XXX4504372'

                Plan:Unknown, Type:Unknown

Jun  7 08:32:19: ISDN Se2/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0x8B30

        Channel ID i = 0xA9838B

                Exclusive, Channel 11

CLV-MDF-RTR-02#

Jun  7 08:32:20: ISDN Se2/0:23 Q931: RX <- PROGRESS pd = 8  callref = 0x8B30

        Cause i = 0x82FF - Interworking error; unspecified

        Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info

CLV-MDF-RTR-02#

Jun  7 08:32:28: ISDN Se2/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x0B30

        Cause i = 0x8090 - Normal call clearing

Jun  7 08:32:28: ISDN Se2/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x8B30

Jun  7 08:32:28: ISDN Se2/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x0B30



Here is my PRI configuration:


!

interface Serial2/0:23

no ip address

encapsulation hdlc

isdn switch-type primary-ni

isdn incoming-voice voice

isdn supp-service name calling

no cdp enable

end

Here is other related voice configuration:

!
isdn switch-type primary-ni

!
voice-card 0
!
voice-card 2
 dspfarm
 dsp services dspfarm
!
!
voice rtp send-recv
!
voice service voip
 fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none
 h323
  call preserve
!
voice class codec 1
 codec preference 1 g711ulaw
 codec preference 2 g729r8
!
voice class h323 1
  h225 timeout tcp establish 3
  h225 timeout connect 120
  h225 timeout setup 5
 h225 display-ie ccm-compatible
!
!
!
voice translation-rule 20
 rule 1 // // type any unknown plan any unknown
!
!
voice translation-profile pri-inbound
 translate called 1
!
voice translation-profile pri-outbound
 translate calling 20

!
!
controller T1 2/0
 pri-group timeslots 1-11,24
!
!
!
interface Serial2/0:23
 no ip address
 encapsulation hdlc
 isdn switch-type primary-ni
 isdn incoming-voice voice
 isdn supp-service name calling
 no cdp enable

!
voice-port 2/0/0
!
voice-port 2/0/1
!
voice-port 2/0:23
 translation-profile incoming pri-inbound
 bearer-cap Speech
!
!
sccp ccm group 1
 description Call Manager DSP Resources
 associate ccm 1 priority 1
 associate ccm 2 priority 2
 associate ccm 3 priority 3
 associate profile 1 register CLV-MDF-CFB
!
dspfarm profile 1 conference
 description Conferencing for Call Manager
 codec g711ulaw
 codec g711alaw
 codec g729ar8
 codec g729abr8
 codec g729r8
 codec g729br8
 maximum sessions 2
 associate application SCCP
!
dial-peer voice 1 pots
 description Incoming T1/PRI calls
 incoming called-number .
 direct-inward-dial
!
dial-peer voice 2 voip
 description Incoming voip calls
 incoming called-number .
 voice-class codec 1
 voice-class h323 1
 dtmf-relay h245-alphanumeric
 no fax-relay sg3-to-g3
 fax rate 14400
 no vad
!
dial-peer voice 10 pots
 preference 1
 destination-pattern 9T
 port 2/0:23
!
dial-peer voice 101 voip
 preference 1
 destination-pattern [1-8]...
 modem passthrough nse codec g711ulaw
 session target ipv4:10.1.3.11
 voice-class codec 1
 voice-class h323 1
 dtmf-relay h245-alphanumeric
 no fax-relay sg3-to-g3
 fax rate 14400
 no vad

I've attached screenshots of the gateway when it was configured for MGCP

I'm pretty much lost.

Everyone's tags (3)
2 REPLIES
VIP Super Bronze

Caller ID / ISDN Issues on H323 Gateway

The only time your provider will replace the calling number with the billing number is when your calling number is not in the allocated DDI range. If you are 100% certain that the calling number is in your ddi block range then take this up with XO. XO switch is the one passing the CLI to Sprint.

The fact that they said it should work doesnt mean it will or is working. I will hold their neck tight until they figure out or tell you why they are modifying the CLI

Please rate useful posts

"I am complete in God, God completes me"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
Hall of Fame Super Gold

Re: Caller ID / ISDN Issues on H323 Gateway

Configure CM so that calling number plan/type is ISDN/national.

Otherwise, telco may not acknowledge as valid DID.

Other than that, it's like aokanlawon said.

1494
Views
0
Helpful
2
Replies