I have an AS5850 configured as a SIP Gateway and as a H323 Gateway. I'm planning to use this equipment as an interconnection point between PSTN,SIP and H323.
I already have a functional H323 Network with ISDN trunks to the pstn and it is working fine. I added SIP configuration to the AS5850 in order to be able to route calls out to the PSTN or H323 remote ends coming from a SIP Phone registered with a third-party SIP Proxy.
When the calls coming from the SIP Phone goes to a PSTN destination the calls completes properly, but i am having problems trying to send calls coming from the SIP phone to a remote h323 gateway(also cisco)
Attached is my configuration and the error i'm getting in my cdr. It seems that the "ext" number of the phone is being used as destination string in the last call leg, but i'm not sure.
dial-peer voice 100 pots
dial-peer voice 102 pots
dial-peer voice 103 voip
incoming called-number 001T
session protocol sipv2
session target ipv4:20X.21X.17X.1X
.Mar 24 2004 18:31:42.620 GMT: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 9F74CE17 7D2A11D8 82A09B41 D2C3D418, SetupTime .18:31:42.470 GMT Wed Mar 24 2004, ***PeerAddress 2006***, PeerSubAddress , DisconnectCause 3 , DisconnectText no route to destination (3), ConnectTime .18:31:42.620 GMT Wed Mar 24 2004, DisconnectTime .18:31:42.620 GMT Wed Mar 24 2004, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
Attached you can find the debug ccsip messages output.
There are 2 solutions here.
1. Use of SIP/H.323 Signalling Gateway as the protocol convertor. Search google will yield heaps of hits on this subject. Product available both commercial and open source, trial, etc. Using this method means that the SIP End Point will communicate with H.323 End Point without going out the PSTN. I believe this is what you want to achieve in the long term. You are trying the AS5xxx as the protocol convertor for you, which it will not work. A call flow will be something like SIP IP Phone->SIP Server->SIP-to-H.323 Gateway->H.323 Gatekeeper->H.323 End Point. Of couse there is a SIP server that do the protocol convertor in the same box but the functionality is the still the same. Performance and concurrent call setup differ from products to products. Going for this solution would require you to find such products and test it on the your network.
2. If you do not wish to try on Soluton 1, this solution is a workaround way by not getting device but using the existing equipment that you have right now. Onto whether this good long term solution for depends on what you want to achieve both in term of commercially and technically. A call flow will be SIP End Point->SIP Server->Voice Gateway (AS5xxx)->PSTN Switch(ISDN/PRI)->Voice Gateway->H.323 Gatekeeper>H.323 End Point. The key is the Voice session must traverse the ISDN link. In other words your dial pattern must be setup is such as way that will go out thru the dial peer pots to pstn switch then come back to another dial-peer pots. I am not saying this is the most efficient way of doing it, I merely suggesting a workable way to achieve your desired goal without soluton 1.
Hopes you get better understanding now.