Forwarding Incoming Calls

[10m]

Good day Guys.

I have got a GoIP (GSM gateway) connected to my network to allow me make outgoing calls and receive calls from outside. I want the gateway to forward the ID of the caller to the 3CX server so they can be identified using the company phone book. My challenge is I keep getting this error :

30-Mar-2015 13:02:43.922 [CM102001]: Authentication failed for AuthFail Recv Req INVITE from xxx.xxx.xxx.7:5060 tid=971824389 [email protected]:

I've tried fiddling with the outbound parameters but I am not making any headway.

In the body of the error I see that the ID of the caller is in the log, but the call will not go through.

On the same gateway though, I am able to make outgoing calls.

Any help?


Thank you

 

[leejor]

To clarify....You cannot receive any incoming calls as a result of what ever is causing the error log? Or you do get calls, just no Caller ID?

As you've hidden the IP, I cannot tell if it is a public IP, or a local IP (locals IP's don't need to be concealed).

 

[10m]

Thanks for your response Leejor.

The device (ie the GSM gateway) allows you to forward the ID of the caller to 3CX. When this feature is set, I get the error and what characterizes the error is that the 3CX PBX can make a call out on the device but cannot receive a call. That is when I get the error.

The full error log is displayed below

30-Mar-2015 13:02:43.922 [CM102001]: Authentication failed for AuthFail Recv Req INVITE from 172.20.11.7:5060 tid=971824389 [email protected]:
INVITE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 172.20.11.7:5060;rport=5060;branch=z9hG4bK971824389
Max-Forwards: 30
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>
From: "0803401xxxx"<sip:[email protected]:5060>;tag=974495270
Call-ID: [email protected]
CSeq: 3 INVITE
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REFER, REGISTER, MESSAGE, INFO, SUBSCRIBE
Content-Type: application/sdp
Proxy-Authorization: Digest username="90001",realm="3CXPhoneSystem",nonce="414d535c0b29cc6317:86aa1f68329d97301e2666cc2cbca1fe",uri="sip:[email protected]",response="6ffdfd3f2a84415819694a8e787572d1",algorithm=MD5
User-Agent: dble
Content-Length: 280
Remote-Party-ID: "0803401xxxx" <sip:[email protected]>;party=calling;screen=no;privacy=off

v=0
o=dble 1427717036 1427717036 IN IP4 172.20.11.7
s=dble
c=IN IP4 172.20.11.7
t=0 0
m=audio 16384 RTP/AVP 8 0 18 4 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings


Thank you

 

[10m]

Hi Everyone.

I have got my problem solved. It all was in the GoIP. I had to make a few configuration changes to the device as seen in the screenshot attached.

Once I did this, there were no errors and the caller IDs were transferred from the device to the 3CX PBX and they were matched against entries in the company phonebook and Viola,..... Caller ID Displayed.

Thanks.

 

[leejor]

When creating trunk groups in 3CX, they usually start with 10000 and count up. I see you have the gateway as 90001. Does that match the trunk number in the PBX? You also appear to be sending the call to 1001, is that supposed to be a trunk group (missing a digit), or an extension number?

 

[10m]

Hi Leejor.

90001 is the virtual extension number that was assigned the gateway by 3CX. It should have been 10000 but when I installed v12.5 I noticed that it was assigned 90001. I think the problem was in the configuration of the GoIP, when the CID forward mode was set to Remote Party ID, it worked with the extension 1001. When I set the CID Forward Mode to Use CID as SIP Caller ID, it resulted in the authentication error. Setting the Forward Number (PSTN to VoIP) as the virtual number of the gateway corrected the authentication issue.

I got the idea after reading a post relating to the same problem but the poster had issues with a Polycom Soundstation.

 

[leejor]

So...you got it working?

 

[10m]

Yes I did.