• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

MWI SPA921 & GXP2000 Not working

Status
Not open for further replies.
Thanks Andy and Michael, just tried firmware 1.1.4.17 and I stil ahve he same problem, so it looks like somehign I have missed on the 3cx config (if it has to be different to a GXP2000) or there is somehing in the GXP2020 config thta is different, though I thought they were primarily the same account pages.

I do hope its not an isolated case/problem I have.


Phil
 
i have send you a mail

silentfun said:
hi phil

you have interesting emailadress (arbeitmachen) it is a german word. are you speaking german ?

i have added some firmware´s for the gxp-2020 as a zip file

GXP_1.1.4.17 and GXP_1.1.5.15

and the gxp config in 3 pages also zipped

Andy
 
Thanks for he help so far. I have installed the earlier firmware, and thansk to Andy for a copy of the account config, where I found the only difference was I had not set rfc sysmetry routing. However, I still get
403 Forbidden, your request is not allowed on the phone when I try to make a call on the GXP2020. I can receive calls no problem.

If I put an existing working extension number in he GXP2020 that doesnt work either.

Your help would be appreciated.

Phil

I have appended the log, which as you can see says the incoming caller is unknown.

:[CM503008]: Call(4): Call is terminated
:[CM502001]: Source info: From: 4; To: "Acc1"[sip:[email protected];user=phone];tag=12fe72edcaafee9f[sip:[email protected];user=phone]
:[CM503012]: Call(4): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=78007e99fe85a60f cseq=INVITE [email protected]:5110 / 30689 from(wire)
:[CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/UDP 90.155.90.190:5110;branch=z9hG4bKc4994499944c8a0f;rport=5110
Max-Forwards: 70
Contact: [sip:[email protected]:5110;transport=udp;user=phone]
To: [sip:[email protected];user=phone]
From: "Acc1"[sip:[email protected];user=phone];tag=12fe72edcaafee9f
Call-ID: [email protected]
CSeq: 30688 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK, MESSAGE
Supported: replaces, timer, path
User-Agent: Grandstream GXP2020 1.1.4.17
Content-Length: 0
:[CM302001]: Authorization system can not identify source of: SipReq: INVITE [email protected] tid=c4994499944c8a0f cseq=INVITE [email protected]:5110 / 30688 from(wire)
:[CM504001]: Ext.103: new contact is registered. Contact(s): [sip:[email protected]:63268;transport=udp/103]
 
I wonder if Admin or someone could pass comment on my log results above please.

I've just configured a GXP2000 straight out of the box on the same extension as above and that works fine. Obviously something different between the GXP2000 and GXP2020, but what?

Thanks in anticipation.


Phil
 
Ok we still have the problem, it did go away on one phone then all of a sudden one extension number on the GXP2020 would not make calls (it would receive), all the other 5 lines could. The follwoing is a net mon log followed by he 3cx log of he attempted call from ext 107 to 101.

Note his is with a Grandstream GXP2020 but the same problem also occured on a snom320 which at the moment is behaving ok.

So can the 3cx team explain what the logs are actualy telling me. Note the leading '0's in line 10 and 13 of the 3cx log which should not be there. They are correspondingly in the text shown in the net mon log but not in he actual address. is 3cx server placing these leading 0s and causing the server itself to not reconixe a caller.

1 0.000000 NetmonFilter NetmonFilter: Updated Capture Filter: None
2 0.000000 NetworkInfoEx NetworkInfoEx: Network info for PCPC_14, Network Adapter Count = 1
3 0.000000 90.155.90.176 90.155.90.174 SMB SMB: C; Logoff Andx
4 0.000000 90.155.90.174 90.155.90.176 SMB SMB: R; Logoff Andx
5 0.000000 90.155.90.176 90.155.90.174 SMB SMB: C; Tree Disconnect
6 0.000000 90.155.90.174 90.155.90.176 SMB SMB: R; Tree Disconnect
7 0.125000 90.155.90.176 90.155.90.174 TCP TCP: Flags=....A..., SrcPort=4445, DstPort=Microsoft-DS(445), Len=0, Seq=2375985575, Ack=4267867986, Win=16424 (scale factor not found)
8 1.265625 90.155.90.169 90.155.90.174 SDP SDP: Session Name=SIP Call, Version=0
9 1.593750 90.155.90.174 90.155.90.169 SIP SIP: Response: SIP/2.0 407 Proxy Authentication Required
10 1.609375 90.155.90.169 90.155.90.174 SIP SIP: Request: ACK sip:[email protected] SIP/2.0
11 1.625000 90.155.90.169 90.155.90.174 SDP SDP: Session Name=SIP Call, Version=0
12 1.968750 90.155.90.174 90.155.90.169 SIP SIP: Response: SIP/2.0 403 Forbidden
13 1.984375 90.155.90.169 90.155.90.174 SIP SIP: Request: ACK sip:[email protected] SIP/2.0
14 4.406250 90.155.90.180 90.155.90.174 ARP ARP: Request, 90.155.90.180 asks for 90.155.90.174
15 4.406250 90.155.90.174 90.155.90.180 ARP ARP: Response, 90.155.90.174 at 00-11-09-19-84-BC
16 4.421875 90.155.90.180 90.155.90.174 SIP SIP: Request: REGISTER sip:90.155.90.174 SIP/2.0
17 4.750000 90.155.90.174 90.155.90.180 SIP SIP: Response: SIP/2.0 200 OK
18 6.468750 90.155.90.170 90.155.90.191 UDP UDP: SrcPort = 32770, DstPort = 32770, Length = 36
19 11.109375 90.155.90.162 90.155.90.174 SIP SIP: Request: REGISTER sip:90.155.90.174 SIP/2.0
20 11.437500 90.155.90.174 90.155.90.162 SIP SIP: Response: SIP/2.0 200 OK

20:39:03.578 CallCtrl::eek:nIncomingCall [CM502001]: Source info: From: 10; To: "Acc107"[sip:[email protected]];tag=40d2ecbdc9cd2a70[sip:[email protected]]
20:39:03.578 CallCtrl::eek:nIncomingCall [CM503012]: Call(10): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=d63fe88fe7c74ba3 cseq=INVITE [email protected]:5110 / 53891 from(wire)
20:39:02.890 evt::CheckIfAuthIsRequired::not_handled [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 90.155.90.169:5110;branch=z9hG4bK30218798b3adc613
Max-Forwards: 70
Contact: [sip:[email protected]:5110;transport=udp]
To: [sip:[email protected]]
From: "Acc107"[sip:[email protected]];tag=40d2ecbdc9cd2a70
Call-ID: [email protected]
CSeq: 53890 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK, MESSAGE
Supported: replaces, timer, path
User-Agent: Grandstream GXP2020 1.1.5.15
Content-Length: 0
20:39:02.890 evt::CheckIfAuthIsRequired::not_handled [CM302001]: Authorization system can not identify source of: SipReq: INVITE [email protected] tid=30218798b3adc613 cseq=INVITE [email protected]:5110 / 53890 from(wire)
 
Hi,

3CX PBX doesn't modify (in log) any messages that were received(or sent). We are using it as a source of information.
If you don't believe then try to capture network traffic using third party tool.

Regards
 
Thanks for the reply Stephan. So what are the leading 0s in he log, they dont appear in the address field of NETMON but they do in the text (the top dump I have shown).

The botom dump is the log from 3cx which shows the leading 0s in the text.

The PC the system is rnning on is only running 3cx. Note existing devices GXP2000 and HT486, HT487 and eybeam all work fine. This problem only occures on new devices (not extension numbers) added to the server.


This problems showed up on a GXP2020 but also on a snom320.

Phil
 
Hi Stephan you'll be pleased to know that the problem has been cured. Ross at 3cx UK (ZEN) simulated my exact problem, and discovered the cure almost simulatniously with me, as I'd just set up a GXP2000 with and without leading 0s in the server address lines in the phones and thats when I discovered it was the case.

I had been placing leading 0 in the server address in the phone config, now bear in mind that the devices were registering fine with the 3cx server using this configuration allowing the devices to receive calls, but not make them. Maybe this is an oversight in the application??


Thanks to Andy (Silentfun) and Paul for their help in confirming GXP2020 were not an issue on 3cx.

Thanks

Phil
 
Re:

Philco said:
:[CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:103@090.155.090.174;user=phone SIP/2.0
Via: SIP/2.0/UDP 90.155.90.190:5110;branch=z9hG4bKc4994499944c8a0f;rport=5110
Max-Forwards: 70
Contact: [sip:[email protected]:5110;transport=udp;user=phone]
To: [sip:[email protected];user=phone]
From: "Acc1"[sip:[email protected];user=phone];tag=12fe72edcaafee9f
Call-ID: [email protected]
CSeq: 30688 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK, MESSAGE
Supported: replaces, timer, path
User-Agent: Grandstream GXP2020 1.1.4.17
Content-Length: 0
:[CM302001]: Authorization system can not identify source of: SipReq: INVITE [email protected] tid=c4994499944c8a0f cseq=INVITE [email protected]:5110 / 30688 from(wire)
:[CM504001]: Ext.103: new contact is registered. Contact(s): [sip:[email protected]:63268;transport=udp/103]

This (selected) will not work. You need to force GXP to send proper IP (90.155.90.190).
 
Thats correct Archie, see my post above. Works fine now

I had not noticed that I had omitted the leading zeros in all the other devices I already had on the 3cx server.


Interesting that 3cx allowed the registration ok.


Thanks

Phil
 
It seems REGISTER has correct address in request line.
 
Indeed. 3cx ignores (or accepts) the leading 0s on registration but not on Session request.

Nice when it works though...

Phil
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,630
Messages
748,955
Members
144,746
Latest member
gamingpro2131
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.