Hi Team,
Hope you all are doing well…
We need Your Support for incoming call issue in Asterisk Server.
I have installed Asterisk 11.8.1 in Centos 6.5 with Core I3 Processor which has 4GB RAM and 500GB Hard-Drive.
I have taken PRI-Lines from Tata Teletel India Telecom Company. I have mapped our Asterisk server with SIP Trunk. When our front-end customer wants to dialed on our PRI(Pilot) number i.e ‘011-12345678’ its get connected successfully with my asterisk machine and proper IVR Plays and entire application working fine in which out-bound called happened. But “some time” or “some fraction of time slot” some callers again wants to connect with our PRI server they can’t able to make call on my PRI, if they called it from mobile number call-disconnected within 1 second if they called it from Landline or pstn it’s say Dialed number doesn’t exist ,Please check the number’ and I am not able to see any SIP logs on my asterisk server after 30 to 40 second its works fine. All incoming calls get connected successfully and no issue But this issue come 20 to 30 times in a Day and our customer would irritates just because of call not connected:
Please suggest me what should I do to resolve this issue
Below is my SIP Logs
Scheduling destruction of SIP dialog ['038d200307191120@XX.X.XX.XX](mailto:'038d200307191120@XX.X.XX.XX)' in 32000 ms (Method: OPTIONS) Really destroying SIP dialog ['038d200307191120@XX.X.XX.XX](mailto:'038d200307191120@XX.X.XX.XX)' Method: OPTIONS [2015-02-06 16:27:09] NOTICE[24508]: chan_sip.c:15059 sip_reregister: -- Re-registration for [XXXXXXX@XX.X.XX.XX](mailto:XXXXXXX@XX.X.XX.XX) REGISTER 11 headers, 0 lines Reliably Transmitting (no NAT) to XX.X.XX.XX:5060: REGISTER sip:XX.X.XX.XX SIP/2.0 Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK192c93fb Max-Forwards: 70 From: <sip:XXXXXXX@XX.X.XX.XX>;tag=as645301b7 To: <sip:XXXXXXX@XX.X.XX.XX> Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 778 REGISTER
User-Agent: Asterisk PBX 11.8.1
Authorization: Digest username=“XXXXXXX”, realm=“SIP-XXXXXXX”, algorithm=MD5, uri=“sip:XX.X.XX.XX”, nonce=“67a22382fd5f88b5a1a239e8d69884ad”, response="7be6c3df2c8f02824fbeedd1c0b1d900"
Expires: 300
Contact: sip:XXXXXXX@XX.X.XX.XXX:5060
Content-Length: 0
<— SIP read from UDP:XX.X.XX.XX:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK192c93fb
To: sip:XXXXXXX@XX.X.XX.XX
From: sip:XXXXXXX@XX.X.XX.XX;tag=as645301b7
Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 778 REGISTER
User-Agent: ZTE-SoftSwitch
Content-Length: 0
WWW-Authenticate: Digest realm=“SIP-XXXXXXX”,nonce=“225e999d00e77800bc32c8c51079444c”,ZTE-ID=a59211495dab314eb5ded58cc9e4e6e1
<------------->
— (9 headers 0 lines) —
Responding to challenge, registration to domain/host name XX.X.XX.XX
REGISTER 11 headers, 0 lines
Reliably Transmitting (no NAT) to XX.X.XX.XX:5060:
REGISTER sip:XX.X.XX.XX SIP/2.0
Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK102ef31e
Max-Forwards: 70
From: sip:XXXXXXX@XX.X.XX.XX;tag=as645301b7
To: sip:XXXXXXX@XX.X.XX.XX
Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 779 REGISTER
User-Agent: Asterisk PBX 11.8.1
Authorization: Digest username=“XXXXXXX”, realm=“SIP-XXXXXXX”, algorithm=MD5, uri=“sip:XX.X.XX.XX”, nonce=“225e999d00e77800bc32c8c51079444c”, response="23237f4c532606a0bd61462ab6cdbb10"
Expires: 300
Contact: sip:XXXXXXX@XX.X.XX.XXX:5060
Content-Length: 0
<— SIP read from UDP:XX.X.XX.XX:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK102ef31e
To: sip:XXXXXXX@XX.X.XX.XX
From: sip:XXXXXXX@XX.X.XX.XX;tag=as645301b7
Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 779 REGISTER
Contact: sip:XXXXXXX@XX.X.XX.XXX:5060;expires=300
User-Agent: ZTE-SoftSwitch
Date: Fri, 06 Feb 2015 16:28:57 GMT
Content-Length: 0
<------------->
— (10 headers 0 lines) —
[2015-02-06 16:27:09] NOTICE[24508]: chan_sip.c:23519 handle_response_register: Outbound Registration: Expiry for XX.X.XX.XX is 300 sec (Scheduling reregistration in 285 s)
Really destroying SIP dialog ‘18e1b9d23f9158fb259b22566ae35ca3@[::1]’ Method: REGISTER
<— SIP read from UDP:XX.X.XX.XX:5060 —>
OPTIONS sip:XXXXXXX@XX.X.XX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP XX.X.XX.XX:5060;branch=z9hG4bK1d2e39ec06ce4bdctaN0
Max-Forwards: 70
To: sip:XXXXXXX@XX.X.XX.XX
From: BgwLinkTest5031 sip:bgw@XX.X.XX.XX;tag=200307191120
Call-ID: 216d200307191120@XX.X.XX.XX
CSeq: 1000 OPTIONS
Accept: application/sdp
Content-Length: 0
<------------->
— (9 headers 0 lines) —
Sending to XX.X.XX.XX:5060 (no NAT)
Looking for XXXXXXX in from-general (domain XX.X.XX.XXX)
<— Transmitting (no NAT) to XX.X.XX.XX:5060 —>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP XX.X.XX.XX:5060;branch=z9hG4bK1d2e39ec06ce4bdctaN0;received=XX.X.XX.XX
From: BgwLinkTest5031 sip:bgw@XX.X.XX.XX;tag=200307191120
To: sip:XXXXXXX@XX.X.XX.XX;tag=as5fe200cf
Call-ID: 216d200307191120@XX.X.XX.XX
CSeq: 1000 OPTIONS
Server: Asterisk PBX 11.8.1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Accept: application/sdp
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '216d200307191120@XX.X.XX.XX’ in 32000 ms (Method: OPTIONS)
Really destroying SIP dialog '216d200307191120@XX.X.XX.XX’ Method: OPTIONS
asterisk_serverCLI>
asterisk_serverCLI>
[2015-02-06 16:31:54] NOTICE[24508]: chan_sip.c:15059 sip_reregister: – Re-registration for XXXXXXX@XX.X.XX.XX
REGISTER 11 headers, 0 lines
Reliably Transmitting (no NAT) to XX.X.XX.XX:5060:
REGISTER sip:XX.X.XX.XX SIP/2.0
Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK4277869c
Max-Forwards: 70
From: sip:XXXXXXX@XX.X.XX.XX;tag=as645301b7
To: sip:XXXXXXX@XX.X.XX.XX
Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 780 REGISTER
User-Agent: Asterisk PBX 11.8.1
Authorization: Digest username=“XXXXXXX”, realm=“SIP-XXXXXXX”, algorithm=MD5, uri=“sip:XX.X.XX.XX”, nonce=“225e999d00e77800bc32c8c51079444c”, response="23237f4c532606a0bd61462ab6cdbb10"
Expires: 300
Contact: sip:XXXXXXX@XX.X.XX.XXX:5060
Content-Length: 0
<— SIP read from UDP:XX.X.XX.XX:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK4277869c
To: sip:XXXXXXX@XX.X.XX.XX
From: sip:XXXXXXX@XX.X.XX.XX;tag=as645301b7
Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 780 REGISTER
User-Agent: ZTE-SoftSwitch
Content-Length: 0
WWW-Authenticate: Digest realm=“SIP-XXXXXXX”,nonce=“227a17cfad5fe1450b8d4fdaead6a124”,ZTE-ID=123545f9287fd760cf11b2a18f16981f
<------------->
— (9 headers 0 lines) —
Responding to challenge, registration to domain/host name XX.X.XX.XX
REGISTER 11 headers, 0 lines
Reliably Transmitting (no NAT) to XX.X.XX.XX:5060:
REGISTER sip:XX.X.XX.XX SIP/2.0
Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK6b89cc96
Max-Forwards: 70
From: sip:XXXXXXX@XX.X.XX.XX;tag=as645301b7
To: sip:XXXXXXX@XX.X.XX.XX
Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 781 REGISTER
User-Agent: Asterisk PBX 11.8.1
Authorization: Digest username=“XXXXXXX”, realm=“SIP-XXXXXXX”, algorithm=MD5, uri=“sip:XX.X.XX.XX”, nonce=“227a17cfad5fe1450b8d4fdaead6a124”, response="8639103a65278ce6176708745da06ccc"
Expires: 300
Contact: sip:XXXXXXX@XX.X.XX.XXX:5060
Content-Length: 0
<— SIP read from UDP:XX.X.XX.XX:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP XX.X.XX.XXX:5060;branch=z9hG4bK6b89cc96
To: sip:XXXXXXX@XX.X.XX.XX
From: sip:XXXXXXX@XX.X.XX.XX;tag=as645301b7
Call-ID: 18e1b9d23f9158fb259b22566ae35ca3@[::1]
CSeq: 781 REGISTER
Contact: sip:XXXXXXX@XX.X.XX.XXX:5060;expires=300
User-Agent: ZTE-SoftSwitch
Date: Fri, 06 Feb 2015 16:33:42 GMT
Content-Length: 0
<------------->
— (10 headers 0 lines) —
[2015-02-06 16:31:54] NOTICE[24508]: chan_sip.c:23519 handle_response_register: Outbound Registration: Expiry for XX.X.XX.XX is 300 sec (Scheduling reregistration in 285 s)
Really destroying SIP dialog ‘18e1b9d23f915enter code here
8fb259b22566ae35ca3@[::1]’ Method: REGISTER `