• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
HP Recommended

Hi 

We have a problem with QDX 6000 afterchanging ISP. We have changed ip address in NAT config in QDX and since then it doesnt work.

Below part of log:

 

2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Conn[0]: dialing 195.116.18.200 at 1920Kbps
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Conn[0]: state:"disconnected" --> "connecting"
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: state:"disconnected" --> "allocated"
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM call state 0 allocated
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Conn[0]: adding call:H323Call[0]
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM connection callAdded 0 0 h323 h323
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: state:"allocated" --> "offHook"
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: state:"offHook" --> "dialing"
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM call state 0 offHook
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM call state 0 dialing
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM connection state 0 connecting
2014-01-21 13:50:20 DEBUG avc: pc[0]: h323nat: localIP = "10.42.62.100", farIP = "195.116.18.200", localIP is non-routable but farIP is.
2014-01-21 13:50:20 DEBUG avc: last message repeated 1 times
2014-01-21 13:50:20 DEBUG avc: pc[0]: uimsg: A146f: 20000 audiocallmix video codec
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: disconnected, unreachable cause code :3
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: state:"dialing" --> "disconnecting"
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM call state 0 disconnecting
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Conn[0]: state:"connecting" --> "disconnecting"
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: hangup, cause code 3
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM connection lastNumber 0 "195.116.18.200"
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM connection state 0 disconnecting
2014-01-21 13:50:20 DEBUG avc: pc[0]: --------------- Number of connected calls: 0 -------------
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: Gatekeeper confirmed our DRQ or we timed out waiting for a response; end the call.
2014-01-21 13:50:20 INFO avc: pc[0]: H323Call[0]: outgoing disconnected, cause code:3
2014-01-21 13:50:20 WARNING avc: pc[0]: outgoing h323 call to 195.116.18.200, rate 1920, disconnected with cause code 3
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Call[0]: state:"disconnecting" --> "disconnected"
2014-01-21 13:50:20 DEBUG avc: pc[0]: NOTIFY: COMM call state 0 disconnected 3
2014-01-21 13:50:20 DEBUG avc: pc[0]: H323Conn[0]: deleting call - H323Call[0]
2014-01-21 13:50:20 INFO avc: pc[0]: H323Conn[0]: H323Call[0] deleted, address:195.116.18.200
2014-01-21 13:50:21 DEBUG avc: pc[0]: NOTIFY: COMM connection callDeleted 0 0
 

 

 

so it says lacal is non routeable but it is NATed on Cisco ASA and pings and traceroute works good. WAN ip is entered in Nat configuration of polycom and same address is entered on Cisco ASA as static nat. 

Please help- what can i do?

2 REPLIES 2
HP Recommended

Is the ASA set up for H.323 traffic?

HP Recommended

Hi All,

 

I have same issue with HDX 7000 HD polycom device. We able to make internal network VC call but public IP VC call just not happening. We having same error log messages on Polycom logs files. ISP even confused why this is like this. After so many conversation they detach filrewall and initial VC traffic now visible on TMG Proxy but still VC not successfull to public IPs.


  

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.