- Joined
- Jun 25, 2008
- Messages
- 9
- Reaction score
- 0
Hi,
We're evaluating 3CX and so far we're very impressed. We're working on testing our current T1 using a CIsco 1760 we alreay have in place. After some tweaking, we've managed to get the outbound calls working. We're hitting a wall with inbound. The way our Cisco is configured is to not use authentication.
We've configured the SPTN gateway in 3cx to not use authentication. We then had some errors in the logs about not identifying the source ([CM302001]: Authorization system can not identify source of...). We've subsequently gotten those errors to disappear.
According to all of our settings, the incoming call should now work. We have a DID set and evrything looks good. Wehn we test it, all the caller hears is ringing. There are no log entries in the Server Status screen. We captured some packets and it seems that the server is receiving the invite and challenging with a SIP 407 Proxy Authentication required. In the 3CXPhoneSystem.trace.log I have the following lines:
12:38:24.875|.\ServerAuthManager.cxx(48)|Trace5|Resip|::ResipLogger:ServerAuth requested info (requiresChallenge) SipReq: INVITE [email protected]:5060 tid=1343125 cseq=INVITE [email protected]:5060 / 101 from(wire)<br>
12:38:24.875|.\CM_Stack.cpp(192)|Trace5|SipStack|CallMgr::Stack::isMyExternalIP:Compare IPs: incoming=10.1.10.119; external=65.161.85.50<br>
12:38:24.875|.\CM_Stack.cpp(202)|Trace5|SipStack|CallMgr::Stack::isMyExternalIP:IPs do not match!<br>
12:38:25.187|.\ServerAuthManager.cxx(64)|Trace5|Resip|::ResipLogger:ServerAuth got ChallengeInfo ChallengeInfo 0 : 1<br>
12:38:25.187|.\ServerAuthManager.cxx(394)|Trace5|Resip|::ResipLogger:Sending challenge to SipReq: INVITE [email protected]:5060 tid=1343125 cseq=INVITE [email protected]:5060 / 101 from(wire)<br>
12:38:25.187|.\ServerAuthManager.cxx(84)|Trace5|Resip|::ResipLogger:ServerAuth challenged request (after async) SipReq: INVITE [email protected]:5060 tid=1343125 cseq=INVITE [email protected]:5060 / 101 from(wire)<br>
Shouldn't the server not be challenging if the source identifier matches?
What am I missing?
Thanks.
Eric
We're evaluating 3CX and so far we're very impressed. We're working on testing our current T1 using a CIsco 1760 we alreay have in place. After some tweaking, we've managed to get the outbound calls working. We're hitting a wall with inbound. The way our Cisco is configured is to not use authentication.
We've configured the SPTN gateway in 3cx to not use authentication. We then had some errors in the logs about not identifying the source ([CM302001]: Authorization system can not identify source of...). We've subsequently gotten those errors to disappear.
According to all of our settings, the incoming call should now work. We have a DID set and evrything looks good. Wehn we test it, all the caller hears is ringing. There are no log entries in the Server Status screen. We captured some packets and it seems that the server is receiving the invite and challenging with a SIP 407 Proxy Authentication required. In the 3CXPhoneSystem.trace.log I have the following lines:
12:38:24.875|.\ServerAuthManager.cxx(48)|Trace5|Resip|::ResipLogger:ServerAuth requested info (requiresChallenge) SipReq: INVITE [email protected]:5060 tid=1343125 cseq=INVITE [email protected]:5060 / 101 from(wire)<br>
12:38:24.875|.\CM_Stack.cpp(192)|Trace5|SipStack|CallMgr::Stack::isMyExternalIP:Compare IPs: incoming=10.1.10.119; external=65.161.85.50<br>
12:38:24.875|.\CM_Stack.cpp(202)|Trace5|SipStack|CallMgr::Stack::isMyExternalIP:IPs do not match!<br>
12:38:25.187|.\ServerAuthManager.cxx(64)|Trace5|Resip|::ResipLogger:ServerAuth got ChallengeInfo ChallengeInfo 0 : 1<br>
12:38:25.187|.\ServerAuthManager.cxx(394)|Trace5|Resip|::ResipLogger:Sending challenge to SipReq: INVITE [email protected]:5060 tid=1343125 cseq=INVITE [email protected]:5060 / 101 from(wire)<br>
12:38:25.187|.\ServerAuthManager.cxx(84)|Trace5|Resip|::ResipLogger:ServerAuth challenged request (after async) SipReq: INVITE [email protected]:5060 tid=1343125 cseq=INVITE [email protected]:5060 / 101 from(wire)<br>
Shouldn't the server not be challenging if the source identifier matches?
What am I missing?
Thanks.
Eric