Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

All DIDs coming up not in services 500v2 9.1.600.153

Status
Not open for further replies.

SAToronto

IS-IT--Management
Sep 21, 2011
199
CA
My 500V2 all of a sudden has every DID coming up as not in service intermittently
Approximately 3 out of 5 times it say not in services
As you can see in the logs below the calls are clearly hitting the PBX via my sip trunks
I have done the following to try and resolve

rebooted PBX several times
Deleted and re added DID#s (this has worked in the past)
The log below shows my call

70396826mS SIP Rx: UDP 10.9.254.2:39279 -> 10.9.100.10:5060
OPTIONS sip:10.9.100.10 SIP/2.0
Via: SIP/2.0/UDP 10.15.5.136:5060;rport;branch=z9hG4bK73a2a56ed715c9b499c277e5c6986a12
From: <sip:10.15.5.136>;tag=0aae968063dc1975
To: <sip:10.9.100.10>
Call-ID: 9922f45f669248bacc4f511199fb3300
CSeq: 441369077 OPTIONS
Contact: <sip:10.15.5.136:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.1.6.0 build 153
Content-Length: 0

70396828mS SIP Reg/Opt Rx: phone
OPTIONS sip:10.9.100.10 SIP/2.0
Via: SIP/2.0/UDP 10.15.5.136:5060;rport;branch=z9hG4bK73a2a56ed715c9b499c277e5c6986a12
From: <sip:10.15.5.136>;tag=0aae968063dc1975
To: <sip:10.9.100.10>
Call-ID: 9922f45f669248bacc4f511199fb3300
CSeq: 441369077 OPTIONS
Contact: <sip:10.15.5.136:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.1.6.0 build 153
Content-Length: 0

70397588mS SIP Rx: UDP 10.9.254.2:11967 -> 10.9.100.10:5060
INVITE sip:xxxxxx9993@10.9.100.10;user=phone SIP/2.0
Max-Forwards: 48
Session-Expires: 86400;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:xxxxx9993@10.9.100.10;user=phone>
From: "xxxxx" <sip:4xxxxx87099@10.254.11.4>;tag=3672056311-520696
Call-ID: 1215732-3672056311-520690@SBC2-TOR.mydomain.com
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP 10.254.11.4:5060;branch=z9hG4bK2dbc0c885b9bce178326d137587fb6a3
Contact: <sip:4162187099@10.254.11.4:5060;tgrp=KLWNBCSBC11>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 224

v=0
o=SBC2-TOR 1463064487970 1463064487970 IN IP4 10.254.11.4
s=sip call
c=IN IP4 10.254.11.5
t=0 0
m=audio 20914 RTP/AVP 18 0 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=fmtp:18 annexb=no
70397591mS SIP Call Rx: phone
INVITE sip:2507629993@10.9.100.10;user=phone SIP/2.0
Max-Forwards: 48
Session-Expires: 86400;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:xxxxxx9993@10.9.100.10;user=phone>
From: "xxx" <sip:xxx099@10.254.11.4>;tag=3672056311-520696
Call-ID: 1215732-3672056311-520690@SBC2-TOR.mydomain.com
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP 10.254.11.4:5060;branch=z9hG4bK2dbc0c885b9bce178326d137587fb6a3
Contact: <sip:xxxx099@10.254.11.4:5060;tgrp=KLWNBCSBC11>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 224

v=0
o=SBC2-TOR 1463064487970 1463064487970 IN IP4 10.254.11.4
s=sip call
c=IN IP4 10.254.11.5
t=0 0
m=audio 20914 RTP/AVP 18 0 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=fmtp:18 annexb=no
70398088mS SIP Rx: UDP 10.9.254.2:11967 -> 10.9.100.10:5060
INVITE sip:2507629993@10.9.100.10;user=phone SIP/2.0
Max-Forwards: 48
Session-Expires: 86400;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:2507629993@10.9.100.10;user=phone>
From: "xxxxx" <sip:4xxxx187099@10.254.11.4>;tag=3672056311-520696
Call-ID: 1215732-3672056311-520690@SBC2-TOR.mydomain.com
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP 10.254.11.4:5060;branch=z9hG4bK2dbc0c885b9bce178326d137587fb6a3
Contact: <sip:xxxxx099@10.254.11.4:5060;tgrp=KLWNBCSBC11>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 224

