error cm500002

[wessexarch]

hi

I am testing the 3CX sofware - impressed so far - got everthing working but incoming DDI.
When I dial the DDI number i get the following error:-

[CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:[email protected]:5060;rinstance=1822ec27f83c8c26 SIP/2.0
Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bK32f4.b036b187.0
Via: SIP/2.0/UDP 91.151.11.20:5060;rport=5060;branch=z9hG4bK4ac17c078cb11b1b72f0190e766874c8
Max-Forwards: 9
Record-Route: [sip:91.151.2.130;lr=on;ftag=3424073642-63320]
Contact: [sip:[email protected]:5060]
To: [sip:[email protected]:5060]
From: [sip:[email protected]];tag=3424073642-63320
Call-ID: 5963-3424073642-63311@msx2-voip-unlimit ... domain.com
CSeq: 1 INVITE
Session-Expires: 3600;refresher=uac
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE
Call-Info: [sip:91.151.11.20];method="NOTIFY;Event=telephone-event;Duration=1000"
Supported: timer, 100rel
Allow-Events: telephone-event
Content-Length: 0


11:28:45.453 evt::CheckIfAuthIsRequired::not_handled [CM302001]: Authorization system can not identify source of: SipReq: INVITE [email protected]:5060 tid=32f4.b036b187.0 cseq=INVITE [email protected]:5060 / 1 from(wire)


I asked my voip provider (voip-unlimited) for help - who asked for a sip trace, which i provided, and they came back with the folloing reply:-

Packet 91 and 92 is asking us to authenticate with you ...
This is incorrect... please contact vendor if you are unsure about the settings..

I can't work out where my configuration is wrong - I have just used the voip-unlimited config as supplied - can anyone help me out?

Paul

 

[Anonymous]

Hi There,

As VOIP-Unlimted is a supported provider, I would suggest getting technical support on this one, you can contact our technical support (This requires commercial edition with support package). If you have a commercial edition, but no support package, you can purchase one here:

https://erp.3cx.com/orderform/support.aspx

With this we will be able to analyse Wireshark captures and check the problem.

If you have any further enquiries about our support packages please contact Chris Martin on [email protected]

Thanks,

 

[wessexarch]

Hi Keith

Thanks for the reply.

I am testing the free version at present and therefore don't have support.
So I thought I would try the forum because it would be nice to test with two extns with DDI.
My plan was (if i couldn't resolve the problem with help from the forum) I would continue testing without DDI and get it fixed after I have purchased a copy with support in a few days time.
I am happy with the product so far - I was just hoping I could fix this issue.

regards

Paul

 

[Anonymous]

Would it be possible to attach the trace and point out the lines the provider said were wrong packets?

Thanks,

 

[wessexarch]

Below is the reply sent to me from voip-unlimited.
Attached is the trace I sent them. (it's a pcap file renamed for upload)


Paul
..............................

Hi

Packet 91 and 92 is asking us to authenticate with you ...
This is incorrect... please contact vendor if you are unsure about the settings..

Thanks




INVITE sip:[email protected]:5060;rinstance=a538360e7252170a SIP/2.0

Record-Route: <sip:91.151.2.130;lr=on;ftag=3424435325-448372>

Max-Forwards: 9

Session-Expires: 3600;refresher=uac

Supported: timer, 100rel

To: <sip:[email protected]:5060>

From: <sip:[email protected]>;tag=3424435325-448372

Call-ID: 53045-3424435325-448363@msx2-voip-unlim ... domain.com

CSeq: 1 INVITE

Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE

Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bKfa01.7c8dec3.0

Via: SIP/2.0/UDP
91.151.11.20:5060;rport=5060;branch=z9hG4bK551ebba4c6ff36cfa8aefc52682608a6

Contact: <sip:[email protected]:5060>

Call-Info:
<sip:91.151.11.20>;method="NOTIFY;Event=telephone-event;Duration=1000"

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Length: 322



v=0

o=msx2-voip-unlimited-net 4153 9881 IN IP4 91.151.11.20

s=sip call

c=IN IP4 91.151.8.146

t=0 0

m=audio 62582 RTP/AVP 0 8 18 4 101

a=fmtp:101 0-16

a=rtpmap:101 telephone-event/8000

a=fmtp:4 annexa=no

a=rtpmap:4 G723/8000

a=fmtp:18 annexb=no

a=rtpmap:18 G729/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

INVITE sip:[email protected]:5060;rinstance=a538360e7252170a SIP/2.0

Record-Route: <sip:91.151.2.130;lr=on;ftag=3424435325-448372>

Max-Forwards: 9

Session-Expires: 3600;refresher=uac

Supported: timer, 100rel

To: <sip:[email protected]:5060>

From: <sip:[email protected]>;tag=3424435325-448372

Call-ID: 53045-3424435325-448363@msx2-voip-unlim ... domain.com

CSeq: 1 INVITE

Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE

Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bKfa01.7c8dec3.0

Via: SIP/2.0/UDP
91.151.11.20:5060;rport=5060;branch=z9hG4bK551ebba4c6ff36cfa8aefc52682608a6

Contact: <sip:[email protected]:5060>

Call-Info:
<sip:91.151.11.20>;method="NOTIFY;Event=telephone-event;Duration=1000"

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Length: 322



v=0

o=msx2-voip-unlimited-net 4153 9881 IN IP4 91.151.11.20

s=sip call

c=IN IP4 91.151.8.146

t=0 0

m=audio 62582 RTP/AVP 0 8 18 4 101

a=fmtp:101 0-16

a=rtpmap:101 telephone-event/8000

a=fmtp:4 annexa=no

a=rtpmap:4 G723/8000

a=fmtp:18 annexb=no

a=rtpmap:18 G729/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

SIP/2.0 407 Proxy Authentication Required

Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bKfa01.7c8dec3.0

Via: SIP/2.0/UDP
91.151.11.20:5060;rport=5060;branch=z9hG4bK551ebba4c6ff36cfa8aefc52682608a6

Proxy-Authenticate: Digest
nonce="12859916202:cb69779f36606881ba3dd7430f242c0a",algorithm=MD5,realm="3CXPhoneSystem"

To: <sip:[email protected]:5060>;tag=e5209426

From: <sip:[email protected]>;tag=3424435325-448372

Call-ID: 53045-3424435325-448363@msx2-voip-unlim ... domain.com

CSeq: 1 INVITE

User-Agent: 3CXPhoneSystem 5.1.4510.0

Content-Length: 0



SIP/2.0 407 Proxy Authentication Required

Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bKfa01.7c8dec3.0

Via: SIP/2.0/UDP
91.151.11.20:5060;rport=5060;branch=z9hG4bK551ebba4c6ff36cfa8aefc52682608a6

Proxy-Authenticate: Digest
nonce="12859916202:cb69779f36606881ba3dd7430f242c0a",algorithm=MD5,realm="3CXPhoneSystem"

To: <sip:[email protected]:5060>;tag=e5209426

From: <sip:[email protected]>;tag=3424435325-448372

Call-ID: 53045-3424435325-448363@msx2-voip-unlim ... domain.com

CSeq: 1 INVITE

User-Agent: 3CXPhoneSystem 5.1.4510.0

Content-Length: 0



ACK sip:[email protected]:5060;rinstance=a538360e7252170a SIP/2.0

Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bKfa01.7c8dec3.0

From: <sip:[email protected]>;tag=3424435325-448372

Call-ID: 53045-3424435325-448363@msx2-voip-unlim ... domain.com

To: <sip:[email protected]:5060>;tag=e5209426

CSeq: 1 ACK

Content-Length: 0



ACK sip:[email protected]:5060;rinstance=a538360e7252170a SIP/2.0

Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bKfa01.7c8dec3.0

From: <sip:[email protected]>;tag=3424435325-448372

Call-ID: 53045-3424435325-448363@msx2-voip-unlim ... domain.com

To: <sip:[email protected]:5060>;tag=e5209426

CSeq: 1 ACK

Content-Length: 0

 

[Anonymous]

Hi there,

The VOIP provider is wrong. This is the expected behaviour from the phonesystem. This is an issue on their end... please contact VOIP-Unlimited.

The packet shows 407 - Proxy Authentication Required, this is absolutely normal.

Keith

 

[wessexarch]

Thanks Keith

I'll send voip-unlimited the info and post back the results.

Paul

 

[wessexarch]

Hi Keith

I passed your response to Voip-Unlimited.
They came back with the below:-

Hi

We have hundreds of 3CX systems connected to us (and working fine) and none of them are setup this way as we cannot support authing to a UA ...

Despite what the 3CX engineer says this is not correct!!!

Thanks

 

[Anonymous]

As VOIP-UNLIMITED correctly say, many 3CX installations work fine (in fact, they are a supported provider).

This leads me to believe it is a problem with your configuration.

For further analysis though, you would need to submit a trouble ticket, which is part of the commercial service.

Thanks,

 

[wessexarch]

OK Keith

Thanks for your all your help on the forum.
I will continue to test without the DDI and sort it out when i have purchased the full version.

Paul

 

[lanrover]

Bro; same problem here. I am using DID's from DIDx. I worked around it by adding a generic sip provider (compat mode) specifying the ip address of the did provider in the from field of the invite as the host, etc. Then the only other config i did to the gateway is to specify that no auth to be used in or outbound then add the did in the appropriate field. Works now. I will post results as I play with the config. Seems to me like the option in the did config specifying from anywhere is not working. Take care and let me know if it works for you.

 

[dominicbatty]

Paul, I have a solution for your DDI / VOIP Unlimited problem but not worth me writing it up if you have already solved the issue. cheers, dom.

 

[martinpluss]

@domincbatty
I know this tread is a lifetime old - and I probally shouldn't reopen it, but I've just done an a new install of 3CX and am using voipunlimited and have the same issue with inbound auth (plus inbound audio doesn't work - only outbound).

If you can you throw any light into my deep ark pit of VoIP despair at this time of night I'd really appreciate it..

 

[eagle2]

Hi,

have you configured correctly the DDIs in your 3CX system ? What is the version of your 3CX system ?
Check this post also: http://www.3cx.com/blog/docs/source-identification-issues/

Check the system manual carefully, it is not so trivial. I mean you get the '407' error because of misconfiguration. In the 'Source ID' tab settings you must have selected 'Source Identification by DID', SIP field containing DID numbers should be 'Request Line URI: User Part', you must have added all DIDs in the field below; plus you must route each DID to specific destination, etc.

Regards