Yate server > SIP to H.323 proxy

Yate sending an incorrect address to PBX

(1/3) > >>

hilander:
Dear developers. We propose to use your product YATE as a converter H.323 signaling to SIP and back (H.323 to SIP Signaling Proxy). Acquainted with the recommendations:
http://docs.yate.ro/wiki/H323_To_SIP_Signaling_Proxy,
http://yate.null.ro/pmwiki/index.php?n=Main.H323ToSIPSignallingProxy
Connection diagram :
IPGW Panasonic (H.323, UDP) - YATE - MS Lync (SIP, TCP).
At the moment, the connection from the MS Lync towards PBX succeeds (Signalling, voice) .
When callback (PBX-MS Lynk) connection failed. When analyzing the trace call that during the exchange of signaling messages YATE towards PBX sends a broadcast address xxx.xxx.xxx.255 . And a voice PBX directed to that broadcast address xxx.xxx.xxx.255. We can send settings YATE, success and failure trace calls. If you will need additional information, I send. Prompt what went wrong

marian:
Yes, we need the log (configuration would help also).

Start yate with -Dt to see the debug message time.
Also start it with max debug level: -vvvvv
Message sniffer would help also (see http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages)

hilander:
OK!
first file: bad call from PBX with numbers 1032  to MS Link number 01032 
second file: successful call from a MS Link number 01032  to PBX number 1032

marian:
So you have an H323 issue.
I can't see the problem: the failed H323 call is not even routed.

I'm not sure I can help you with h323, but:

You should post the h323chan.conf file along with a wireshark capture and yate log.
Set debug=10 in h323chan.conf, 'general' section. This will put a lot of debug from H323 library.

hilander:
IP GW PBX address 10.1.64.100, call from 1032 to 01032
Yate address 10.1.64.63

Navigation

[0] Message Index

[#] Next page