06-03-2008 01:04 AM - edited 03-15-2019 11:01 AM
I am trying to install a 2801 CME router with VIC2-2BRI-NT/TE onto telefonica supplied BRI Circuits. I cannot get layer 2 up. their circuits are setup as Point to point is their anyway to get the CME to work with point to point? I have already set the Interfaces with point to point setup but this still does not bring layer 2 up. below is a debug ISDN Q921 and errors.
*Jun 2 19:57:42.163: ISDN BR0/1/1 SERROR: L2_Go: at bailout DLCB is NULL
L2: sapi 0 tei 0 ces 255 ev 0x6F
Jun 2 19:57:19.135: ISDN BR0/2/0 Q921: User RX <- SABMEp sapi=0 tei=0
*Jun 2 19:57:19.135: ISDN BR0/2/1 Q921: User RX <- SABMEp sapi=0 tei=0
*Jun 2 19:57:19.151: ISDN BR0/1/0 Q921: User RX <- SABMEp sapi=0 tei=0
*Jun 2 19:57:19.155: ISDN BR0/1/1 Q921: User RX <- SABMEp sapi=0 tei=0
Barcelona_CME#sh isdn stat
Global ISDN Switchtype = basic-net3
ISDN BRI0/1/0 interface
dsl 2, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 2 CCBs = 0
The Free Channel Mask: 0x80000003
Barcelona_CME#debug isdn q931
debug isdn q931 is ON.
*Jun 2 20:07:24.743: ISDN BR0/1/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 6178
*Jun 2 20:07:24.747: ISDN BR0/1/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Called num 933010414
Barcelona_CME#
*Jun 2 20:07:30.747: ISDN BR0/1/1 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Barcelona_CME#
Ian
06-03-2008 03:31 AM
Hi,
I have recently configured a BRI in Madrid wth the same provider.
The most important is probably the TEI config. See below our config :
Interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
If it doesn't work, please post you running config.
06-03-2008 03:58 AM
Hi
Thank you - I have tried setting Static-TEI to 0 and my layer 2 comes up but then still cannot dialout
below is an output of a call with static TEI set to 0 where we juat cannot make a successful call.
Global ISDN Switchtype = basic-net3
ISDN BRI0/2/1 interface
dsl 5, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 5 CCBs = 0
The Free Channel Mask: 0x80000003
Total Allocated ISDN CCBs = 0
*Jun 3 12:37:58.867: ISDN BR0/2/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 6178
*Jun 3 12:37:58.871: ISDN BR0/2/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Called num 933014014
*Jun 3 12:37:58.871: ISDN BR0/2/1 Q931: TX -> SETUP pd = 8 callref = 0x06
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x81
Preferred, B1
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0080, '6178'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '933014014'
Plan:Unknown, Type:Unknown
Barcelona_CME#
*Jun 3 12:37:59.035: ISDN BR0/2/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x86
Cause i = 0x82E404 - Invalid information element contents
*Jun 3 12:38:25.423: ISDN BR0/2/1 EVENT: process_bri_call: call id 0x8007, called_number 933014014, Guid C91C4CAC8016 speed 0, call type VOICE, bchan -1 clng_num 6178
*Jun 3 12:38:25.423: ISDN BR0/2/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 6178
*Jun 3 12:38:25.423: ISDN BR0/2/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Called num 933014014
*Jun 3 12:38:25.423: ISDN BR0/2/1 Q931: TX -> SETUP pd = 8 callref = 0x07
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x81
Preferred, B1
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0080, '6178'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '933014014'
Plan:Unknown, Type:Unknown
*Jun 3 12:38:25.599: ISDN BR0/2/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x87
Cause i = 0x82E404 - Invalid information element contents
Barcelona_CME#
*Jun 3 12:38:25.599: ISDN BR0/2/1 EVENT: process_rxstate: ces/callid 1/0x8007 calltype 2 HOST_DISCONNECT_ACK
Ian
06-03-2008 04:12 AM
Good news for layer 2 ;-)
Have you tried incoming calls?
It could be a problem with line coding or number/type presentation, channel selection...
Please send a show run, it will be easier to debug...
Thanks,
Fred
06-03-2008 04:16 AM
Hi Fred,
Below is a edited output of the run config
!
isdn switch-type basic-net3
!
!
trunk group 1
carrier-id Telefonica
description BRI Trunks
hunt-scheme sequential both
translation-profile outgoing 2
!
voice-card 0
!
!
!
!
!
!
!
!
!
!
!
!
!
!
voice translation-rule 1
rule 1 /^933436161/ /6161/
!
!
voice translation-profile 2
translate calling 2
!
voice translation-profile Default
translate called 1
!
!
interface BRI0/1/0
no ip address
shutdown
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
isdn skipsend-idverify
isdn static-tei 0
trunk-group 1
!
interface BRI0/1/1
no ip address
shutdown
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
isdn skipsend-idverify
isdn static-tei 0
trunk-group 1 5
!
interface BRI0/2/0
no ip address
shutdown
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
isdn skipsend-idverify
isdn static-tei 0
trunk-group 1 10
!
interface BRI0/2/1
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
!
voice-port 0/1/0
cptone ES
!
voice-port 0/1/1
cptone ES
!
voice-port 0/2/0
cptone ES
!
voice-port 0/2/1
cptone ES
!
!
!
dial-peer voice 1 pots
description Inbound PSTN Dial Peer
translation-profile incoming default
incoming called-number 6161
direct-inward-dial
!
dial-peer voice 10 pots
trunkgroup 1
description outbound all calls BRI
translation-profile outgoing 2
destination-pattern 0T
!
dial-peer voice 99 pots
translation-profile outgoing 2
destination-pattern 0093
port 0/2/1
prefix 093
!
!
telephony-service
no auto-reg-ephone
load 7941 TERM41.7-0-3-0S
max-ephones 30
max-dn 150
ip source-address 10.10.92.1 port 2000
url directories http://10.10.92.1/localdirectory
url services http://10.10.92.5/voiceview/common/login.do
url authentication http://10.10.92.5/voiceview/authentication/authenticate.do
user-locale ES
network-locale ES
time-format 24
dialplan-pattern 1 61.. extension-length 4
voicemail 6100
max-conferences 4 gain -6
moh moh1.wav
web admin system name admin password cisco
web admin customer name cmeadmin password administrat0r
dn-webedit
time-webedit
transfer-system full-consult
night-service day Sun 00:00 23:59
night-service day Mon 09:00 19:00
night-service day Tue 09:00 19:00
night-service day Wed 09:00 19:00
night-service day Thu 09:00 19:00
night-service day Fri 09:00 19:00
night-service day Sat 00:00 23:59
create cnf-files version-stamp 7960 Jun 03 2008 09:41:23
!
debug isdn q931 when dailing the spanish speaking clock on tel 093
!Barcelona_CME#
*Jun 3 14:03:43.287: ISDN BR0/2/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 6178
*Jun 3 14:03:43.287: ISDN BR0/2/1 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Called num 093
*Jun 3 14:03:43.287: ISDN BR0/2/1 Q931: TX -> SETUP pd = 8 callref = 0x15
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x81
Preferred, B1
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0080, '6178'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '093'
Plan:Unknown, Type:Unknown
Barcelona_CME#
*Jun 3 14:03:43.463: ISDN BR0/2/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x95
Cause i = 0x82E404 - Invalid information element contents
Regards
Ian
06-03-2008 04:27 AM
Hi,
The call is getting rejected by the carrier, and the cause code they send back to your router is:
Cause i = 0x82E404 - Invalid information element contents
So one of the information elements that the router is sending in the outgoing SETUP message is not correct. My guess is that the Bearer Capability is not correct. From your debugs, the bearer capability in the ougoing setup is 0x8090A2, which decodes to Voice/Speech call (u-law). Because the switch-type is Basic-net3, I think the call should be A-law instead (0x8090A3).
Try setting the compand-type to alaw under the voice port.
voice-port 0/2/1
compand-type a-law
ISDN Bearer Capability Values are defined here:
http://www.cisco.com/en/US/customer/docs/ios/12_3/debug/command/reference/dbg_ap2g.html#wp1003938
Regards,
Michael.
06-03-2008 04:35 AM
I agree with mowuor...
That's what we configured in Madrid...
Fred
06-03-2008 04:46 AM
Hi Michael,
perfect answer we are now able to make successful outgoing calls.
I only noe have a problem with the incoming now.
the telco is sending me the following 933436xxx and this is translated to an internal extension 6XXX however the call is unsuccessful.
*Jun 3 14:42:44.715: ISDN BR0/2/0 Q931: RX <- SETUP pd = 8 callref = 0x26
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x82
Preferred, B2
Calling Party Number i = 0x0183, '00447740937963'
Plan:ISDN, Type:Unknown
Called Party Number i = 0xA1, '933436164'
Plan:ISDN, Type:National
*Jun 3 14:42:44.727: ISDN BR0/2/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xA6
Channel ID i = 0x8A
Exclusive, B2
*Jun 3 14:42:44.743: ISDN BR0/2/0 Q931: TX -> DISCONNECT pd = 8 callref = 0xA6
Cause i = 0x8081 - Unallocated/unassigned number
Barcelona_CME(cfg-translation-rule)#
*Jun 3 14:42:44.843: ISDN BR0/2/0 Q931: RX <- RELEASE pd = 8 callref = 0x26
*Jun 3 14:42:44.847: ISDN BR0/2/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xA6
Ian
06-03-2008 04:54 AM
Hi Ian,
If dial-peer voice 1 is intended to be used for inbound calls, then change the incoming called-number statement from 'incoming called-number 6161' to 'incoming called-number .'
Let us know how this works.
Regards,
Michael.
06-03-2008 05:06 AM
We had origionally done that and set it to 6161 to see if it would work so in both instances we cannot get incoming calls.
show voice translation-rule is correct
and test voice translation-rule matches also.
Ian
06-03-2008 05:09 AM
Ian,
We should make sure that the incoming test call is using that dial-peer. Output of 'debug voip ccapi inout' will confirm that for us.
Did you also try it after specifying the port under the dial-peer?
Thanks,
Michael.
06-03-2008 05:15 AM
Hi Michael,
debug voip ccapi inout
*Jun 3 15:10:40.719: //-1/1054BAD48026/CCAPI/cc_api_display_ie_subfields:
cc_api_call_setup_ind_common:
cisco-username=
----- ccCallInfo IE subfields -----
cisco-ani=00447717290172
cisco-anitype=0
cisco-aniplan=1
cisco-anipi=0
cisco-anisi=3
dest=933436161
cisco-desttype=2
cisco-destplan=1
cisco-rdie=FFFFFFFF
cisco-rdn=
cisco-rdntype=-1
cisco-rdnplan=-1
cisco-rdnpi=-1
cisco-rdnsi=-1
cisco-redirectreason=-1 fwd_final_type =0
final_redirectNumber =
hunt_group_timeout =0
*Jun 3 15:10:40.719: //-1/1054BAD48026/CCAPI/cc_api_call_setup_ind_common:
Interface=0x658A859C, Call Info(
Calling Number=00447717290172,(Calling Name=)(TON=Unknown, NPI=ISDN, Screening=Network, Presentation=Allowed),
Called Number=933436161(TON=National, NPI=ISDN),
Calling Translated=FALSE, Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE,
Incoming Dial-peer=1, Progress Indication=NULL(0), Calling IE Present=TRUE,
Source Trkgrp Route Label=Telefonica, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1
*Jun 3 15:10:40.719: //-1/1054BAD48026/CCAPI/ccCheckClipClir:
In: Calling Number=00447717290172(TON=Unknown, NPI=ISDN, Screening=Network, Presentation=Allowed)
*Jun 3 15:10:40.723: //-1/1054BAD48026/CCAPI/ccCheckClipClir:
Out: Calling Number=00447717290172(TON=Unknown, NPI=ISDN, Screening=Network, Presentation=Allowed)
*Jun 3 15:10:40.723: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Jun 3 15:10:40.723: :cc_get_feature_vsa malloc success
*Jun 3 15:10:40.723: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Jun 3 15:10:40.723: cc_get_feature_vsa count is 1
*Jun 3 15:10:40.723: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Jun 3 15:10:40.723: :FEATURE_VSA attributes are: feature_name:0,fearture_time:1706154424,feature_id:94
*Jun 3 15:10:40.723: //94/1054BAD48026/CCAPI/cc_api_call_setup_ind_common:
Set Up Event Sent;
Call Info(Calling Number=00447717290172(TON=Unknown, NPI=IS
Barcelona_CME#DN, Screening=Network, Presentation=Allowed),
Called Number=933436161(TON=National, NPI=ISDN))
*Jun 3 15:10:40.723: //94/1054BAD48026/CCAPI/cc_process_call_setup_ind:
Event=0x6557CE50
*Jun 3 15:10:40.723: //94/1054BAD48026/CCAPI/ccCallSetContext:
Context=0x662CA1AC
*Jun 3 15:10:40.727: //94/1054BAD48026/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 94 with tag 1 to app "_ManagedAppProcess_Default"
*Jun 3 15:10:40.727: //94/1054BAD48026/CCAPI/ccCallProceeding:
Progress Indication=NULL(0)
*Jun 3 15:10:40.731: //94/1054BAD48026/CCAPI/ccCallDisconnect:
Cause Value=1, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
*Jun 3 15:10:40.731: //94/1054BAD48026/CCAPI/ccCallDisconnect:
Cause Value=1, Call Entry(Responsed=TRUE, Cause Value=1)
*Jun 3 15:10:40.731: //94/1054BAD48026/CCAPI/cc_api_get_transfer_info:
Transfer Number Is Null
*Jun 3 15:10:40.843: //94/1054BAD48026/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x658A859C, Tag=0x0, Call Id=94,
Call Entry(Disconnect Cause=1, Voice Class Cause Code=0, Retry Count=0)
*Jun 3 15:10:40.843: //94/1054BAD48026/CCAPI/cc_api_call_disconnect_done:
Call Disconnect Event Sent
*Jun 3 15:10:40.843: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
*Jun 3 15:10:40.843: :cc_free_feature_vsa freeing 65B1D9B0
*Jun 3 15:10:40.843: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
*Jun 3 15:10:40.843: vsacount in free is 0Barcelona_CME#
We are using A trunk group as we have 4 x BRI Circuits
Ian
06-03-2008 05:25 AM
Hi Ian,
In the debug we see 'Incoming Dial-peer=1', so it does match the expected dial-peer.
The called number from the debug is 933436161, which is what is specified in the voice translation-pattern.
One other item to correct - The name of the voice translation-profile is Default, with a capital 'D', but the one applied to the dial-peer has a lower case letter. Can we try again after changing the latter?
Thanks,
Michael.
06-03-2008 05:33 AM
Hi Michael,
Thank you for all your help it is always something simple that gets you.
We have had so many issues here and made that many changes.
I have checked a backed up config and it was origionally spelt correct in both locations.
Regards
Ian
06-03-2008 05:39 AM
Hi Ian,
I understand your sentiments - Happens to me a lot when I've been looking at a problem for too long and its too late in the night :-)
So, just to confirm, do your calls work correctly in both directions now?
Regards,
Michael.
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