SIP TRUNK SETTING ISSUE

Status
Not open for further replies.

speedinet

Free User
Joined
Aug 25, 2022
Messages
5
Reaction score
0
IM TRY TO CONNECT VOXBEAM AS MY OUTBOUND I HAVE TRY SETTING FROM THE FORUMS , WHEN DIAL I GET THE MSG IN LOGS




05/18/2023 9:56:15 PM - Call to T:Line:10001>>923182991538@[Dev:sip:[email protected]] from L:71.1[Extn:100] failed, cause: Cause: 403 Forbidden/INVITE from 108.59.2.133:5060
05/18/2023 9:56:15 PM - [CM503003]: Call(C:71): Call to <sip:[email protected]:0> has failed; Cause: 403 Forbidden/INVITE from 108.59.2.133:5060
05/18/2023 9:55:58 PM - Call to T:Line:10001>>923182991538@[Dev:sip:[email protected]] from L:70.1[Extn:100] failed, cause: Cause: 403 Forbidden/INVITE from 108.59.2.133:5060
05/18/2023 9:55:58 PM - [CM503003]: Call(C:70): Call to <sip:[email protected]:0> has failed; Cause: 403 Forbidden/INVITE from 108.59.2.133:5060
05/18/2023 9:53:52 PM - Call to T:Line:10001>>923182991538@[Dev:sip:[email protected]] from L:69.1[Extn:100] failed, cause: Cause: 403 Forbidden/INVITE from 108.59.2.133:5060
05/18/2023 9:53:52 PM - [CM503003]: Call(C:69): Call to <sip:[email protected]:0> has failed; Cause: 403 Forbidden/INVITE from 108.59.2.133:5060
05/18/2023 9:51:35 PM - Call to T:Line:10001>>923182991538@[Dev:sip:[email protected]] from L:68.1[Extn:100] failed, cause: Cause: 403 Forbidden/INVITE from 108.59.2.133:5060
05/18/2023 9:51:35 PM - [CM503003]: Call(C:68): Call to <sip:[email protected]:0> has failed; Cause: 403 Forbidden/INVITE from 108.59.2.133:5060


UPON CONTACTING THE PROVIDER I GOT THIS RESPONSE PLEASE ADVISE WHAT IAM MISSING





""
Dear Customer,

Our requirements are that you provide a Genuine number in both your From: & your P-Asserted-Identity: headers in +E164 format, currently you are sending your From: header as sip:[email protected] this might be a National format in your country but it is unacceptable for us. You are also NOT providing any P-Asserted-Identity: header which again is unacceptable.

Please fix both of these errors before attempting your calls again.""



3CX1.JPG3CX2.JPG
 

Attachments

  • 1684429126699.png
    1684429126699.png
    47.6 KB · Views: 5
I believe the reply from your provider is pretty clear. You need to dial your numbers in the +E164 number format.
 
I believe the reply from your provider is pretty clear. You need to dial your numbers in the +E164 number format.
i did that aswell i belive i miss something in outbound pattern
 
What does the Activity Log now show, after you made the changes?
 
If the number being sent still looks the same as the log you posted, then you have not yet corrected the problem. Numbers should begin with a +, then the country code, as per the E164 format.

Are you making use of the E164 settings in 3CX, or simply the outbound rules?
 
If the number being sent still looks the same as the log you posted, then you have not yet corrected the problem. Numbers should begin with a +, then the country code, as per the E164 format.

Are you making use of the E164 settings in 3CX, or simply the outbound rules?


these are my setting wat iam i missing






1684942946456.png


1684942981579.png

1684943010906.png


1684943038159.png
 
It looks as if you are still sending a leading 00 rather than +. The E164 settings will normally convert a + to the required long distance prefix. If E164 is enabled, then you may have to disable. You can modify your outbound rules to strip the 00 and replace with a +, it will all depend on how you dial the digits from a set/device.
 
Last edited:
Status
Not open for further replies.

Forum statistics

Threads
111,973
Messages
590,079
Members
164,898
Latest member
grahamaskew