[netswork]

Pasting a wireshark capture of the call from the 3cx server will help see whats going on.

[startelecom]

How is this?



Session Initiation Protocol
Request-Line: INVITE sip:16475551234@204.X.Y.Z:5060 SIP/2.0
Method: INVITE
Request-URI: sip:16475551234@204.X.Y.Z:5060
Request-URI User Part: 16475551234
Request-URI Host Part: 204.X.Y.Z
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP 192.168.2.60:5095;branch=z9hG4bK-d8754z-682b116ee9082e0c-1---d8754z-;rport
Transport: UDP
Sent-by Address: 192.168.2.60
Sent-by port: 5095
Branch: z9hG4bK-d8754z-682b116ee9082e0c-1---d8754z-
RPort: rport
Max-Forwards: 70
Contact: <sip:default@192.168.2.60:5095>
Contact-URI: sip:default@192.168.2.60:5095
Contactt-URI User Part: default
Contact-URI Host Part: 192.168.2.60
Contact-URI Host Port: 5095
To: <sip:16475551234@204.X.Y.Z:5060>
SIP to address: sip:16475551234@204.X.Y.Z:5060
SIP to address User Part: 16475551234
SIP to address Host Part: 204.X.Y.Z
SIP to address Host Port: 5060
From: "8778008000"<sip:default@204.X.Y.Z:5060>;tag=8c34832e
SIP Display info: "8778008000"
SIP from address: sip:default@204.X.Y.Z:5060
SIP from address User Part: default
SIP from address Host Part: 204.X.Y.Z
SIP from address Host Port: 5060
SIP tag: 8c34832e
Call-ID: YWNlM2I0M2VmMzU4ZDNiMTdlZjExMGZhOGEyMGQxZDM.
CSeq: 1 INVITE
Sequence Number: 1
Method: INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Content-Type: application/sdp
Supported: replaces
User-Agent: 3CXPhoneSystem 10.0.22539.0
Content-Length: 276
Remote-Party-ID: "8778008000"<sip:8778008000@204.X.Y.Z:5060>;party=calling
[Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
[Message: Unrecognised SIP header (Remote-Party-ID)]
[Severity level: Note]
[Group: Undecoded]
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): 3cxPS 434278236160 38990249985 IN IP4 192.168.2.60
Owner Username: 3cxPS
Session ID: 434278236160
Session Version: 38990249985
Owner Network Type: IN
Owner Address Type: IP4
Owner Address: 192.168.2.60
Session Name (s): 3cxPS Audio call
Connection Information (c): IN IP4 192.168.2.60
Connection Network Type: IN
Connection Address Type: IP4
Connection Address: 192.168.2.60
Time Description, active time (t): 0 0
Session Start Time: 0
Session Stop Time: 0
Media Description, name and address (m): audio 7010 RTP/AVP 0 8 3 101
Media Type: audio
Media Port: 7010
Media Protocol: RTP/AVP
Media Format: ITU-T G.711 PCMU
Media Format: ITU-T G.711 PCMA
Media Format: GSM 06.10
Media Format: DynamicRTP-Type-101
Connection Information (c): IN IP4 192.168.2.60
Connection Network Type: IN
Connection Address Type: IP4
Connection Address: 192.168.2.60
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute Fieldname: rtpmap
Media Format: 0
MIME Type: PCMU
Sample Rate: 8000
Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute Fieldname: rtpmap
Media Format: 8
MIME Type: PCMA
Sample Rate: 8000
Media Attribute (a): rtpmap:3 GSM/8000
Media Attribute Fieldname: rtpmap
Media Format: 3
MIME Type: GSM
Sample Rate: 8000
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute Fieldname: rtpmap
Media Format: 101
MIME Type: telephone-event
Sample Rate: 8000
Media Attribute (a): sendrecv

[startelecom]

Hi Folks,

Any feedback based on the trace?

[netswork]

are you still using stun?

[startelecom]

I have tried both using STUN and by forcing the public IP... it doesn't seem to make a difference.

[startelecom]

Any further thoughts/ideas?

[startelecom]

bump?

[danhriscanu]

Can you upload here a pcap file between your server and the SIP provider? Its easy to follow than a plain text. Also check your settings of your trunk to this Voip provider. Have you followed a 3cx template or you created a generic one? What do you have at outbound proxy?

[startelecom]

Dan,

Unfortunately that's not possible. I don't feel comfortable posting PCAPs because they include information that I do not want to post like IPs, phone numbers, etc.

I have checked the pcap from the carrier end and the private IPs is included in the contact field and that's where the problem lies as I've indicated from the beginning. The firewall does not do any packet inspection, it's the 3CX box that is incorrectly including the private IP in the contact field, regardless of settings.

Has anyone from 3CX tried to replicate this? It seems like I am doing all the work

If you want me to follow certain steps to try to make it to work, I'd be more than happy to. I used the generic SIP trunk profile. Outbound proxy is blank at the moment.

[danhriscanu]

Unfortunately I could not replicate your issue but in my opinion its a configuration of sip trunk issue and not a STUN one. In INVITE coming from your provider you should see Contact-URI [your ID]@[IP of provider] instead of "default@192.168.2.60:5095".
Try to remake your Voip Provider and in "SIP server hostname or IP" put the IP address of your provider and the port that he specified to you. Outbound proxy hostname and port should be according to your provide specification. Some of them prefer leave it blank and on some of them will be the same as SIP server address.
In account details fill in Authentication ID and External number as told by your SIP provider. On most of them these 2 parameters are the same. Don't check 3 Way Authentication ID!
It should be as simple as that.
Good luck!

[startelecom]

Dan,

I followed the exact steps you outlined below. I re-created the provider, input their IP in the "SIP Server and hostname or IP" and left the proxy fields blank.

I put dummy data in the external number & authentication ID and left password blank (since the provider doesn't require registration).

Tried to make the call again, and I still see the internal IP in the Contact field. Again, I think this is the root of the problem. I need to be able to populate the external IP in the Contact field and 3CX is not allowing me to do this for some reason.

[SY]

4 pieces of information should be provided:
1.output of "ipconfig /all" command
2.output of "route print" command
3. description of network topology
4. 3CXPhoneSystem.log and 3CXPhoneSystem.trace.log
a) set debug level of the log
b) restart 3CX PhoneSystem service.
c) wait for 1 minute. Make problematic call.
d) collect logs

If this information cannot be provided then nobody will be able to answer your question

[startelecom]

Stepan, I've PMed you with requested information.