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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP Trunking Trace

Status
Not open for further replies.

texmatlock

Programmer
May 23, 2013
44
US
I am seeing the following every few minutes. This SIP trunk is having problems. Does anyone know what all this means?

3265219447mS Sip: SIP Line (19): Options timer expired
3265219448mS Sip: SIPDialog f5199000 created, size 1
3265219448mS Sip: (f5199000) SendSIPRequest: OPTIONS SENT TO 10.120.17.24 5060
3265219449mS SIP Reg/Opt Tx: 19
OPTIONS sip:10.120.17.24 SIP/2.0
Via: SIP/2.0/UDP 10.120.17.23:5060;rport;branch=z9hG4bKe3434a722aebfff84b9eb8d940025c7e
From: <sip:10.120.17.23>;tag=6736e9bb098f36c1
To: <sip:10.120.17.24>
Call-ID: ef674ad2979a578a1e027bba54fa524f
CSeq: 1082474211 OPTIONS
Contact: <sip:10.120.17.23:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
User-Agent: IP Office 8.1 (63)
Content-Length: 0

3265219449mS SIP Tx: UDP 10.120.17.23:5060 -> 10.120.17.24:5060
OPTIONS sip:10.120.17.24 SIP/2.0
Via: SIP/2.0/UDP 10.120.17.23:5060;rport;branch=z9hG4bKe3434a722aebfff84b9eb8d940025c7e
From: <sip:10.120.17.23>;tag=6736e9bb098f36c1
To: <sip:10.120.17.24>
Call-ID: ef674ad2979a578a1e027bba54fa524f
CSeq: 1082474211 OPTIONS
Contact: <sip:10.120.17.23:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
User-Agent: IP Office 8.1 (63)
Content-Length: 0

3265219453mS SIP Rx: UDP 10.120.17.24:5060 -> 10.120.17.23:5060
SIP/2.0 200 OK
From: <sip:10.120.17.23>;tag=6736e9bb098f36c1
To: <sip:10.120.17.24>;tag=31bf5d90-a781118-13c4-52728853-528dd076-52728853
Call-ID: ef674ad2979a578a1e027bba54fa524f
CSeq: 1082474211 OPTIONS
Via: SIP/2.0/UDP 10.120.17.23:5060;rport=5060;branch=z9hG4bKe3434a722aebfff84b9eb8d940025c7e
Supported: 100rel,sipvc,x-nortel-sipvc,replaces
User-Agent: Nortel Networks BCM VoIP Gateway release_44 version_44.134.0.33
Allow: INVITE,UPDATE,INFO,ACK,OPTIONS,CANCEL,BYE,NOTIFY,PRACK,REFER
Content-Length: 0

3265219455mS SIP Reg/Opt Rx: 19
SIP/2.0 200 OK
From: <sip:10.120.17.23>;tag=6736e9bb098f36c1
To: <sip:10.120.17.24>;tag=31bf5d90-a781118-13c4-52728853-528dd076-52728853
Call-ID: ef674ad2979a578a1e027bba54fa524f
CSeq: 1082474211 OPTIONS
Via: SIP/2.0/UDP 10.120.17.23:5060;rport=5060;branch=z9hG4bKe3434a722aebfff84b9eb8d940025c7e
Supported: 100rel,sipvc,x-nortel-sipvc,replaces
User-Agent: Nortel Networks BCM VoIP Gateway release_44 version_44.134.0.33
Allow: INVITE,UPDATE,INFO,ACK,OPTIONS,CANCEL,BYE,NOTIFY,PRACK,REFER
Content-Length: 0

3265219455mS Sip: (f5199000) Process SIP response dialog f5199000, method OPTIONS, CodeNum 200 in state SIPDialog::INITIAL(0)
3265219456mS Sip: (f5199000) UpdateSIPCallState SIPDialog::INITIAL(0) -> SIPDialog::FINAL(27)
3265224455mS Sip: sip_indicateTimeOut Timer 11
3265224455mS Sip: Timer 11 callback found dialog f5199000 ef674ad2979a578a1e027bba54fa524f OPTIONS SIPDialog::FINAL
3265224455mS Sip: Completed ... (todelete) removing Dialog f5199000 of CallId: ef674ad2979a578a1e027bba54fa524f and State: SIPDialog::FINAL(27)
3265224455mS Sip: SIPDialog f5199000 destroyed, size 0

 
Why don't you give us a general overview of the situation/setup, going straight into a trace makes it hard to picture what you have got :)

 
This is an IPO 8. It has SIP trunks to 2 different BCM 450's.
Also SCN to 3 other IPOs.
The SIP trunk to one of the BCM's is good. The H323's are all up.
But the SIP trunk in question, which is shown in the trace, is having problems. Calls can make it into the IPO from the BCM, but not the other way around.
Also calls placed from the BCM to one of the other IPO's through this IPO do not make it.

The trace activity above is indicative of something that is not user generated. Its appearing in the trace every few minutes even when no one is attempting to use that trunk.
 
Post traces of the calls described above failing, that will indicate the issue better than the trace provided :)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top