Jump to content

Calls Disconnect and No Inbound Calls


Recommended Posts

Hello,

 

My first issue is that the outgoing calling seems to work just fine, except for 1 issue. After the call connects, you only have 8-9 seconds to talk and then the call is dead, here is an example of the SIPTrace that I did from Axon.

 

----------------------------------------------------------------

 

04:21:34 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:34 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:34 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:34 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:34 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:34 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:34 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:34 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:34 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 UDP Packet Received from 64.34.176.212:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.0.100:62781;branch=z9hG4bK46956;received=65.35.198.95;rport=62781

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 872 INVITE

User-Agent: LES.NET.VoIP

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Contact: <sip:17278085703@64.34.176.212>

Content-Type: application/sdp

Content-Length: 218

 

v=0

o=root 28156 28157 IN IP4 64.34.176.212

s=session

c=IN IP4 64.34.176.212

t=0 0

m=audio 12172 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=silenceSupp:off - - - -

 

----------------------------------------------------------------

 

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 64.34.176.212:12172 >>> 192.168.0.100:8000 (172 bytes)

04:21:35 Rtp Relay 192.168.0.100:8000 >>> 64.34.176.212:12172 (172 bytes)

04:21:35 UDP Packet Sent to 64.34.176.212:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:17278085703@64.34.176.212 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK47956

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 872 ACK

Max-Forwards: 20

User-Agent: NCH Swift Sound Axon 1.20

Proxy-Authorization: Digest username="1305517377",realm="did.voip.les.net",nonce="038d0c54",uri="sip:17278085703@did.voip.les.net",response="14412e0d5a50c4954c8bd760bf0a63f1",opaque="",algorithm=MD5

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Sent to 64.34.176.212:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BYE sip:17278085703@64.34.176.212 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK48956

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 873 BYE

Max-Forwards: 20

User-Agent: NCH Swift Sound Axon 1.20

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Sent to 65.35.198.95:60820 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

BYE sip:101@65.35.198.95:60820 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK49956

To: "Larry Braziel" <sip:101@65.35.198.95>;tag=1383

From: <sip:117278085703@65.35.198.95>;tag=4058

Call-ID: 1184571550-848-WITSERVER@192.168.0.100

CSeq: 871 BYE

Max-Forwards: 20

User-Agent: NCH Swift Sound Axon 1.20

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Sent to 64.34.176.212:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:17278085703@64.34.176.212 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK47956

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 872 ACK

Max-Forwards: 20

User-Agent: NCH Swift Sound Axon 1.20

Proxy-Authorization: Digest username="1305517377",realm="did.voip.les.net",nonce="038d0c54",uri="sip:17278085703@did.voip.les.net",response="14412e0d5a50c4954c8bd760bf0a63f1",opaque="",algorithm=MD5

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Sent to 64.34.176.212:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:17278085703@64.34.176.212 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK47956

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 872 ACK

Max-Forwards: 20

User-Agent: NCH Swift Sound Axon 1.20

Proxy-Authorization: Digest username="1305517377",realm="did.voip.les.net",nonce="038d0c54",uri="sip:17278085703@did.voip.les.net",response="14412e0d5a50c4954c8bd760bf0a63f1",opaque="",algorithm=MD5

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Sent to 64.34.176.212:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:17278085703@64.34.176.212 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK47956

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 872 ACK

Max-Forwards: 20

User-Agent: NCH Swift Sound Axon 1.20

Proxy-Authorization: Digest username="1305517377",realm="did.voip.les.net",nonce="038d0c54",uri="sip:17278085703@did.voip.les.net",response="14412e0d5a50c4954c8bd760bf0a63f1",opaque="",algorithm=MD5

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Sent to 64.34.176.212:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:17278085703@64.34.176.212 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK47956

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 872 ACK

Max-Forwards: 20

User-Agent: NCH Swift Sound Axon 1.20

Proxy-Authorization: Digest username="1305517377",realm="did.voip.les.net",nonce="038d0c54",uri="sip:17278085703@did.voip.les.net",response="14412e0d5a50c4954c8bd760bf0a63f1",opaque="",algorithm=MD5

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Received from 65.35.198.95:60820 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.0.100:62781;rport;branch=z9hG4bK49956

To: "Larry Braziel" <sip:101@65.35.198.95>;tag=1383

From: <sip:117278085703@65.35.198.95>;tag=4058

Call-ID: 1184571550-848-WITSERVER@192.168.0.100

CSeq: 871 BYE

User-Agent: NCH Swift Sound Express Talk 2.06

Content-Length: 0

 

 

----------------------------------------------------------------

 

04:21:35 UDP Packet Received from 64.34.176.212:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.0.100:62781;branch=z9hG4bK48956;received=65.35.198.95;rport=62781

From: "Larry Braziel" <sip:1305517377@did.voip.les.net>;tag=4057

To: <sip:17278085703@did.voip.les.net>;tag=as0d82e348

Call-ID: 1184573455-956-WITSERVER@192.168.0.100

CSeq: 873 BYE

User-Agent: LES.NET.VoIP

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

Contact: <sip:17278085703@64.34.176.212>

Content-Length: 0

X-Asterisk-HangupCause: Normal Clearing

 

 

 

 

The 2nd issue that I'm having is that incoming calls are not working. When a calls comes in, I see the following error message in the Axon dialog screen:

 

4:03:04 Incoming call failed

04:03:04 Unable to find any lines with the ID "7274707622" or extensions with the ID "7278085703".

 

 

So, it's stating that it can not find any lines with the ID 7274707622 or any extensions with my cell # ID 7278085703. I have the lines setup as followed:

 

Line 1

-------

External Line Name ID or Username Proxy Server Ring On Edit Delete

----------------------------------------------------------------------------------------------------------------

7274707622 1305517377 did.voip.les.net 701 Edit Line Delete Line

 

 

 

Please let me know how I can resolve this as soon as possible. Thank you. I need to get my lines working ASAP, as I have been advertising them.

 

 

Regards,

Larry Braziel

Whitewater IT

Link to post
Share on other sites

I got the inbound calling working. It was an issue with my trunks with my service provider and some settings I had to play around with, with the inbound caller ID.

 

However... I need to get my outbound calling issue resolved, ASAP. It's nearly impossible to call someone and have my calls drop out after 8-9 seconds of speaking with a customer. They will thing that we are rude and unprofessional. You get my point?

 

Please help me with this last issue, ASAP!

 

Regards,

Larry Braziel Jr.

Whitewater IT

New Port Richey, FL

Link to post
Share on other sites
  • 4 weeks later...
  • 2 months later...
I got the inbound calling working. It was an issue with my trunks with my service provider and some settings I had to play around with, with the inbound caller ID.

 

However... I need to get my outbound calling issue resolved, ASAP. It's nearly impossible to call someone and have my calls drop out after 8-9 seconds of speaking with a customer. They will thing that we are rude and unprofessional. You get my point?

 

Please help me with this last issue, ASAP!

 

Regards,

Larry Braziel Jr.

Whitewater IT

New Port Richey, FL

 

Because no further information , let me guess...

 

If your SIP phone (soft/hard) or gateway device with "silence detection" or something like that, disable it and "Voice Activity Detection" as well .

Link to post
Share on other sites

Hi Larry

 

I managed to solve the problem by removing one of two IP-adresses assigned to the network card on the server. In the log I found that the wrong IP-address was used by Axon and when it did the call seems to disconnnect. I think this caused the disconnecting after 8-9 seconds. I hope this information helps.

 

/Bobby

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...