I'm testing some TEHO configs in lab (for redundancy/disaster recovery, not really for toll-bypass). I have 2 2811's on the same network segment, each with a single POTS. I configured an h.323 gateway to a ccm 4.1 cluster for the sole purpose of placing test calls and testing inbound POTS delivery.
The purpose of my testing is to pass a call to router1 with 2 dial-peers - pref 1 routes to router2, pref 2 routes out the POTS on router1. I have the same configs in place on router2. I haven't gotten around to adding RSVP configs because I'm not getting RTP on all call legs.
From a phone registered to ccm, I place a test call to router1. The pref 1 dial-peer routes the call to router2. Router1 shows 2 active call legs - both h.323 (ccm to gateway & gateway to gateway). Router2 shows 2 active call legs - 1 telephony and 1 h.323 (router1 to router2 & POTS). The call rings to a 2nd test phone via the PSTN. I answer, and get no RTP either way and the call disconnects after 7-8secs every time.
I've attached the configs for both routers. Both are running c2800nm-adventerprisek9_ivs-mz.124-24.T.bin.
I've tried adding the h225 connect-passthru statement to both routers but it's still the same -- no audio and the call disconnects 7-8 secs after answering it.
I can dial either of the 2 POTS (1 to each router) and ring my desk phone with 2 way audio. Right now the 2 dial-peers are setup as pref 1 - ipipgw, pref 2 - pstn. If I flip the preferences (cucm phone - isr - pots), I get 2 way audio.
It's only when I'm routing from cucm - isr 1 - isr 2 - pots (or vice versa) that I get no audio and the call disconnects.
I've only got g711ulaw in the voice class codec ref'd by all voip dial-peers. I found a Cisco page (can't find it now though) which specifically covered 1/no way audio issues, but didn't help me.
I'm not sure where to go from here, what debugs to run, etc.
A debug voice rtp shows this though which I'm sure is a problem:
I don't recall that this was ever resolved. Shortly after opening the tac case, my contract with that company ended. I doubt anything was done on this after I left since it was sort of a pet project of mine. I'll try to reach out to the remaining engineer who I believe is still working for that company and post again if he ever got it working.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...