cpendl Posted January 23, 2010 Report Share Posted January 23, 2010 When I try to place outgoing calls I get a "SIP Trunk Not Found" error when I check the logs. If I have up and call again (within 2 seconds) the call goes through. Any idea what might keep causing this? Is there a "keep alive" funtion on the trunk that would help with this? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 23, 2010 Report Share Posted January 23, 2010 When I try to place outgoing calls I get a "SIP Trunk Not Found" error when I check the logs. If I have up and call again (within 2 seconds) the call goes through. Any idea what might keep causing this? Is there a "keep alive" funtion on the trunk that would help with this? For outbound calls, the log message probably comes from the call that initiates the call (from the extension). That is of course okay. This message is only interesting for inbound calls from a trunk to the PBX. Quote Link to comment Share on other sites More sharing options...
cpendl Posted January 23, 2010 Author Report Share Posted January 23, 2010 For outbound calls, the log message probably comes from the call that initiates the call (from the extension). That is of course okay. This message is only interesting for inbound calls from a trunk to the PBX. The problem is, I have to make every outgoing call twice to get one to connect. How do I fix? Quote Link to comment Share on other sites More sharing options...
pbx support Posted January 28, 2010 Report Share Posted January 28, 2010 The problem is, I have to make every outgoing call twice to get one to connect. How do I fix? What version of the software are you using? Quote Link to comment Share on other sites More sharing options...
cpendl Posted January 28, 2010 Author Report Share Posted January 28, 2010 What version of the software are you using? Version: 3.4.0.3201 (Darwin) Here is the email i receive about the error. The call between sip:8002752273@10.10.0.9;user=phone and sip:40@10.10.0.9 has been disconnected because no media session was establised (source=10.10.1.90:1024) Here is the log from attempting to make a call where it does not find trunk. [9] 2010/01/28 10:47:46: Resolve 70672: aaaa udp 10.10.1.90 1024 [9] 2010/01/28 10:47:46: Resolve 70672: a udp 10.10.1.90 1024 [9] 2010/01/28 10:47:46: Resolve 70672: udp 10.10.1.90 1024 [9] 2010/01/28 10:47:46: Resolve 70673: aaaa udp 10.10.1.90 1024 [9] 2010/01/28 10:47:46: Resolve 70673: a udp 10.10.1.90 1024 [9] 2010/01/28 10:47:46: Resolve 70673: udp 10.10.1.90 1024 [9] 2010/01/28 10:47:47: Resolve 70674: aaaa udp 10.10.1.90 1024 [9] 2010/01/28 10:47:47: Resolve 70674: a udp 10.10.1.90 1024 [9] 2010/01/28 10:47:47: Resolve 70674: udp 10.10.1.90 1024 [5] 2010/01/28 10:47:50: SIP Rx udp:10.10.1.90:1024: INVITE sip:8002752273@10.10.0.9;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.10.1.90:1024;branch=z9hG4bK-tit99cgtbg9q;rport From: "Chris Pendl" <sip:40@10.10.0.9>;tag=dhytveg316 To: <sip:8002752273@10.10.0.9;user=phone> Call-ID: 3c34d70a133c-l437z7ee50bv CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:40@10.10.1.90:1024;line=68fy0mcb>;reg-id=1 X-Serialnumber: 000413400B70 P-Key-Flags: resolution="31x13", keys="4" User-Agent: snom820/8.2.11 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, from-change Session-Expires: 3600;refresher=uas Min-SE: 90 Content-Type: application/sdp Content-Length: 450 v=0 o=root 1646706789 1646706789 IN IP4 10.10.1.90 s=call c=IN IP4 10.10.1.90 t=0 0 m=audio 49264 RTP/AVP 0 8 9 99 3 18 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:MrIgPoS2Z9P6mumzlBeH59we70t32m94rtIYR48k a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:99 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:18 g729/8000 a=rtpmap:4 g723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv [8] 2010/01/28 10:47:50: Could not find a trunk (2 trunks) [9] 2010/01/28 10:47:50: Resolve 70675: aaaa udp 10.10.1.90 1024 [9] 2010/01/28 10:47:50: Resolve 70675: a udp 10.10.1.90 1024 [9] 2010/01/28 10:47:50: Resolve 70675: udp 10.10.1.90 1024 [5] 2010/01/28 10:47:50: SIP Tx udp:10.10.1.90:1024: SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.10.1.90:1024;branch=z9hG4bK-tit99cgtbg9q;rport=1024 From: "Chris Pendl" <sip:40@10.10.0.9>;tag=dhytveg316 To: <sip:8002752273@10.10.0.9;user=phone>;tag=2526568c61 Call-ID: 3c34d70a133c-l437z7ee50bv CSeq: 1 INVITE Content-Length: 0 [9] 2010/01/28 10:47:50: Resolve 70676: aaaa udp 10.10.1.90 1024 [9] 2010/01/28 10:47:50: Resolve 70676: a udp 10.10.1.90 1024 [9] 2010/01/28 10:47:50: Resolve 70676: udp 10.10.1.90 1024 [5] 2010/01/28 10:47:50: SIP Tx udp:10.10.1.90:1024: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 10.10.1.90:1024;branch=z9hG4bK-tit99cgtbg9q;rport=1024 From: "Chris Pendl" <sip:40@10.10.0.9>;tag=dhytveg316 To: <sip:8002752273@10.10.0.9;user=phone>;tag=2526568c61 Call-ID: 3c34d70a133c-l437z7ee50bv CSeq: 1 INVITE User-Agent: pbxnsip-PBX/3.4.0.3201 WWW-Authenticate: Digest realm="10.10.0.9",nonce="2acca235cefaa3239a09cefca18b5721",domain="sip:8002752273@10.10.0.9;user=phone",algorithm=MD5 Content-Length: 0 [5] 2010/01/28 10:47:50: SIP Rx udp:10.10.1.90:1024: ACK sip:8002752273@10.10.0.9;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.10.1.90:1024;branch=z9hG4bK-tit99cgtbg9q;rport From: "Chris Pendl" <sip:40@10.10.0.9>;tag=dhytveg316 To: <sip:8002752273@10.10.0.9;user=phone>;tag=2526568c61 Call-ID: 3c34d70a133c-l437z7ee50bv CSeq: 1 ACK Max-Forwards: 70 Contact: <sip:40@10.10.1.90:1024;line=68fy0mcb>;reg-id=1 Content-Length: 0 [9] 2010/01/28 10:47:51: Resolve 70677: aaaa udp 10.10.1.90 1024 [9] 2010/01/28 10:47:51: Resolve 70677: a udp 10.10.1.90 1024 [9] 2010/01/28 10:47:51: Resolve 70677: udp 10.10.1.90 1024 [9] 2010/01/28 10:47:52: Resolve 70678: aaaa udp 10.10.1.91 5060 [9] 2010/01/28 10:47:52: Resolve 70678: a udp 10.10.1.91 5060 [9] 2010/01/28 10:47:52: Resolve 70678: udp 10.10.1.91 5060 [9] 2010/01/28 10:48:01: Resolve 70679: aaaa udp 10.10.0.9 26964 [9] 2010/01/28 10:48:01: Resolve 70679: a udp 10.10.0.9 26964 [9] 2010/01/28 10:48:01: Resolve 70679: udp 10.10.0.9 26964 [9] 2010/01/28 10:48:01: Resolve 70680: aaaa udp 10.10.1.90 1024 [9] 2010/01/28 10:48:01: Resolve 70680: a udp 10.10.1.90 1024 [9] 2010/01/28 10:48:01: Resolve 70680: udp 10.10.1.90 1024 [9] 2010/01/28 10:48:02: Resolve 70681: aaaa udp 10.10.0.9 63136 [9] 2010/01/28 10:48:02: Resolve 70681: a udp 10.10.0.9 63136 [9] 2010/01/28 10:48:02: Resolve 70681: udp 10.10.0.9 63136 [9] 2010/01/28 10:48:06: Resolve 70682: aaaa udp 10.10.1.91 5060 [9] 2010/01/28 10:48:06: Resolve 70682: a udp 10.10.1.91 5060 [9] 2010/01/28 10:48:06: Resolve 70682: udp 10.10.1.91 5060 [9] 2010/01/28 10:48:09: Remote site closed the connection Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 29, 2010 Report Share Posted January 29, 2010 The phone does not answer the challenge it seems. Try a newer firmware version, the one you are using might be buggy. Quote Link to comment Share on other sites More sharing options...
cpendl Posted March 18, 2010 Author Report Share Posted March 18, 2010 The phone does not answer the challenge it seems. Try a newer firmware version, the one you are using might be buggy. Found out what was going on here...the firewall was rejecting the packets because the headers were too large and contained all of the codecs. I removed the ones that weren't being used, and the problem has been solved. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 19, 2010 Report Share Posted March 19, 2010 Found out what was going on here...the firewall was rejecting the packets because the headers were too large and contained all of the codecs. I removed the ones that weren't being used, and the problem has been solved. Ouch. See why I have a problem with firewalls? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.