- Joined
- May 26, 2010
- Messages
- 51
- Reaction score
- 0
Hi there,
I have upgraded to V11 and it works fine, except the below issue I faced since V8, still the same problem:
When I make call from another NEC phone system via SIP trunk, if call to existing 3CX extension, no any problem, regardless registered phone or forward to other party via outbound routing.
however, if dial a number which is go to other party via the outbound routing directly, then call failed.
for example:
I have setup :
1. extension 28000(forward all call to external number: 28133)
2. Ports/Trunks 27203/GXW4108 gateway
3. Outbound rules: prefix 28, route GXW4108, strip Digits 2
==> when I make call from SIP Trunk: dial 28000, the call will successfully go to port 27203, strip 28, and reach to 133 in another pbx system;
==> when I make call from SIP Trunk: dial 28133, call failed, with below log info: -- please help
there should not be credentials issue as the call go via Outbound Rules...
==> If dial from 3CX registered IP Phone, no any problem.
Regards,
Zhang
*************************** Server Activity Log ******************************************
26-07-2012 15:05:17.352 [CM102001]: Authentication failed for INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.100.4.238:5060;branch=z9hG4bK-3b5c50115cda30-241
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>
From: "22161"<sip:[email protected]:5060>;tag=83550115cda2b-241
Call-ID: [email protected]
CSeq: 2 INVITE
Session-Expires: 1800
Allow: INVITE, ACK, CANCEL, BYE, UPDATE, PRACK
Content-Type: application/sdp
Proxy-Authorization: Digest username="27100",realm="3CXPhoneSystem",nonce="414d535c06217d2d34:2d494eb83b8adf88e25b47fc884bfa96",uri="sip:[email protected]:5060",response="c10c26446b2bf92afc99ec99d42ed050",opaque=""
Supported: timer
Content-Length: 175
v=0
o=IPS 22875 0 IN IP4 10.100.4.243
s=IPS
c=IN IP4 10.100.4.243
t=0 0
m=audio 10104 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
I have upgraded to V11 and it works fine, except the below issue I faced since V8, still the same problem:
When I make call from another NEC phone system via SIP trunk, if call to existing 3CX extension, no any problem, regardless registered phone or forward to other party via outbound routing.
however, if dial a number which is go to other party via the outbound routing directly, then call failed.
for example:
I have setup :
1. extension 28000(forward all call to external number: 28133)
2. Ports/Trunks 27203/GXW4108 gateway
3. Outbound rules: prefix 28, route GXW4108, strip Digits 2
==> when I make call from SIP Trunk: dial 28000, the call will successfully go to port 27203, strip 28, and reach to 133 in another pbx system;
==> when I make call from SIP Trunk: dial 28133, call failed, with below log info: -- please help
there should not be credentials issue as the call go via Outbound Rules...
==> If dial from 3CX registered IP Phone, no any problem.
Regards,
Zhang
*************************** Server Activity Log ******************************************
26-07-2012 15:05:17.352 [CM102001]: Authentication failed for INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.100.4.238:5060;branch=z9hG4bK-3b5c50115cda30-241
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>
From: "22161"<sip:[email protected]:5060>;tag=83550115cda2b-241
Call-ID: [email protected]
CSeq: 2 INVITE
Session-Expires: 1800
Allow: INVITE, ACK, CANCEL, BYE, UPDATE, PRACK
Content-Type: application/sdp
Proxy-Authorization: Digest username="27100",realm="3CXPhoneSystem",nonce="414d535c06217d2d34:2d494eb83b8adf88e25b47fc884bfa96",uri="sip:[email protected]:5060",response="c10c26446b2bf92afc99ec99d42ed050",opaque=""
Supported: timer
Content-Length: 175
v=0
o=IPS 22875 0 IN IP4 10.100.4.243
s=IPS
c=IN IP4 10.100.4.243
t=0 0
m=audio 10104 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings