Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Oneway Voice issue observe when we call from Cisco-Avaya,never receive Call message from Avaya side

Status
Not open for further replies.

farazshamsi

IS-IT--Management
Mar 24, 2015
19
PK
I have observed one way voice when we call from cisco PABX (A) to Avaya PABX (B) as Cisco PABX can hear the voice of Avaya PABX, but Avaya PABX Cannot hear the Voice of Cisco PABX.Although Calling from Avaya to Cisco no issue observed and below are the Call logs and detail so any one let me know why avaya cannnot generate call connect message as I have tried everything nothing is work

Call Flow: Cisco Phone ---sip--Cisco PABX---h323----Cisco Gatekeepr------h323-----Cisco Gateway-------h323----Avaya PABX---h323--Avaya Phone

I have analyzed debugs from both CME and GW (CUBE).
++I could see that this was a fast start call with early media and RTP ports are established both direction in GW as well as in CME .

++However, I could not see call is getting connected here.
++On GW, call is matching dial-peer 8001 and sending call to Avaya PBX (192.168.37.31).
++We could see that “call proceeding” and “call Alerting” message coming from Avaya side. But we never receive a “call connect” message from Avaya side.
++And we disconnect call from SIP phone side by sending a CANCEL after 1:30 minutes ( if call was actually connected, SIP phone should have send a BYE)

*Mar 28 11:47:45.761: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:8@192.168.65.225;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.65.232:5060;branch=z9hG4bK04a63e68
From: "OM" <sip:5903@192.168.65.225>;tag=0041d2b36e870150148896de-214324e4
To: <sip:8@192.168.65.225>
Call-ID: 0041d2b3-6e87007d-68bd6401-4b532ad1@192.168.65.232
Max-Forwards: 70Date: Mon, 28 Mar 2016 11:47:53 GMT
CSeq: 101 CANCEL
User-Agent: Cisco-CP7821/10.3.1
Content-Length: 0


From the captures we collected, it is very clear that there is no “H225 connect” message coming from Avaya side.
As discussed, please collect similar capture from Avaya PBX and check if h225 messages are going out to network. If yes, please involve your network team to check why the connect messages are not reaching Cisco router.


 
do a status station on the Avaya phone when the call is up, and maybe turn off direct IP audio on the H323 Avaya trunk and see if pinning the call down to an Avaya gateway helps.
 
Dear Kyle

Is might be Routing issue that why Avaya Cannot generate H225 connect message ? And how we can take packet capture on Avaya so please share the step in details

Avaya Model:S8300 B G700 CM (4.0

Anyway thanks
 
I honestly doubt you've got a routing issue from CM - if your H323 trunk is up, it wouldn't be routing.

If you go in the CM terminal, and do a "status station 1234" if your Avaya phone were 1234, while the call is up, you'll see the media path for that call. You can also "list trace station 1234" and see a live trace.

Check the difference calling Avaya to Cisco and vice versa. In your H323 signaling group, you can set direct media. Maybe you have a routing issue between the phone (not CM and the gateway) and your Cisco environment and in one circumstance your Avaya endpoint is sending or receiving audio to/from an IP it can't reach.
 
Please find the below trace

17:58:19 idle station 8008 cid 0x2aa
17:58:22 Calling party trunk-group 3 member 1 cid 0x2ad
17:58:22 Calling Number & Name 5904 UT 1
17:58:22 active trunk-group 3 member 1 cid 0x2ad
17:58:22 dial 8008
17:58:22 ring station 8008 cid 0x2ad
17:58:22 G729 ss:eek:ff ps:20 rn:8/1 172.16.26.11:16756 192.168.37.35:2066
17:58:22 xoip: fax:Relay modem:eek:ff tty:US 192.168.37.35:2066 uid:0x50009
17:58:24 active station 8008 cid 0x2ad
17:58:24 G711MU ss:eek:ff ps:20 rn:1/1 192.168.32.143:3318 192.168.37.35:2076
17:58:24 xoip: fax:Relay modem:eek:ff tty:US 192.168.37.35:2076 uid:0x7
VOIP data from: 192.168.37.35:2076
17:58:33 Jitter:1 0 0 0 0 0 0 0 1 0: Buff:8 WC:19 Avg:0
17:58:33 Pkloss:0 0 1 0 0 2 0 1 0 0: Oofo:0 WC:2 Avg:0
17:58:35 idle station 8008 cid 0x2ad
17:59:23 TRACE COMPLETE trunk-group 3 cid 0x0
 
Ok, so is this a Cisco phone calling your Avaya one with the problem of the Avaya phone not being able to hear the Cisco one?

What are the IPs of the phones and gateways involved?

It seems you've got a G729 stream set up from 172.16.26.11 to a 192.168.37.35.
That .37.35 is transcoding to 711 and sending to 192.168.32.143.

What are all of those things?

This is where playign with things like shuffling, direct and indirect IP audio and network region connectivity factor in to how that call is set up.
 
hi,

Yes problem to be reported when cisco calling to Avaya Phone not being able to hear cisoo Phone

Cisco Calling number 5904 Avaya Gateway 192.168.37.35
Avaya Calling number 8008 Cisoo Gateway 172.16.26.11 where Avaya PABX connected

Call Flow: Cisco Phone ---sip--Cisco PABX---h323----Cisco Gatekeepr------h323-----Cisco Gateway (172.16.26.11)-------h323----Avaya PABX---h323--Avaya Phone
 
make sure the cisco gateway can reach the IP network that the telephone is in not just the network the Avaya PBX is in.
 
Hi All,

Thank for the input, My issue has resolved after adding the DSp resource command on cisco router
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top