search

olivluca / danube-voip

This is a sip client using the 2 FXS ports available on routers based on the Infineon Danube and running openwrt.
16 stars 10 forks source link

Precompiled binaries for lantiq xrx200 #13

Closed Wapitiii closed 3 years ago

Wapitiii commented 3 years ago

Would it be possible to compile it for MIPS 34Kc or could someone provide precompiled binaries?

Thanks

olivluca commented 3 years ago

You can download a precompiled sdk for your platform (which one, btw?) and follow the instructions here: https://openwrt.org/docs/guide-developer/using_the_sdk

Wapitiii commented 3 years ago

Alright, i will do that, i want to try it on my Easybox 904 xDSL i don't know what platform it is (i think as it says in the wiki "Lantiq XWAY™ VRX288") im also not sure if it even would work on my hardware.

olivluca commented 3 years ago

Well, looking at the makefile for ltq-tapi I see that it should work with the xrx200. Good luck.

Wapitiii commented 3 years ago

So, i've got it compiled with the precompiled sdk for my platform, the only thing that worked to install was sofia-sip the others didn't work. Any idea how i could fix it? Also when compiling with the latest precompied sdk i've got the same error as #12 , i just used an older version and it worked. image

olivluca commented 3 years ago

I only found this message on the forum, unfortunately no solution.

Wapitiii commented 3 years ago

I found the error, it wanted to get a package, and i wasn't connected to the internet 🤦🏻‍♂️. Now it installs.

image

Also here are the packages for the lantiq xrx200 (if anyone needs them): danube-voip-lantiq-xrx200-packages.zip

Thanks for guiding me to the wiki with the sdk stuff.

olivluca commented 3 years ago

Apart from compiling and installing, does it work?

Wapitiii commented 3 years ago

Nope, doesn't want to connect to the voip provider and the fxs port also doesn't work.

On my Easybox 803A it works as expected (it tries to connect). On the Easybox 904 not, maybe because it uses 1 core for VoIP. But i am not an expert on it. But VoIP should work with Asterisk (which i wanted to avoid)

olivluca commented 3 years ago

Maybe you need a different firmware/parameters/device name , i.e. the defines in ab_basic.c 

#define AB_DRIVER_DEV_NODE "/dev/sgatab"
#define TAPI_AUDIO_DEV_NUM 2
#define TAPI_LL_DEV_FIRMWARE_NAME   "/lib/firmware/danube_firmware.bin" 
#define TAPI_LL_BBD_NAME   "/lib/firmware/danube_bbd_fxs.bin"

(just guessing)

Wapitiii commented 3 years ago

Yeah, seems like i need to set the right .bin files there with the name.

image

Need to figure out which one is the right .bin with trial and error. I'll report back if i got new updates.

Wapitiii commented 3 years ago

Ok, got it working even my telephone detects it now.

olivluca commented 3 years ago

Just for your information, in my router that file (that appears to be missing in yours) comes from kmod-ltq-vmmc

root@voip:~# opkg search /lib/firmware/danube_firmware.bin
kmod-ltq-vmmc - 4.14.171+1.9.0-3

The firmware files used by asterisk apparently are these

olivluca commented 3 years ago

Ok, got it working even my telephone detects it now.

What did you to to make it work?

Wapitiii commented 3 years ago

I've took the already included firmware files called "voice_ar9_firmware.bin" and "vr9_bbd_fxs.bin" and renamed it to "danube_firmware.bin" and "danube_bbd_fxs.bin". (With included i mean they were already in the /lib/firmware/ folder). Now i'll try to connect to my VoIP provider and try to call with it.

olivluca commented 3 years ago

Oh, that saves me the trouble of making the path configurable :sweat_smile: though it will break whenever you upgrade the package providing the firmware (in any case I never saw updates to the firmware).

Wapitiii commented 3 years ago

So, i configured it, and now i have another issue, somehow i can't call anyone and also weird is that "From:" and "To:" has the same telephone number. And it errors out to a "403 Contact User und Anrufernummer verschieden" which is in english "403 Authentication User Name does not match account name". Maybe i misconfigured it? image

Well i was a bit dumb, i thought the "config account 'XXX'" was just some note where i could name it whatever i wanted, seems like i needed to enter in the "XXX" the account username 🤦🏻‍♂️ . Now thankfully it gives a "200 OK"

olivluca commented 3 years ago

No actually the XXX is a descriptive text that isn't used anywhere else, the username is in the "option user"

Wapitiii commented 3 years ago

Huh, thats weird, after changing it to the user name it doesn't give me the 403 anymore.

Before: image

After: image

Wapitiii commented 3 years ago

But still, i want to thank you for this wonderful program, it just made VoIP on OpenWRT much easier for me. I will probably make a video about it when i have the time.

olivluca commented 3 years ago

Huh, thats weird, after changing it to the user name it doesn't give me the 403 anymore.

Well, I can assure it that it's just descriptive, maybe it was a temporary glitch. Some sip providers don't allow more than one simultaneous registration, maybe the other router you were trying hadn't timed out yet.

Wapitiii commented 3 years ago

It could be also that, but i didn't use the other router for hours now, so i could cross that. At least it works now, will try it running for a while. The only issue that i have noticed is that i can't reject a oncoming call.

olivluca commented 3 years ago

The only issue that i have noticed is that i can't reject a oncoming call.

I don't think that's even possible with an analogue phone, I mean, you either pick up or you don't.