OXE to Cisco IP trunk

bigmac · Post by **bigmac** » 15 Jan 2010 10:21

Hi All,

t3 trace below. I have an IP link to CCM based on direct speed dial. was working ok but today no joy. The problem appears to be with B channel. I can ping CCM and he can ping me but to me it looks like I am not even getting out. Any assistance appreciated

Mac

Traces Analyser activated

mtracer started ...
(149912:000001) MTRACER host (10.248.92.57, xb0000), version: R9.0-h1.301-25-a-
e-c6s2
(149912:000001) MTRACER num: 005, time: 2010/01/15 15:01:26, loss: 0%
______________________________________________________________________________
| (150127:000002) 1123: Send_IO1 (link-nbr=15, sapi=0, tei=0) :
| long: 108 desti: 0 source: 15 cryst: 1 cpl: 26 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 1a
|______________________________________________________________________________
|
| [9f] Non-locking shift. codeset : 7
| [a2] EI_IP_TYPE_TERM
| [9f] Non-locking shift. codeset : 7
| IE:[05] EI_IP_INFOS (l=4) -> G729 Ece 1 Vad 0 Profil 2,
| IE:[06] UNKNOWN (l=1) c0
| [9f] Non-locking shift. codeset : 7
| IE:[07] EI_IP_QOS (l=3) 00 e0 00
| [9f] Non-locking shift. codeset : 7
| IE:[0a] EI_RTP_INFO (l=30)
| -> stop_packet=0 stop_rtp=0 h323=0 wc=0 rf=0 udp=1 rqm=0
| -> Transm_Bande=1 detection_Q23=1 dtmf_payload=96
| -> Port RTP = 32028, IPv4 : 10. 248. 92. 63.
| -> Port RTCP SR = 32029, IPv4 : 10. 248. 92. 63.
| -> Port RTCP RR = 32029, IPv4 : 10. 248. 92. 63.
| -> Port Fax = 32031, IPv4 : 10. 248. 92. 63.
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a8 83 81 -> T2 : No B channel
| IE:[6c] CALLING_NUMBER (l=10) -> 01 81 Num : 61606500
| IE:[70] CALLED_NUMBER (l=9) -> 81 Num : 88616900
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|______________________________________________________________________________

______________________________________________________________________________
| (150128:000004) Concatenated-Physical-Event :
| long: 21 desti: 0 source: 0 cryst: 1 cpl: 26 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 80 1a
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=1) a8 -> T2 : No B channel
|______________________________________________________________________________

______________________________________________________________________________
| (150128:000005) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 1 cpl: 26 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 80 1a
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 fe -> [fe] GOING IN CONVERSATION STATE
|______________________________________________________________________________

______________________________________________________________________________
| (150128:000006) 1123: Send_IO1 (link-nbr=15, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 1 cpl: 26 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : 00 1a
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e4 08 -> [e4] INVALID INFORMATION ELEMENT CONTENTS
|______________________________________________________________________________

tincho.rn · Post by **tincho.rn** » 15 Jan 2010 16:34

Hi. You are using H323. Just an idea, I do not know if it will work. In mgr --> System, look for Ignore ISDN Cause Invalid Content. Turn it YES. Regards.

freedom · Post by **freedom** » 15 Jan 2010 17:32

Perhaps a very drastic way, but did you try a reboot?
You say it has been working up-to now. Did someone changed the configuration on either OXE or Cisco side?

bigmac · Post by **bigmac** » 16 Jan 2010 03:43

Hi Freedom,

I know we didn't change anything and as you would expect the Cisco side are claiming the same....Tried a reboot of int-ip then reboot of system but no joy. Will try
tincho.rn idea. To be honest I think this is a CCM issue but Cisco engineer "unavailable" until next week so will need to wait for then to perform any meaningful diagnosis.

tincho.rn · Post by **tincho.rn** » 17 Jan 2010 12:43

You are right bigmac, I didn't notice CCM was releasing the call. Regards.

Post by **frank** » 20 Jan 2010 23:04

I'm nowhere to be a pro with CCM, but is the NO B CHANNEL normal ?

Post by **vad** » 20 Jan 2010 23:21

frank wrote:I'm nowhere to be a pro with CCM, but is the NO B CHANNEL normal ?

For H.323 yes. As I remember (f.e. H323 IP TG between two OXE) - in outgoing t3 trace we will see B-channel but in incoming t3 trace we will see "no B channel".

alex · Post by **alex** » 21 Jan 2010 02:49

frank wrote:I'm nowhere to be a pro with CCM, but is the NO B CHANNEL normal ?

Sure it is OK. Remember, that H.323 is not a "circuit-mode", but a "packet-mode" communication. So no circuit (or channel)need to be indicated in SETUP message.

Elandryl · Post by **Elandryl** » 21 Jan 2010 04:32

Hi Bigmac,

Can you explain more specifically the architecture ?
Do you have something like that :
CCM == MGCP/H323/SIP => GW == H323 => INTIPB/GD
Or something else ?

I found something looking weird for me but maybe i'm wrong.
I think :" IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3" mean we are using G711 compression.
But in the setup : "IE:[05] EI_IP_INFOS (l=4) -> G729 Ece 1 Vad 0 Profil 2,"

Which could explain the release error : "INVALID INFORMATION ELEMENT CONTENTS"

bigmac · Post by **bigmac** » 21 Jan 2010 09:40

Hi CCM is on H323 no GW in between. I never spotted the G729 element this looks like it could be it. Does this mean the CCM is using G729 or something is forcing me to go from G711 to G729?

Thanks

M