Solved Source Identification issues

[Quest4Voice]

Good day experts

I seem not to understand what i should configure at this part. I keep getting error 407 when a call comes in from the service provider.
is i wish i could share what the provider has given me as parameters I using peer IP addresses.

When i do debug am able to see my call coming in and dropping.

I hope someone can assist me with a practical example un fortunately this below is a bit confusing.

https://www.3cx.com/docs/sip-trunk-inbound-calls/

I dont know what i can use.

thanks in advance

Quest!

 

[cobaltit]

And this is why you use a supported provider.

If you don't have multiple trunks you shouldn't really need to touch anything there. All calls should follow the default trunk destination. Once you confirm that is working then you can start adding additional DIDs and if those aren't matching you can work on those settings.

 

[YiannisH_3CX]

Hi @Quest4Voice

Since you do not know how to configure the Source Identification section then your best bet is to disable it. The PBX will then try to match the call with your trunk only via DID.
Make sure that all your DIDs are added in the DID section of the trunk and make sure that you have added them in the correct format (the one the provider is using).
If you are not sure you could use the "*" wildcard to eliminate any errors.
For example you have a DID +44123456789.
Your provider could be sending the DID as +44123456789 or 44123456789 or 0123456789.
To cover all instances you can add your DID as *123456789.

Also make sure that your DIDs are only present under one trunk.

 

[Quest4Voice]

i will try this and advise to test my trunks there was one that initial installation comes with that i left i will delete and try.

 

[Quest4Voice]

YiannisH_3CX

Hello team i have run my self into the same issue here i have attached screen shots of my configuration for a start we can start from there. However to answer this question.

For example you have a DID +44123456789.
Your provider could be sending the DID as +44123456789 or 44123456789 or 0123456789.
To cover all instances you can add your DID as *123456789

ITSP sends the number "0123456789" without the leading zero."123456789 " thats what i have configured please peruse through the attached document and kindly assist.

Thanks in advabce
Quest

 

[cobaltit]

Ignore the inbound rules for now. Did you disable Source Identification as asked? With Source Identification disabled do calls come in on the default trunk route? Once you can confirm calls come in then we can start looking at routing DIDs.

 

[Quest4Voice]

Ignore the inbound rules for now. Did you disable Source Identification as asked? With Source Identification disabled do calls come in on the default trunk route? Once you can confirm calls come in then we can start looking at routing DIDs.

I will need help on how to do that I attached a screenshot of my configurations on that part. Also I said I have two trunks one trunk is the webmeeting trunk which am failing to delete.
Your help on this will be highly appreciated

Thanks in advance

 

[YiannisH_3CX]

The webmeeting trunk is part of the system and should not be deleted. It is the part that connects the PBX with the webmeeting service and has nothing to do with your issue.
I have sent you a p.m. with some instructions so we can better troubleshoot your issue.

 

[Quest4Voice]

Thanks
YiannisH_3C
for the help calls are able to get in now i dont know how i missed that in my SIP debug analysis with Wireshark.

Problem was as stated the numbers that the ITSP was sending to me where not matching. I was recieving 10 numbers with other extra leading numbers. So i trimed it to what the debug was showing as incoming numbers from the ITSP. When i put in the numbers as the ITSP wanted the issue was resolved.

Thanks

Quest

 

[YiannisH_3CX]

Glad to see the issue has been resolved