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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP OFFICE - CISCO SPA112 NO Audio After Transfer

Status
Not open for further replies.

PCovarrubias

IS-IT--Management
Oct 19, 2012
9
MX
Scenario: Avaya IP 500v2 with 1608 & 1603 IP Phones. Also, SIP endpoints (Cisco ATA SPA112 & Polycom Conference Phones). I can make calls from either type of device, and audio is flawless.

The Problem: If I receive a call from a Cisco SPA112 on an Avaya 1608/1603, everything works fine. BUT when I transfer this call from the Avaya IP Phone to another Avaya IP Phone, the original SIP Enpoint (Only on ATA SPA112) theres no audio on call, although the Avaya Phone still hears audio coming from the ATA.

Notes.
[li]This only happens while making an ASSISTED TRANSFER. When a BLIND TRANSFER takes place, audio works both ways.[/li]
[li]Happens with ALLOW DIRECT MEDIA PATH on/off.[/li]
[li]Codec is the same when Audio gets through and when it doesn't G711U[/li]
[li]Tried to replicate the error using POLYCOM and BRIA softphone. Audio gets through just fine.¿.[/li]

 
How your LAN is setup?

Were Cisco and IPO in the same network range?

I've experienced this one but not with CISCO, it is because IPO was not in the same network range of the end-user/softphone. This might be same case yours.
 
I have a 10.100.10.x LAN for Avaya Phones. On the SIP side 172.16.x.x, We have different external LANs but everything is routed through a gateway and IP Route on IPO has been programmed. Just finished testing connecting the CISCO ATA directly on the 10.100.10.x voice network and same result. The funny thing is, this only happens on ASSISTED TRANSFERS not on BLIND TRANSFERS. And only on CISCO ATA not on Polycom. Also on IP Office, Fixed SIP Extn for just using 6711A Codec, no change...
 
Problem was on CISCO SPA112. A new firmware came out, upgraded, problem solved!
 
Can you share your config for setting up the SPA112 on the Cisco and Avaya side. thanks
 
You better try to figure it out yourself as then you understand how it works which simplifies fault finding and avoid you to come back here complaing it not to work as it is in the example as you don't know what you are doing.

Learning a ape a trick is easy, learning a ape how the trick works is a challenge
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top