Remote SPA942 issue after v11 installed

[amygoda]

Hello,
After installation for v11 the call rejected
It was work on v10
Thank You

19:17:50.375 [CM502001]: Source info: From: <sip:[email protected]>;tag=27a62d3d29d33e25o0"Sister Hanan"<sip:[email protected]>
19:17:50.375 [CM503013]: Call(19): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=-4543468a cseq=INVITE [email protected]:5071 / 102 from(wire)
19:17:49.906 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 172.17.99.101:5071;branch=z9hG4bK-e72f47ed;received=41.234.245.35
Max-Forwards: 70
Contact: <sip:[email protected]:5071>
To: "Sister Hanan"<sip:[email protected]>
From: <sip:[email protected]>;tag=27a62d3d29d33e25o0
Call-ID: [email protected]
CSeq: 101 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
User-Agent: Linksys/SPA941-5.1.8
Content-Length: 0

19:17:49.906 [CM302001]: Authorization system can not identify source of: SipReq: INVITE [email protected] tid=-e72f47ed cseq=INVITE [email protected]:5071 / 101 from(wire)
19:17:42.453 [CM502001]: Source info: From: <sip:[email protected]>;tag=48d377f2e4c8e7c9o0"Brother Ahmed"<sip:[email protected]>
19:17:42.453 [CM503013]: Call(18): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=-c9a629a cseq=INVITE [email protected]:5071 / 102 from(wire)
19:17:41.984 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 172.17.99.101:5071;branch=z9hG4bK-cb700089;received=41.234.245.35
Max-Forwards: 70
Contact: <sip:[email protected]:5071>
To: "Brother Ahmed"<sip:[email protected]>
From: <sip:[email protected]>;tag=48d377f2e4c8e7c9o0
Call-ID: [email protected]
CSeq: 101 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
User-Agent: Linksys/SPA941-5.1.8
Content-Length: 0

 

[leejor]

If you have remote extensions that are contacting 3CX using a URL rather than the 3CX locations public IP, you need to insure that the URL is filled in the Domain Name setting in 3CX. In your example con00.abc.com

I'm not sure why that would change after the upgrade, if it was working previously.

 

[amygoda]

Hello Leejor,
Thank you
I'll try it
but it was not required in previous V.