Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vPBX can not do external/internal calls #2728

Open
1 of 6 tasks
gmoreno90 opened this issue Aug 13, 2024 · 6 comments
Open
1 of 6 tasks

vPBX can not do external/internal calls #2728

gmoreno90 opened this issue Aug 13, 2024 · 6 comments
Assignees
Labels
asterisk +bug Bug * halliday * IvozProvider 3.x Halliday Release *tempest* IvozProvider 4.x Tempest Release

Comments

@gmoreno90
Copy link

gmoreno90 commented Aug 13, 2024

Description

I'm trying to create a vPbx Client and this client cal recieve call but not sent (internal or external)
We configured:

  • 2 Users (with the correct setup of extension and terminal)
  • 2 Terminals (both registered OK)
  • 2 Extensions (1001 and 1002)
  • 1 DID (inbound and outbond)
  • 1 Hung Groups (We use to recieve calls and thats works)

When try to call between 1001 to 1002 return 603 Decline
searching the asterisk debug we can see the following error
> [2dec43c3] Executing [1002@trunks:1] NoOp("PJSIP/proxytrunks-0000001c", "Incoming external call from "" <gonzalo> to 1002") in new stack > [2dec43c3] Executing [1002@trunks:2] AGI("PJSIP/proxytrunks-0000001c", "agi://127.0.0.1:4573/fastagi-runner.php?command=Dialplan/Trunks") in new stack > [2dec43c3] [Kernel.php:60 ] AGI Error ("PJSIP/proxytrunks-0000001c", "DDI 1002 not found in database.") -- <PJSIP/proxytrunks-0000001c>AGI Script agi://127.0.0.1:4573/fastagi-runner.php?command=Dialplan/Trunks completed, returning 0 -- Auto fallthrough, channel 'PJSIP/proxytrunks-0000001c' status is 'UNKNOWN'

How we can configure a vpbx on that version? or is samething missing on configuration side?

Thanks


  • IvozProvider version: 4.04.0.520240430.1111~34aa327+tempest

  • Related sections:

    • SIP & Telephony
    • vPBX Functionalities
    • Billing & Invoicing
    • Web Interface
    • API
    • Other

Troubleshooting

Create the following data on vpbx client

  • 2 Users (with the correct setup of extension and terminal)
  • 2 Terminals (both registered OK)
  • 2 Extensions (1001 and 1002)
  • 1 DID (inbound and outbond)
  • 1 Hung Groups (We use to recieve calls and thats works)

Additional Information

N/A

@gmoreno90 gmoreno90 changed the title vPBX can not generate external/internal calls vPBX can not do external/internal calls Aug 13, 2024
@gmoreno90
Copy link
Author

Hello!
I make the same test using the stable version and have the same result.

image

IvozProvider version: 3.43.4.120240212.929~ee6564e+halliday

That test was made with the Demo Brand and vpbx demo client

@gmoreno90
Copy link
Author

Hello!
I make the same on 4.1 version and have the same result.

image

IvozProvider version: 4.14.1.020240805.1214~83ffdec+tempest
That test was made with the Demo Brand and vpbx demo client

@Kaian
Copy link
Member

Kaian commented Sep 13, 2024

Hi @gmoreno90

Are you using different IP address for Trunks and Users kamailio proxies?
It looks like asterisk is identifing your user calls as trunks (external) calls

Also, I would also try updating to 4.2.0 version (It will be released next week) that have some fixed on how proxies are identified by asterisk on standalone installations.

Best regards

@Kaian Kaian self-assigned this Sep 13, 2024
@Kaian Kaian added +bug Bug * halliday * IvozProvider 3.x Halliday Release *tempest* IvozProvider 4.x Tempest Release asterisk labels Sep 13, 2024
@gmoreno90
Copy link
Author

Hi @Kaian
I'm using the same IP for both proxies.
I intall a the new version, and now the proxytrunks not start with the following error. need to open a new ticket? with that issue?

root@ivoz42:/etc/apt/sources.list.d# systemctl -l status [email protected] --no-pager
× [email protected] - Kamailio - the Open Source SIP Server
Loaded: loaded (/lib/systemd/system/[email protected]; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2024-09-26 14:49:16 CEST; 6min ago
CPU: 137ms

Sep 26 14:49:16 ivoz42 kamailio[25997]: tcp: trunks.ivozprovider.local [46.183.118.130]:8002
Sep 26 14:49:16 ivoz42 kamailio[25997]: tcp: trunks.ivozprovider.local [46.183.118.130]:8001
Sep 26 14:49:16 ivoz42 kamailio[25997]: tls: trunks.ivozprovider.local [46.183.118.130]:5061
Sep 26 14:49:16 ivoz42 kamailio[25997]: Aliases:
Sep 26 14:49:16 ivoz42 /usr/sbin/kamailio[25999]: WARNING: db_mysql [km_my_con.c:187]: db_mysql_new_connection(): opt_ssl_ca option not supported by mysql version (value (null)) - ignoring
Sep 26 14:49:16 ivoz42 /usr/sbin/kamailio[25999]: ERROR: dmq [dmq.c:241]: mod_init(): server_uri is not a socket the proxy is listening on
Sep 26 14:49:16 ivoz42 /usr/sbin/kamailio[25999]: ERROR: [core/sr_module.c:1039]: init_mod(): Error while initializing module dmq (/usr/lib/x86_64-linux-gnu/kamailio/modules/dmq.so)
Sep 26 14:49:16 ivoz42 systemd[1]: [email protected]: Control process exited, code=exited, status=255/EXCEPTION
Sep 26 14:49:16 ivoz42 systemd[1]: [email protected]: Failed with result 'exit-code'.
Sep 26 14:49:16 ivoz42 systemd[1]: Failed to start [email protected] - Kamailio - the Open Source SIP Server.

Best Regards

@Kaian
Copy link
Member

Kaian commented Oct 16, 2024

Hi,

Sorry for the late response, I was on holidays.

Can you provide the contents of /etc/kamailio/proxytrunks/listeners.cfg and /etc/kamailio/proxytrunks/ports.cfg ?

Best Regards,

@Kaian
Copy link
Member

Kaian commented Nov 12, 2024

Hi,

Could you check if this can be reproduced in 4.2.0?

Best regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
asterisk +bug Bug * halliday * IvozProvider 3.x Halliday Release *tempest* IvozProvider 4.x Tempest Release
Development

No branches or pull requests

2 participants