Cannot make oubound calls thru D-Link DIV-140 as PSTN

[skrodzkim]

I think I have the proper setup of the lines but things aren't working. I have been reading thru some of the posts regarding similar issues but no resolve. Below is the log I keep getting...

16:52:57.913 Terminated c7 "Mark Skrodzki"<sip:[email protected];user=phone> <sip:[email protected];user=phone> Call ended
16:52:56.869 Calling c7 "Mark Skrodzki"<sip:[email protected];user=phone> <sip:[email protected];user=phone> Send INVITE to [#8001 @D-Link DIV-140]
16:52:56.853 Routed c7 "Mark Skrodzki"<sip:[email protected];user=phone> <sip:[email protected];user=phone> From: Ext:3001; To: [#8001 @D-Link DIV-140]
16:52:56.853 CallConf::findDestination: Found destination [#8001 @D-Link DIV-140] for caller Ext:3001
16:52:56.838 Registrar::checkAor: Registrar resolved sip:[email protected] as <sip:[email protected]:5060;user=phone>
16:52:56.838 Incoming c7 "Mark Skrodzki"<sip:[email protected];user=phone> <sip:[email protected];user=phone> Incoming call from 3001
16:52:56.838 AuthMgr:nAuthSuccess: Extension "Mark Skrodzki"<sip:[email protected];user=phone>;tag=d04ed9d27a7f74ab has been registered successfully

Can anyone offer some help on this???

 

[fischershaw]

That means you actually got the DIV-140 to register? I can't even get it that far. What parameters on each end did you use, if you don't mind me asking. I am unable to get any VOIP to be registered at all with 3cx, and no answers either.

 

[skrodzkim]

I had to give the external line the same internal number as is listed as the line number on the DIV-140.. (this is on the 3CX system). Not sure why it works that way, but it does. I can except calls but cannot make outgoing.

Good Luck!!

 

[fischershaw]

Well OK, that worked. Of course it crashed the "3CX PhoneSystem" service, and all the 3CX services had to be restarted before registration would occur.

This implies a very specific bug for 3CX to fix: Registration is refused unless the "External Number" field and "Internal Number" fields are the same.

Also, 3cx does not appear to do anything until the services are restarted. The log shows that changes were made, but nothing happens.

Thirdly, the "3CX PhoneSystem" service does not want to shut down after changing the internal number fields. It hangs when stopping the service and must be killed.

 

[N_G]

D-link

Actually this is a bug in the D-link itself, not 3CX phone system. Sometimes lines will appear as not registered however the device will still be usable, one can still make outbound and inbound calls. (providing the number is different)

We assume this will be addressed in a future firmware upgrade of D-link

 

[fischershaw]

Could you provide more specifics on the D-Link bug so that I might harass them about it? What I see is:

D-Link sends a register
3CX responds with "needs a password," and I presume its public key
D-Link replies with another register with the encoded password
3CX responds again with "needs a password" and it just repeats from there

When the internal and external fields are the same, 3CX does not complain after D-Link responds. I did not compare the responses in detail yet. True, D-Link registers the line about 5 more times, and it does not support the Register message itself, so 3CX can't do the registering.

 

[N_G]

Can you let us know what firmware you have installed? Then we can check if we have the same/latest first...

 

[fischershaw]

Software Version 1.00 b2
Boot Code Verson RDB 1.92
DSP Version 02060801
Hardware Version A1
Kernel Version MVL 3.0

 

[fischershaw]

When the DIV-140 boots, it begins to plaster 3CX with registration requests. At first, 3CX responds with the 407 error, complaining of Proxy Authentication missing. The DIV-140 provides such authentication on subsequent messages. It receives no response from 3CX (no 200 OK or 407 error). The DIV-140 sends the same response 4 more times, with no reply from 3CX. It eventually sends a register message with no authentication parameter, and receives another 407 error reply. The rest of the lines attempt to register in somewhat the same pattern. None ever receive a 200 OK response. The 3CX log shows that the lines were registered. After awhile, 3CX stops responding altogether to the register request messages from the DIV-140.

I would bet that the DIV-140 is refusing a connection because it was never told by 3CX that the registration succeeded. Just a guess of course, as I have not got that far yet.

 

[Henrik]

I can also not make outgoing calls.

My 3CX gateway config screen has the following for each PSTN:

External Number: 001
Internal Numer: 001
Allow Outbound: yes
Answer Incoming: yes
Answer after: 0
ID: 001
Password: 'password'
Connect to Ring Group: 110
Connect to Ring Group: 110

The DIV-140 configs are as follows:

VOIP Config:
Primary server address: IP of 3CX system
Secondary server address: IP of 3CX system

Port Configuration:
Phone Number: 001
Display Name: Port 1
Authentication ID: 001
Password: 'password'

Incoming calls on the DIV-140 forward to the 3CX ok.
Outbound is a problem and not sure where to look to troubleshoot.

 

[Sione]

Did any one get this working yet?

Has anyone been able to get the calls going out the DIV-140 yet? I been trying to get D-Link help on this, but they just keep playing stupid with me like "Sorry Sir, my computers are down" or "I have no record of your case number" so every call I make to them is like starting all over agian.

I am wondering if there is a special header that needs to be add on the out going call for the DIV-140, just need someone to privide a sniffer capture if possable of the DVX-1000 making a call to the DIV-140 and see if they using some kinda of added numbers or names.

 

[archie]

Latest release has greatly improved registration and authorization subsystems. Please, check if it still has the problem to accept registration from DIV-140. If it does, try to remove password from line settings in 3CX Administrative console, and try it.

 

[AndrewRTS]

Did anyone ever have luck getting the DIV-140 to work?

Just looking at ideas to replace the staticy Grandstream...

 

[GlennS]

DIV-140 Outbound calls

Has anyone been able to get outbound calls working withe the Dlink DIV-140, if so can you provide the configuration.

 

[GlennS]

Okay alittle more background, the Div-140 is registered with 3CX, I can make incoming call's with out a problem, when trying to make outbound calls I either get a 404 not found or 480 Temporaily Unvailable depending on the number I call, I see in the SIP traces 3CX sends the invite to the gateway then the gateway returns a 404, I've tried every configuration and routing setup including adding ACR's and entries in the System and Port Phone books with no luck, would be a great product if Outbound calls worked, right now it's a 300 dollar paper weight. I'm running the following firmware: 1.00 b2
Boot code Version RDB 1.92
DSP Version 02060801
Hardware Version A1
Kernel Version MVL 3.0
Serial Number 01DIV001-000001
System Name DIV
I work with and troubleshoot IMS/SIP gateways everyday at work and can't believe this is rocket science to get this working, at this point it appears to be a bug in the 3CX software or DIV-140 firmware. Comments anyone.... Including 3CX support.

 

[Denny]

mines shows registered on 3CX, but no incoming or outgoing. What steps do i need to take just to get incoming working?

my settings:
System Config/Call
Route all calls to Voip server enabled

VoIP Config: Primary Address: 3CX server
Secondary address: 3CX server

Port Config:
port #1
phone # 10006
Authentication: 10006
Password: password

port #2
phone # 10007
Authentication: 10007
Password: password


Any other settings i have to do to make it work?

Thanks!

 

[Denny]

anyone? just need incoming working.

Thanks!