Configuring Grandstream GXW4104 FXO via SBC

Status
Not open for further replies.

JCubio

Free User
Joined
Oct 7, 2019
Messages
134
Reaction score
13
Hi all,

Is there any documentation/instructions out there on how to configure a grandstream fxo via SBC?
According here, it will work but I can't find an actual documenation.

I'm a total newbie in voice technologies specially gateway devices so I do rely on documentations.

TIA
 
Officially it isn't supported.

I typically provision locally and then update the SIP server address to point to the SBC.
 
Am I doing it right sir?
SBC IP = 192.168.0.62

13313
Provisioning link from 3CX
13315
 
Looks correct to me, although the real test is... does it register/work?
 
It does register now.
I can do an outbound but not inbound.
3CX can see the inbound call from logs but can't place it to the extension

Do you have an idea where do I need to change sir?
 
So when not behind a SBC, does inbound work?

Can you direct call an extension from another?

I suspect not and it's likely the SBC is not the cause. You need to post full logs, I suspect an inbound rule is incorrect.
 
So when not behind a SBC, does inbound work?
I haven't tested that one sir. Our 3CX is in cloud

As for the logs, this is what I see

11/28/2019 5:17:04 PM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
Invite-UNK Recv Req INVITE from 127.0.0.1:5080 tid=0286f4f380555123 [email protected]:
INVITE sip:[email protected]:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---0286f4f380555123;rport=5080
Via: SIP/2.0/UDP [::ffff:58.69.59.97]:26830;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.895f4bb6
Via: SIP/2.0/UDP 192.168.0.63:5060;branch=z9hG4bK0286f4f380555123
Max-Forwards: 68
Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.895f4bb6>
Record-Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.895f4bb6>
Proxy-Require: 192.168.0.62
Contact: <sip:192.168.0.63:5060>
To: <sip:002@ourfqdn:5060>
From: <sip:Private@ourfqdn:5060>;tag=eee526136ee4b683
Call-ID: [email protected]
CSeq: 27906 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK
Content-Type: application/sdp
Proxy-Authorization: Digest username="",realm=""
Supported: replaces, timer, path
User-Agent: Grandstream GXW4104 (HW 2.3, Ch:2) 1.4.1.5
Content-Length: 279

v=0
o=system 8002 8002 IN IP4 192.168.0.63
s=SIP Call
c=IN IP4 127.0.0.1
t=0 0
m=audio 14126 RTP/AVP 0 8 4 18 3 2
a=sendrecv
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:4 G723/8000
a=rtpmap:18 G729/8000
a=rtpmap:3 GSM/8000
a=rtpmap:2 G726-32/8000
a=ptime:20
 
Is this a 3CX support SIP provider?

Can you direct call an extension from another?
 
Normally, our inbound and outbound works from standard SIP trunks (we have DIDLogic and mVoice)
The one I'm referring to is the inbound from the grandstream gateway
 
My bad - Didn't read clearly enough to see you were doing a FXO (not FXS).

The log shows an issue - it's not getting source ID.
Code:
11/28/2019 5:17:04 PM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
Invite-UNK Recv Req INVITE from 127.0.0.1:5080 tid=0286f4f380555123 Call-

I'll bow out of this - perhaps someone else can assist - without access and more specific information it's complicated for me to troubleshoot over a forum.

You might want to see if any changes here help (SIP Trunks-The Grandstream):
13316
 
Last edited:
  • Like
Reactions: JCubio
FYI if you don't want to configure the SBC IP address manually in the device (to risk possibly a reset removing the settings for example) you might want to look at extracting and altering the primary template for the device (creating a custom one) and simply changing the 3CX address to SBC in there and then applying it to the box.
 
Hi All,
Inbound and outbound now works.
Now I'm adding the 2nd PSTN Line. But how do I specify the outbound rule to use a specific line?
 
  • Like
Reactions: karjune
But how do I specify the outbound rule to use a specific line.
You would have to create each line as an individual trunk, or use a gateway that allows a prefix digit to specify the line. I believe that some Grandstreams will do the latter.
 
Last edited:
This is solved
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,934
Messages
589,821
Members
164,813
Latest member
divdigital