> Ok, now I see all signalling messages in pcap files. > (unfortunately your xml trace file does not contain the whole call...).
Hmm, there is nothing in the xml file I left out. I will try to create a new one. > I do not change my opinion: Don't take me wrong, I have no idea about SIP / VoIP so far but just try to read anything and try to understand as much as possible. And I'm glad that someone tries to help me. The HD voice peer to peer is just something I read while trying to fix the problem. > You do not have voice because one of your polycom phones (200) does not [...] > sipxproxy process thinks, that it has address 192.0.2.254. Which is > GGRROOSSSSLLYY wrong. I'm think you're right, the .254 in nattraversalrules.xml and sipxbridge.xml is definitly wrong. But I can't remember that i've entered that ip address anywhere. > It may happen if you (by mistake) configured 192.0.2.254 address > somewhere in sipx configuration. What is in /etc/sipxpbx/sipXproxy-config > file? (Do not edit it manually). 192.0.2.254 is in use by the phone 200 and the grep here show some entries in /etc/sipxpbx. Ok, no problem I will reinstall sipXecs again and will record everything I enter. [root@sipxecs sipxpbx]# grep 254 * nattraversalrules.xml: <publicaddress>192.0.2.254</publicaddress> sipxbridge.xml: <global-address>192.0.2.254</global-address> --- BOFM /etc/sipxpbx/sipXproxy-config --- SIPX_PROXY_DEFAULT_EXPIRES : 300 SIPX_PROXY_DEFAULT_SERIAL_EXPIRES : 20 SIPX_PROXY_HOST_NAME : sipxecs.einbeck.tk.anolo.de SIPX_PROXY_HOST_ALIASES : 192.0.2.10:5060 sipxecs.einbeck.tk.anolo.de:5060 SIPX_PROXY_LOG_CONSOLE : SIPX_PROXY_LOG_DIR : SIPX_PROXY_LOG_LEVEL : DEBUG SIPX_PROXY_MAX_FORWARDS : SIPX_PROXY_STALE_TCP_TIMEOUT : SIPX_PROXY_TLS_PORT : 5061 SIPX_PROXY_TCP_PORT : 5060 SIPX_PROXY_UDP_PORT : 5060 SIPX_PROXY_CALL_STATE : SIPX_PROXY_CALL_STATE_LOG : SIPX_PROXY_CALL_STATE_DB : ENABLE SIPX_PROXY_AUTHENTICATE_ALGORITHM : SIPX_PROXY_AUTHENTICATE_REALM : einbeck.tk.anolo.de SIPX_PROXY_HOSTPORT : 192.0.2.10:5060 SIPX_PROXY_HOOK_LIBRARY.200_xfer : /usr/lib/authplugins/libTransferControl.so SIPX_PROXY_HOOK_LIBRARY.205_subscriptionauth : /usr/lib/authplugins/libSubscriptionAuth.so SIPX_PROXY.205_subscriptionauth.PACKAGES_REQUIRING_AUTHENTICATION : dialog SIPX_PROXY.205_subscriptionauth.TARGETS_EXEMPTED_FROM_AUTHENTICATION : ^~~rl~ SIPX_PROXY_HOOK_LIBRARY.210_msftxchghack : /usr/lib/authplugins/libMSFT_ExchangeTransferHack.so SIPX_PROXY.210_msftxchghack.USERAGENT : ^RTCC/ SIPX_PROXY_HOOK_LIBRARY.300_calldestination: /usr/lib/authplugins/libCallDestination.so SIPX_PROXY_HOOK_LIBRARY.400_authrules : /usr/lib/authplugins/libEnforceAuthRules.so SIPX_PROXY.400_authrules.RULES : /etc/sipxpbx/authrules.xml SIPX_PROXY.400_authrules.IDENTITY_VALIDITY_SECONDS : 300 SIPX_PROXY_HOOK_LIBRARY.700_fromalias : /usr/lib/authplugins/libCallerAlias.so SIPX_PROXY_HOOK_LIBRARY.900_ntap : /usr/lib/authplugins/libNatTraversalAgent.so SIPX_PROXY_HOOK_LIBRARY.990_emergnotif: /usr/lib/authplugins/libEmergencyNotify.so SIPX_PROXY.990_emergnotif.EMERGRULES : /etc/sipxpbx/authrules.xml SIPX_PROXY_HOOK_LIBRARY.995_requestlinter: /usr/lib/authplugins/libRequestLinter.so --- EOF --- > Of course the above is just a guess, that I can make looking at your > trace... I will report after the sipXecs 4.2.1 reinstall in a few minutes. -- Claas Hilbrecht http://www.jucs-kramkiste.de _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