v=0
o=SBC2-TOR 1463064487970 1463064487970 IN IP4 10.254.11.4
s=sip call
c=IN IP4 10.254.11.5
t=0 0
m=audio 20914 RTP/AVP 18 0 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=fmtp:18 annexb=no
70398091mS SIP Call Rx: phone
INVITE sip:2507629993@10.9.100.10;user=phone SIP/2.0
Max-Forwards: 48
Session-Expires: 86400;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:xxx629993@10.9.100.10;user=phone>
From: "Sxxxxxx" <sip:xxxx7099@10.254.11.4>;tag=3672056311-520696
Call-ID: 1215732-3672056311-520690@SBC2-TOR.mydomain.com
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP 10.254.11.4:5060;branch=z9hG4bK2dbc0c885b9bce178326d137587fb6a3
Contact: <sip:xxxxx7099@10.254.11.4:5060;tgrp=KLWNBCSBC11>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 224

v=0
o=SBC2-TOR 1463064487970 1463064487970 IN IP4 10.254.11.4
s=sip call
c=IN IP4 10.254.11.5
t=0 0
m=audio 20914 RTP/AVP 18 0 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=fmtp:18 annexb=no
70399088mS SIP Rx: UDP 10.9.254.2:11967 -> 10.9.100.10:5060
INVITE sip:xxxxx9993@10.9.100.10;user=phone SIP/2.0
Max-Forwards: 48
Session-Expires: 86400;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:xxxxx629993@10.9.100.10;user=phone>
From: "xxxx" <sip:xxxx187099@10.254.11.4>;tag=3672056311-520696
Call-ID: 1215732-3672056311-520690@SBC2-TOR.mydomain.com
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP 10.254.11.4:5060;branch=z9hG4bK2dbc0c885b9bce178326d137587fb6a3
Contact: <sip:xxxx99@10.254.11.4:5060;tgrp=KLWNBCSBC11>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 224

v=0
o=SBC2-TOR 1463064487970 1463064487970 IN IP4 10.254.11.4
s=sip call
c=IN IP4 10.254.11.5
t=0 0
m=audio 20914 RTP/AVP 18 0 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=fmtp:18 annexb=no
70399091mS SIP Call Rx: phone
INVITE sip:xxxx629993@10.9.100.10;user=phone SIP/2.0
Max-Forwards: 48
Session-Expires: 86400;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:2507629993@10.9.100.10;user=phone>
From: "xxxxxxx" <sip:xxxx187099@10.254.11.4>;tag=3672056311-520696 <-- my DID
Call-ID: 1215732-3672056311-520690@SBC2-TOR.mydomain.com
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP 10.254.11.4:5060;branch=z9hG4bK2dbc0c885b9bce178326d137587fb6a3
Contact: <sip:xxxx099@10.254.11.4:5060;tgrp=KLWNBCSBC11>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 224

v=0
o=SBC2-TOR 1463064487970 1463064487970 IN IP4 10.254.11.4
s=sip call
c=IN IP4 10.254.11.5
t=0 0
m=audio 20914 RTP/AVP 18 0 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=fmtp:18 annexb=no
70400828mS SIP Rx: UDP 10.9.100.50:5060 -> 10.9.100.10:5060


********** Warning: Logging to Screen Stopped **********

 
I would wager it's a programming error/mismatch, that trace is all Rx and no Tx, so it's either missing from the trace or the IPO isn't responding which usually means it's ignoring it for a reason :)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top