Sip Trunk Inbound/Outbound Routing

Status
Not open for further replies.

smokie

Forum User
Joined
Jun 22, 2019
Messages
54
Reaction score
2
Hi and good day,

If someone from South Africa can please assist with this one, I run v16 and I am battling with the Sip trunk, it shows that it is registered but the outbound and inbound calls are still failing, i have contacted my service provider (Wirulink, hopeless) but they are saying that it is not registered. Please advise if more info is needed,
 
First check to see if trunk is seen registred from 3Cx side, Go MC and in dashboard trunks need to be green
11269
11270

try a refresh registration and check register sent and register ok fields

did you create almost one inbound and one outbound rule ?
If no , this can explain why calls are not working.
 
Hi

I have configured both inbound/outbound rules,
 
Check the activity log, to see any activity and errors when making incoming / outgoing calls.

You may have to increase the logging - Activity Log - Settings (will be set to low)
 
Oki doki, will do and get back soonest
 
Nope, hoisted locally, thanks will get back to you
 
Hello

I am in need of help please, I have setup a test environment and I am running v16 on a windows10 box.I am using a Sip Registration account, Problem that I am experiencing is that inbound calls are working but outbound it fails with a 603 Declined, I am not sure if I am sending them the wrong details in the sdp header or something, i have attached wireshark trace, please advise as my Sip knowledge is not good at all, Thanks
 

Attachments

do you use outbound caller id or not ?
and maybe you are send calls in wrong format
 
Are you getting the 603 Declined response on all numbers called?

read the description of what that message means.

https://en.wikipedia.org/wiki/List_of_SIP_response_codes

Are you sure that you are sending numbers in the correct format. Check with your provider if you are not certain. They should also be able to give you more information on the declined message.
 
@leejor

Hi, i'm not sure at all if this thread is always useful because Smokie said in another one his W10 got BSOD and he switched to Debian from scratch.
 
@smokie

  • If it's IP based it always appears registered

  • If it's registration based, the provider should be able to see the registration (unless you are registering elsewhere and are not aware of it)

The 603 declined at the least means that you reached some other side and they declined the call.

Your screenshot of the capture seems to show that phone with ip .109 reached PBX with IP .122 which attempted to make a call to provider/gateway 169.239.8.76, are these assumptions correct?
 
Hi
JohnS_3CX
Thanks for the response, i received feedback from my Sip Provider who stated that their side is sending the 603 declined because the "cid is showing as 000 and not the number 27xxxxxxxxx, where do i change the CID so that i can make that change and not blowing up our server!
 
Are you getting the 603 Declined response on all numbers called?

read the description of what that message means.

https://en.wikipedia.org/wiki/List_of_SIP_response_codes

Are you sure that you are sending numbers in the correct format. Check with your provider if you are not certain. They should also be able to give you more information on the declined message.

Hi
Thanks for the response i really appreciate it,
I have spoken to my provider and they are stating that i am sending the wrong CID,where can i configure this to correct it please
 
You will find this under your trunk settings, check that you added your DID correctly and to confirm what you send check your activity log and filter by call number to see what your invite contains if you need to experiment a bit until you get your number formatting right.

https://www.3cx.com/docs/cid-reformatting/
 
If you have added DID information in the extension settings (Caller ID to be displayed on outside calls), then this may (will probably) override what you have set against the trunk itself. There are trunk options that affect this as well.

If you continue to have issues, ask you provider what caller ID is that they are seeing. Is it the same on every call? (if it is, then it is most likely a trunk setting) What is the number? What number(s) do they want to see? (are you allowed to send) Given that information , will help you narrow down where to make the change.
 
If you have added DID information in the extension settings (Caller ID to be displayed on outside calls), then this may (will probably) override what you have set against the trunk itself. There are trunk options that affect this as well.

If you continue to have issues, ask you provider what caller ID is that they are seeing. Is it the same on every call? (if it is, then it is most likely a trunk setting) What is the number? What number(s) do they want to see? (are you allowed to send) Given that information , will help you narrow down where to make the change.

A couple posts up he states that the provider says they are seeing 000 which is probably the extension number as I doubt he added 000 as the trunk or extension CID.

@smokie

This is why you should use a supported provider as all these settings are already configured for you. You'll want to put the 27xxxx in the trunk CID field and then test. If the provider is still seeing 000 then you'll need to ask them which field they want the CID in and then make the appropriate change in the outbound settings of the trunk configuration.
 
Sorry, missed the 000. If you are attempting calls from various extensions, then 000 is probably not a DID number set against one of them, but a datafill in the trunk settings.
 
Status
Not open for further replies.

Forum statistics

Threads
111,931
Messages
589,804
Members
164,803
Latest member
fcentral