Need help about SIP TRUNKS

[Giorgi Kambarashvili]

hello, i have a really big problem and i need your help bad. here is the situation.

i have a 1 SIP provider and 2 DID numbers from that provider. i want to create 2 separate queue and ring groups, so i did, i went to sip trunks and just created 2 separate SIP TRUNKS 1)2155551 and 2) 155005, i am telling to 2155551 to go for the queue extension created earlier for example 8004 where i have put agents ext 1001-1002-1003 and so on. for the second trunk i have created queue 8005 where i have put ext - 1010-1011-1012 and so on, so when i am calling to DID 2155551 or 2155005 both goes to 1 QUEUE, i have tried many things but run out of ideas what can i do to separate this 2 trunks, i have tried inbound routes with many different configuration but same happens, i also have read a thread about it and tried
What you can try, is to enable the option "Use both "Source Identification" rules and "Caller Number/Name" field mappings" in the Inbound rules as shown below.

useless, when i am trying this options 1 trunk works but second tells busy tone, but when i am putting that other trunk to 3CX softphone client it works....

HELP PLEASE !

update: 2155551 works fine now see attach 1 for details and parameters
2115005 can not make it work.... insta drops call. tried many configurations but still out of ideas...

 

[AWS2P]

i have 2 separate DIDS with authentification and i have created 2 sip trunks, with different numbers and different authentication details.

when you do this are your trunks registred green or not, if not you need to ask support to your sip provider, and in activity log you normally can see registration trying so you should have some infos on what happens

 

[Giorgi Kambarashvili]

update# deleted inbound rule for *155005 , calling to 155551 but same, ext directed because in the sip trunk parameters for 155005 i wrote destination to 1020, so same happens somehow 155551 calls goes now to 1020, but in the parameters of the sip trunk 155551 is call center 8080, also inbound route 8080

 

[AWS2P]

so if you have same credentials, same host, same provider are you sure you have not just only one trunk ?

and 2 DIDs

 

[Giorgi Kambarashvili]

so if you have same credentials, same host, same provider are you sure you have just only one trunk ?

and 2 DIDs

i do not know, they sent me such parameters

2155005
100
username: 999993489
password: **
sip.Server: sip.intelphone.ge ip 92.241.68.3


2155551
101
username: 999993490
password: *
sip Server: sip.intelphone.ge IP 92.241.68.3

 

[AWS2P]

is your firewall checker green?

First of all , your trunks need to be registred green, if not you need support from your provider .
If registration fails of course inbound rules are no use for now.

 

[Giorgi Kambarashvili]

when i am adding sip.intelphone.ge it is not working, when i am putting IP there, it is working, only 1 trunk as i have mentioned.

 

[Giorgi Kambarashvili]

is your firewall checker green?

First of all , your trunks need to be registred green, if not you need support from your provider .
If registration fails of course inbound rules are no use for now.

no firewall is off atm.

 

[AWS2P]

ok so according to what you post , you have two sip accounts so , if your pbx is not in use try to scratch trunks and Set once at a time each trunk sip and check if they are green registred to provider.

If this is not working you need provider support.

 

[AWS2P]

I spoke firewall in console

 

[Giorgi Kambarashvili]

ok so according to what you post , you have two sip accounts so , if your pbx is not in use try to scratch trunks and Set once at a time each trunk sip and check if they are green registred to provider.

If this is not working you need provider support.

i have deleted both trunks, so i have added 1 155551 (callcenter trunk) it is red but it is working. provider tech support are bad people, i have called recently to 1 of them and it was like a hell to talk with him because he told me that they have created simple trunks and gave parameters to us, what else they can do....... useless to talk with them, i have explained situation that their server sends me authentification failed, but they said how it is working then? how it is working on the sipphone if it's their fault....

give me arguments please to ARGUE with them...

 

[Giorgi Kambarashvili]

only this 2 check failed by firewall

 

[AWS2P]

try to do this in same order in picture, see registration date and time change or not


From your FW picture , you have SIP ALG enabled in your router, you need to disable this surely reason why doing a mess in your 3CX

FW checker need to pass with no error, and SIP ALG is very important not to have enabled.

Sorry but i've to go, hope you can fix this, have a good day

 

[Giorgi Kambarashvili]

no progress at all.. unfortunately i am not able to fix this issue. no ideas at all.

 

[AWS2P]

What router brand and model do you use ?
Normally you have a GUI access on router, you need to have credentials of course, after your search for SIP ALG options to disable. When done check once again FW in 3CX, it should pass with no errors.
After try to restart SIP trunk creation and check registration (green only)
Do the same for second one , if all is good with registration, then next step inbound rules and finally do call tests

 

[leejor]

Are each of the trunks from a different provider? One of the attachment in your earlier posts seem to show both, not registered (red), and possibly from the same provider (same IP).

now i changed the thing for the 1 trunk 155005 and directed to the ext not to the group. 1020 ext
when i am calling now to the number 155551 - which must be on call center... it directs to 1020 wtf?

If you are now getting calls, on both numbers, then you can use the Activity Log to see why they are going where they do. It will show which trunk the call comes in on, the full DID number (if sent), and the destination.

 

[YiannisH_3CX]

Hello @Giorgi Kambarashvili

So, you have 2 trunks with 1 number each but the same IP to which the trunks register to.

Since you have 2 trunks with the same IP you need to disable the call source identification from the Inbound parameters for both trunks. If you have call source identification enabled with the wrong settings you might end up breaking the trunks.

Check the Activity log of the PBX and verify the number format the provider is using to present the call to you. Check the Invite message from the provider and identify the format used in the to display your own DID. Then add your DIDs using the same format.

Check if this works and if the trunks register and show as green in the Sip trunks section. If the trunks register but calls still fail you will need to enable the call source identification options and adjust them based on your providers settings but since the provider is not tested we do not know the settings you need to use.
If the trunks do not register and you will still get an error you will need to contact your provider and ask them why they are rejecting the registration.