Retransmitting #1 (NAT) to

When I am trying to call someone, facing this error. i am using Twilio Sip to fix this error?

Sending to (NAT)
Sending to (NAT)
Using INVITE request as basis request - 7IOAg3AH4ZPcXOAM2ee8dQ…
Found peer ‘7001’ for ‘7001’ from
Got SDP version 1 and unique parts [- 1638992831 IN IP4]
Found RTP audio format 105
Found RTP audio format 18
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format opus for ID 105
Found audio description format G729 for ID 18
Found audio description format PCMA for ID 8
Found audio description format PCMU for ID 0
Found audio description format telephone-event for ID 101
Capabilities: us - (ulaw), peer - audio=(ulaw|alaw|g729|opus)/video=(nothing)/text=(nothing), combined - (ulaw)
Non-codec capabilities (dtmf): us - 0x1 (telephone-event|), peer - 0x1 (telephone-event|), combined - 0x1 (telephone-event|)
Peer audio RTP is at port
Looking for 4692512437 in from-phones (domain
sip_route_dump: route/path hop: sip:7001@

<— Transmitting (NAT) to —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP;branch=z9hG4bK-524287-1—d80fb07a67d8aa5d;received=;rport=5060
From: <sip:7001@192.168.0. 101>;tag=5861e577
To: <sip:4692512437@192.168.0. 101>
Call-ID: 7IOAg3AH4ZPcXOAM2ee8dQ…
Server: Asterisk PBX 19.0.0
Supported: replaces
Contact: <sip:4692512437@192.168.1. 101:5060>
Content-Length: 0

what should I do now?

What error? There is no explicit error in the logs.

There are malformed SIP URIs (spurious space in IP address) in the To and From headers, although one would expect those to be what was received, except that your log is truncated at the start and doesn’t include the original ones. Ther eis also the same malformation in the Contact header, which does originate locally.

The From and To errors don’t seem to be in the screen shot, and the Contact header isn’t there. I suspect they are the result of re-keying. Please enable the full log and copy the text directly from it, rather than using screenshots or re-keying.

Considering the subject, if you just have a #1, that just means the network is overloaded, or the peer is sluggish. If you have multiple ones, and a final failure, that probably means wrong external addresses, or NAT or firewall issues.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.