GXW-4004 not able to make outbound calls

[KTech99]

Replaced a bad GXW-4004 with a new one. Setup new one just like old. Able to receive calls but not make calls.

 

[leejor]

What do the 3CX logs show when a call is presented to the gateway? Just a time-out, or some other message?

Loading the same config file into an identical box should be pretty straight forward, one would think. I'm wondering if there are some options that the config file doesn't "deal" with.

 

[KTech99]

this is what I get when I try to make a call, at the bottom of the file is where i reset the 4004

04-Aug-2015 13:58:29.868 Leg L:1834.1[Unknown:] is terminated: Cause: BYE from PBX
04-Aug-2015 13:58:29.862 [CM502001]: Source info: From: "130"<sip:[email protected];user=phone>;tag=1762410600; To: <sip:[email protected];user=phone>
04-Aug-2015 13:58:29.862 [CM503013]: Call(C:1834): Incoming call rejected, caller is unknown; msg=Ivite-IN Recv Req INVITE from 10.10.10.106:5062 tid=1403375659 [email protected]:
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/UDP 10.10.10.106:5062;branch=z9hG4bK1403375659;rport=5062
Max-Forwards: 70
Route: <sip:10.10.10.140:5060;lr>
Contact: "130"<sip:[email protected]:5062;user=phone>
To: <sip:[email protected];user=phone>
From: "130"<sip:[email protected];user=phone>;tag=1762410600
Call-ID: [email protected]
CSeq: 11 INVITE
Accept: application/sdp, application/dtmf-relay
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE
Content-Type: application/sdp
Proxy-Authorization: Digest username="130",realm="3CXPhoneSystem",nonce="414d535c0bd19c5535:14a58eb7fa66fbbef8eb4832e6adc2ce",uri="sip:[email protected];user=phone",response="a575d66532d3cac6414ff5a1401a76e1",algorithm=MD5
Supported: replaces, path, timer, eventlist
User-Agent: Grandstream GXW-4004 V1.5A 1.0.12.4 chip V2.2
Privacy: none
P-Preferred-Identity: "130" <sip:[email protected];user=phone>
Content-Length: 451

v=0
o=130 8002 8000 IN IP4 10.10.10.106
s=SIP Call
c=IN IP4 10.10.10.106
t=0 0
m=audio 5008 RTP/AVP 0 8 4 18 2 97 102 100 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:4 G723/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:2 G726-32/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=20
a=rtpmap:102 G729E/8000
a=rtpmap:100 AAL2-G726-16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16,32-36,54
04-Aug-2015 13:57:29.589 [CM504001]: Endpoint Extn:122: new contact is registered. Contact(s): [sip:[email protected]:5066 / 122]
04-Aug-2015 13:57:29.405 Got REGISTER for foreign registrar: registrar host <sip10.10.10.140.5060:5060> is not mine!
04-Aug-2015 13:57:28.288 [CM504001]: Endpoint Extn:121: new contact is registered. Contact(s): [sip:[email protected]:5064 / 121]
04-Aug-2015 13:57:27.926 Got REGISTER for foreign registrar: registrar host <sip10.10.10.140.5060:5060> is not mine!
04-Aug-2015 13:57:26.822 [CM504008]: Fax Service: Fax.130 registered as sip:[email protected] with contact sip:[email protected]:5062;user=phone
04-Aug-2015 13:57:26.576 Got REGISTER for foreign registrar: registrar host <sip10.10.10.140.5060:5060> is not mine!
04-Aug-2015 13:57:25.451 [CM504001]: Endpoint Extn:106: new contact is registered. Contact(s): [sip:[email protected]:5060 / 106]
04-Aug-2015 13:57:25.086 Got REGISTER for foreign registrar: registrar host <sip10.10.10.140.5060:5060> is not mine!

 

[leejor]

Incoming call rejected, caller is unknown;

This is why it doesn't like the call.

Was there a previous, successful, registration for this extension?

 

[KTech99]

It shows all the extensions registered in the extension list

 

[complex1]

Hi,

Got REGISTER for foreign registrar: registrar host <sip10.10.10.140.5060:5060> is not mine!

This is the cause of the issue.
I had this before with an external device, but can’t remember how I solved it.
Some settings in the GXW are wrong. (Not corresponding or equal with the settings in 3CX)

 

[leejor]

I missed that.

Looks like the IP, somewhere in the GXW was put in incorrectly. 10.10.10.140.5060 At some point you put in the IP that had the port number "tacked on" to it. See the DOT before the port number.

 

[KTech99]

Thanks for the help, I did fat finger the IP address in the gateway. All working now.