Can Ooh323 Work With Cisco Router?
hello every body,
i have big problem to configure h323 trunk between cisco router and asterisk 11.13.1 which uses ooh323 module. any body knows if ooh323 module can work with cisco routers or not???? (in gateway mode, it is ok and register in cisco gatekeeper but i can not configure trunk h323)
any comments or hints are really appreciated. SAM
5 thoughts on - Can Ooh323 Work With Cisco Router?
06.05.2015 10:06, s m пишет:
we use chan_ooh323 with cisco for long time with some issues, but… only issue is not solved in current asterisk version is https://issues.asterisk.org/jira/browse/ASTERISK-24400
so you have to be more specific in your “big problem” description 😉
—
hello Dmitry
thank you for your reply. Ok, you are right. i want to configure trunk h323
between asterisk 11.13.1 and 2800 cisco router. this is my scenario:
PBX(100)—>cisco—>asterisk11.13.1—->PBX(200)
when i call from 100 to 200, everything is ok but when i call from 200 to
100, phone rings but after i answer it, i have no voice and call terminates after 5 seconds. this is ooh323 debug(in asterisk11.13.1 system):
ooh323_get_rtp_peer OOH323/peer-2-5 -> (null):0, 1
this ia h322_log:
10:42:10:835 Processing MakeCall command ooh323c_o_3
10:42:10:835 Created a new call (outgoing, ooh323c_o_3)
10:42:10:835 Enabled RTP/CISCO DTMF capability for (outgoing, ooh323c_o_3)
10:42:10:835 Enabled RFC2833 DTMF capability for (outgoing, ooh323c_o_3)
10:42:10:835 Dtmf mode set to H.245(alphanumeric) for (outgoing, ooh323c_o_3)
10:42:10:835 Dtmf mode set to H.245(signal) for (outgoing, ooh323c_o_3)
10:42:10:835 INFO: FinCall returned 80494a048 for call: ooh323c_o_3
10:42:10:835 INFO: FinCall returned 80494a048 for call: ooh323c_o_3
10:42:10:835 INFO: create cmd connect for call: 80494a048
10:42:10:846 Processing MakeCall command ooh323c_o_3
10:42:10:846 INFO: FinCall returned 80494a048 for call: ooh323c_o_3
10:42:10:846 Parsing destination 192.168.0.139:1720
10:42:10:846 Trying to connect to remote endpoint(192.168.0.139:1720)
(IPv4) to setup H2250 channel (outgoing, ooh323c_o_3)
10:42:10:847 H2250 transmiter channel creation – successful (outgoing, ooh323c_o_3)
10:42:10:847 Determining IP address for outgoing call in multihomed mode.
(outgoing, ooh323c_o_3)
10:42:10:847 Using local ip 192.168.0.71 for outgoing call(multihomedMode). (outgoing, ooh323c_o_3)
10:42:10:847 Building OpenLogicalChannel for Receive Capability
(outgoing, ooh323c_o_3)
10:42:10:848 Created new logical channel entry (outgoing, ooh323c_o_3)
10:42:10:848 Receive channel of type audio started (outgoing, ooh323c_o_3)
10:42:10:848 Building OpenLogicalChannel for transmit Capability
(outgoing, ooh323c_o_3)
10:42:10:848 Created new logical channel entry (outgoing, ooh323c_o_3)
10:42:10:848 Added 2 fast start elements to SETUP message (outgoing, ooh323c_o_3)
10:42:10:848 Built SETUP message (outgoing, ooh323c_o_3)
10:42:10:848 Sending Q931 message (outgoing, ooh323c_o_3)
10:42:10:848 Sent Message – Setup (outgoing, ooh323c_o_3)
10:42:10:861 H.225 Call Proceeding message received (outgoing, ooh323c_o_3)
10:42:10:884 H.225 Alerting message received (outgoing, ooh323c_o_3)
10:42:10:884 Built terminal capability set message (outgoing, ooh323c_o_3)
10:42:10:884 Building Facility message for tunneling OOTerminalCapabilitySet (outgoing, ooh323c_o_3)
10:42:10:884 Sending Q931 message (outgoing, ooh323c_o_3)
10:42:10:884 Sent Message – Facility(OOTerminalCapabilitySet) (outgoing, ooh323c_o_3)
10:42:10:884 Tunneled Message – TerminalCapabilitySet (outgoing, ooh323c_o_3)
10:42:10:889 H.225 Facility message Received (outgoing, ooh323c_o_3)
10:42:10:889 Unsupported cap type encountered. Ignoring. (outgoing, ooh323c_o_3)
10:42:10:889 Unsupported cap type encountered. Ignoring. (outgoing, ooh323c_o_3)
10:42:10:889 Unsupported data capability type
10:42:10:889 Unsupported cap type encountered. Ignoring. (outgoing, ooh323c_o_3)
10:42:10:889 Unsupported cap type encountered. Ignoring. (outgoing, ooh323c_o_3)
10:42:10:889 Unsupported cap type encountered. Ignoring. (outgoing, ooh323c_o_3)
10:42:10:889 Unsupported cap type encountered. Ignoring. (outgoing, ooh323c_o_3)
10:42:10:889 Built TerminalCapabilitySet Ack (outgoing, ooh323c_o_3)
10:42:10:889 Building Facility message for tunneling OOTerminalCapabilitySetAck (outgoing, ooh323c_o_3)
10:42:10:889 Sending Q931 message (outgoing, ooh323c_o_3)
10:42:10:889 Sent Message – Facility(OOTerminalCapabilitySetAck)
(outgoing, ooh323c_o_3)
10:42:10:889 Tunneled Message – TerminalCapabilitySetAck (outgoing, ooh323c_o_3)
10:42:10:890 H.225 Facility message Received (outgoing, ooh323c_o_3)
10:42:10:890 Master Slave Determination received (outgoing, ooh323c_o_3)
10:42:10:890 Determining master-slave based on StatusDeterminationNumber
(outgoing, ooh323c_o_3)
10:42:10:890 Built MasterSlave determination Ack (outgoing, ooh323c_o_3)
10:42:10:890 Building Facility message for tunneling OOMasterSlaveAck
(outgoing, ooh323c_o_3)
10:42:10:890 MasterSlaveDetermination done – Master(outgoing, ooh323c_o_3)
10:42:10:890 Sending Q931 message (outgoing, ooh323c_o_3)
10:42:10:890 Sent Message – Facility(OOMasterSlaveAck) (outgoing, ooh323c_o_3)
10:42:10:890 Tunneled Message – MasterSlaveDeterminationAck (outgoing, ooh323c_o_3)
10:42:10:890 H.225 Facility message Received (outgoing, ooh323c_o_3)
10:42:10:894 H.225 Facility message Received (outgoing, ooh323c_o_3)
10:42:10:894 Listing logical channel 1001 cap 2 state 4 for (outgoing, ooh323c_o_3)
10:42:10:894 Listing logical channel 1002 cap 2 state 4 for (outgoing, ooh323c_o_3)
10:42:10:894 Opening logical channels (outgoing, ooh323c_o_3)
10:42:10:894 Looking for matching capabilities. (outgoing, ooh323c_o_3)
10:42:10:894 Created new logical channel entry (outgoing, ooh323c_o_3)
10:42:10:895 Built OpenLogicalChannel-OO_G711ALAW64K (outgoing, ooh323c_o_3)
10:42:10:895 Building Facility message for tunneling OOOpenLogicalChannel
(outgoing, ooh323c_o_3)
10:42:10:895 Sending Q931 message (outgoing, ooh323c_o_3)
10:42:10:895 Sent Message – Facility(OOOpenLogicalChannel) (outgoing, ooh323c_o_3)
10:42:10:895 Tunneled Message – OpenLogicalChannel(1003). (outgoing, ooh323c_o_3)
10:42:21:947 H.225 Release Complete message received (outgoing, ooh323c_o_3)
10:42:21:947 Cause of Release Complete is 10. (outgoing, ooh323c_o_3)
10:42:21:947 Closing H.245 connection (outgoing, ooh323c_o_3)
10:42:21:947 In ooEndCall call state is – OO_CALL_CLEARED (outgoing, ooh323c_o_3)
10:42:21:947 Cleaning Call (outgoing, ooh323c_o_3)-
reason:OO_REASON_REMOTE_CLEARED
10:42:21:947 Clearing all logical channels (outgoing, ooh323c_o_3)
10:42:21:947 Stopped Receive channel 1001 (outgoing, ooh323c_o_3)
10:42:21:947 ERROR: No Open LogicalChannels – Failed FindLogicalChannelByChannelNo (outgoing, ooh323c_o_3
10:42:21:947 Removing call 80494a048: ooh323c_o_3
10:42:21:947 Removed call (outgoing, ooh323c_o_3) from list
10:42:21:947 Ending Call Monitor thread
cisco debug shows rtp message with src address 0.0.0.0. i really don’t know how i should fix it. please help me.
thanks SAM
06.05.2015 10:58, s m пишет:
Hello!
I’m not h323 expert, may be somebody else can understand from this log what is happening, but I can’t 🙁
Could you, please, provide log with
tracelevel=6
in ooh323.conf ?
Thank you!
—
hello
thanks Dmitry for your useful hints. i enable debug and solve my problem:). it was codec compatibility problem. but it is so strange; if i set codec g711alaw in cisco router and asterisk, i have the mentioned problem but if i set codec to transparent in cisco router, every thing will be ok. is there any difference between g711 codecs which cisco and asterisk utilize?
07.05.2015 08:17, s m пишет:
Hello!
I don’t know, but I hit almost the same problem last time I connected cisco and asterisk- I had to enable more codecs , we use g711, but I had to allow don’t remember which . May be this is bug in asterisk in codecs negitiation. Unfortunately, I
was busy and know that chan_ooh323 was very busy at time, so I didn’t create bug report. If you have logs , may be it is good idea to report bug.
Thank you!
—