Cisco router 2611(IP-IP gateway) and Cisco CallManager Compatability Issue
I have the following network.
Cisco SIP Phones (3322) <-> SIP Express Router (non-cisco SIP Proxy router) <-> SIPH323 Converter (non-cisco) <-> Cisco router 2611XM (acting as IP to IP Gateway) <-> Cisco CallManager <-> Cisco Skinny Phones (1133).
First Problem (SIP->Skinny):
When I call from SIP phone to skinny phone, the skinny phone rings. But when I take the hook, it gives me busy tone. I see from ethereal that the router is sending H.225.0 cs: Release Complete message to CallManager. My router dial-peer config is
dial-peer voice 300 voip
dest pattern 1133
session target CM's IP address
and my CallManager configuartion is: I use my default device pool that has default region using codec g711. I could also see that cisco skinny IP phone config. in CallManager uses default device pool defined above.
Second problem (Skinny->SIP):
The same network configuartion is assumed. When I call from Skinny to SIP phone, the SIP phone just rings once. The SIP phone doesn't seem to ring continuosly (could not hear the dail tone) but shows a missed call from skinny phone.
When I traced the call flow using ethereal, I see again the following
|----------->| H.225.0 cs:Alerting
|<-----------| H.245 TerminalCapabiltySet
|----------->| H.245 Terminal CapabiltySet
|----------->| H.245 MasterSlaveDetermination
|<-----------| H.245 TerminalCapabaility Ack
|----------->| H.225.0 cs:Release Complete
My dial-peer config is
dial-peer voice 201 voip
dest patt 3322
sess tar. SIP Proxy's IP
So, the conclusion is in both cases the router is sending Release complete message to CallManager. So I guess there is some capability mismatch between router and CallManeger. I guess SIPH323 is flexible to use any codec and SIP Express Router also supports any codec scheme.
Having given these problems, my Questions are
1. Could anyone direct me to a document explaining how to configure a Cisco IP to IP gateway router (Cisco 2611XM).
2. similarly aboutconfiguartion related to cisco callmanager releated to this issu.e
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...