SIPSwitch Troubleshooting

Support zone
User avatar
Aaron
Site Admin
Posts: 4563
Joined: Thu Jul 12, 2007 12:13 am

SIPSwitch Troubleshooting

Post by Aaron » Sun Jan 27, 2008 5:05 pm

Hi,

From time-to-time most people using the sipswitch will come across a problem that relates to dial plan matching, inability to call out to a certain provider, an account not registering etc. This is to be expected and one of the main goals of the sipswitch was to provide a way of peeking under the hood to provide a degree of self-help when trying to narrow down such issues.

The sipswitch provides a telnet console that every user can log into and view summary messages the sipswitch generates relating to their account or they can switch on full SIP tracing to view all SIP traffic related to their account. The instructions to use the console are below.

1. The console can be connected to by using: telnet sip.mysipswitch.com 11005, once connected you need to login with your sipswitch username and password,

2. Once logged in you will be presented with a "filter=>" prompt. This is where you select the type of information you would like displayed.

a. Leave it blank by just pressing enter. This will display summary messages for your account and is useful in troubleshooting dial plan issues and other oddities,

b. Type "event full" without the quotes. This will display all SIP messages that are received for your account and is useful in troubleshooting SIP signalling issues.

3. To stop the messages and get back to the filter prompt press the "s" key. To quit the console press the "q" key.

Regards,

Aaron
Last edited by Aaron on Mon Jan 28, 2008 2:55 pm, edited 1 time in total.

hkr
Posts: 72
Joined: Sat Dec 15, 2007 10:05 am

Re: SIPSwitch Troubleshooting

Post by hkr » Mon Jan 28, 2008 12:45 pm

Connected to sip.mysipswitch.com (213.200.94.182).
Escape character is '^]'.
username=> USERNAME
password=> ******
welcome *******
filter=> event = full
filter=ipaddress=*, user=USERNAME, event==, request=*, serveripaddress=*, server=*, regex=.*.
.
q
s^[[3~
s
s
^X

----

Seems I do not get any further messages, and I cannot quit, apart from quitting telnet itself by pressing CTRL-]

User avatar
Aaron
Site Admin
Posts: 4563
Joined: Thu Jul 12, 2007 12:13 am

Post by Aaron » Mon Jan 28, 2008 2:59 pm

Sorry my mistake it should be "event full" and not "event = full".

If the telnet connection times out then you won't get any response when the s or q keys are pressed and will need to use Ctrl-] to quit. Your connection will be timed out by the NAT in your router if there is no traffic. I probably should add some kind of keep alive packet so this doesn't happen but int the meantime it's a limitation. Most NAT's won't time a connection out for 5 to 10 minutes and if you do get an event during that time it will refresh the connection and keep it open.

Regards,

Aaron

Evgen
Posts: 17
Joined: Fri Feb 15, 2008 7:32 pm
Location: Russia

Post by Evgen » Sun Feb 17, 2008 6:57 pm

I can see NewMessage "18:41:46:143: Response 487 Request cancelled for ...", but I've never seen "Bye" messages. And how can I see full SIP-messages from mysipswith server?

User avatar
Aaron
Site Admin
Posts: 4563
Joined: Thu Jul 12, 2007 12:13 am

Post by Aaron » Sun Feb 17, 2008 11:42 pm

Hi Evgen,

If you type the below you should get full SIP messages on your console:

filter => event full

The mechanism used to determine which user owns which SIP message and therefore whether to display it or not is to search for your sipswitch username in the SIP message. The username must exist in the format below:

:username@

Which is designed to match the From header:

From <sip:username@sip.mysipswitch.com>

That will work fine for the incoming calls but for outgoing calls if you have set a custom From header it won't. If you are not seeing your outgoing calls and have a custom From header either remove it for a test or put the require string in the display name, for example:

From: ":username@" <sip:123456@sip.provider.com>

Regards,

Aaron

Evgen
Posts: 17
Joined: Fri Feb 15, 2008 7:32 pm
Location: Russia

Post by Evgen » Tue Feb 19, 2008 10:47 am

Thank you. One more question: may I see SIP-messages between sipswitch and my voip-provider?

User avatar
Aaron
Site Admin
Posts: 4563
Joined: Thu Jul 12, 2007 12:13 am

Post by Aaron » Tue Feb 19, 2008 11:00 am

Hi Evgen,

The only way at the moment would be if your sipswitch username matched the name you were using with your provider.

We're still trying to find a better way to match SIP packets to users and the only mechanism we have at teh moment is to match on the sipswitch username.

Regards,

Aaron

iporter
Posts: 12
Joined: Sun Aug 31, 2008 8:00 am

Post by iporter » Thu Sep 11, 2008 10:25 am

Aaron,

Maybe I'm a complete novice, but I have now read it three times and am non the wiser.

Can you give me a step by step approach with this.

Thanks,

Ian
Ian

gbonnet
Site Admin
Posts: 680
Joined: Wed Jul 11, 2007 2:58 pm
Location: Bologna
Contact:

Post by gbonnet » Thu Sep 11, 2008 10:30 am

hi iporter,

you need to open the console, on windows :
press the windows key + R at the same time
there enter: cmd
that should bring the black DOS console

there enter :
telnet sip.mysipswitch.com 11005

Then, you'll be prompted for username / password.
you should then see : "filter ="
enter : event full
and press enter

You should see the SIP traffic associated to your account going through

HTH
Guillaume
Blueface [url=http://www.blueface.ie/]Phone[/url] Service

iporter
Posts: 12
Joined: Sun Aug 31, 2008 8:00 am

Post by iporter » Thu Sep 11, 2008 10:38 am

Aaron,

I waited a while and eventually the telnet screen flashed more data on it.

I called my Sipgate number a few times and this resulted in generating this data.

Can you make any sense of it?




a=sendrecv

FullSIPTrace 11:33:33:091:
Response Received (UDP): 77.67.57.195:5060<-194.120.0.198:5060
SIP/2.0 400 Bad request
Via: SIP/2.0/UDP 77.67.57.195:5060;branch=z9hG4bK5dda0205bb7b49f6ba7efae25b5026d
e
To: <sip:iporter@sip.voipcheap.co.uk>
From: <sip:iporter@sip.voipcheap.co.uk>;tag=1408834978
Call-ID: bdd15efdce614df5a6edd0a16bb04e5c
CSeq: 1 INVITE
Contact: <sip:194.120.0.198:5060>
Server: (Very nice Sip Registrar/Proxy Server)
Allow: ACKBYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE


FullSIPTrace 11:33:33:091:
Request Sent (UDP): 77.67.57.195:5060->194.120.0.198:5060
ACK sip:iporter@sip.voipcheap.co.uk SIP/2.0
Via: SIP/2.0/UDP 77.67.57.195:5060;branch=z9hG4bK5dda0205bb7b49f6ba7efae25b5026d
e
To: <sip:iporter@sip.voipcheap.co.uk>
From: <sip:iporter@sip.voipcheap.co.uk>;tag=1408834978
Call-ID: bdd15efdce614df5a6edd0a16bb04e5c
CSeq: 1 ACK
Max-Forwards: 70


FullSIPTrace 11:33:33:122:
Proxy Request Received (UDP): 213.200.94.182:5060<-217.10.79.23:5060
ACK sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK63c5.f3e6e064.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK63c5.f3e6e064.0
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as7f9cf59e
Call-ID: 0075948f6d5f08d6471612e243244c9a@sipgate.co.uk
CSeq: 102 ACK
Max-Forwards: 10
Record-Route: <sip:217.10.79.23;lr=on;ftag=as7f9cf59e>


FullSIPTrace 11:33:33:122:
Proxy Request Sent (UDP): 213.200.94.182:5060->77.67.57.195:5060
ACK sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bK4E667F39321848426F2B1B225F8DE
655AD8463EB
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK63c5.f3e6e064.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK63c5.f3e6e064.0
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as7f9cf59e
Call-ID: 0075948f6d5f08d6471612e243244c9a@sipgate.co.uk
CSeq: 102 ACK
Max-Forwards: 9
Record-Route: <sip:217.10.79.23;lr=on;ftag=as7f9cf59e>


FullSIPTrace 11:33:33:122:
Request Received (UDP): 77.67.57.195:5060<-213.200.94.182:5060
ACK sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bK4E667F39321848426F2B1B225F8DE
655AD8463EB
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK63c5.f3e6e064.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK63c5.f3e6e064.0
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as7f9cf59e
Call-ID: 0075948f6d5f08d6471612e243244c9a@sipgate.co.uk
CSeq: 102 ACK
Max-Forwards: 9
Record-Route: <sip:217.10.79.23;lr=on;ftag=as7f9cf59e>


FullSIPTrace 11:33:38:357:
Proxy Request Received (UDP): 213.200.94.182:5060<-217.10.79.23:5060
INVITE sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 217.10.79.23:5060;received=217.10.68.6;branch=z9hG4bK46037d33
Via: SIP/2.0/UDP 217.10.66.71:5060;branch=z9hG4bK46037d33;rport=5060
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as6f1f1d8a
Call-ID: 0c39f2652c32397930fe7fc377fc1adc@sipgate.co.uk
CSeq: 102 INVITE
Contact: <sip:anonymous@217.10.66.71>
Max-Forwards: 67
Record-Route: <sip:217.10.79.23;lr=on;ftag=as6f1f1d8a>,<sip:172.20.40.4;lr=on>,<
sip:217.10.79.23;lr=on;ftag=as6f1f1d8a>
Content-Type: application/sdp
Content-Length: 410
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces

v=0
o=root 11504 11504 IN IP4 217.10.66.71
s=session
c=IN IP4 217.10.66.71
t=0 0
m=audio 16484 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

FullSIPTrace 11:33:38:357:
Proxy Request Sent (UDP): 213.200.94.182:5060->77.67.57.195:5060
INVITE sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bKFD7071E3EFEF91A6F7195DBA28B9A
CC74ED9579
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 217.10.79.23:5060;received=217.10.68.6;branch=z9hG4bK46037d33
Via: SIP/2.0/UDP 217.10.66.71:5060;branch=z9hG4bK46037d33;rport=5060
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as6f1f1d8a
Call-ID: 0c39f2652c32397930fe7fc377fc1adc@sipgate.co.uk
CSeq: 102 INVITE
Contact: <sip:anonymous@217.10.79.23:5060>
Max-Forwards: 66
Record-Route: <sip:213.200.94.182:5060;lr>,<sip:217.10.79.23;lr=on;ftag=as6f1f1d
8a>,<sip:172.20.40.4;lr=on>,<sip:217.10.79.23;lr=on;ftag=as6f1f1d8a>
Content-Type: application/sdp
Content-Length: 410
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces

v=0
o=root 11504 11504 IN IP4 217.10.66.71
s=session
c=IN IP4 217.10.66.71
t=0 0
m=audio 16484 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

FullSIPTrace 11:33:38:357:
Request Received (UDP): 77.67.57.195:5060<-213.200.94.182:5060
INVITE sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bKFD7071E3EFEF91A6F7195DBA28B9A
CC74ED9579
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 217.10.79.23:5060;received=217.10.68.6;branch=z9hG4bK46037d33
Via: SIP/2.0/UDP 217.10.66.71:5060;branch=z9hG4bK46037d33;rport=5060
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as6f1f1d8a
Call-ID: 0c39f2652c32397930fe7fc377fc1adc@sipgate.co.uk
CSeq: 102 INVITE
Contact: <sip:anonymous@217.10.79.23:5060>
Max-Forwards: 66
Record-Route: <sip:213.200.94.182:5060;lr>,<sip:217.10.79.23;lr=on;ftag=as6f1f1d
8a>,<sip:172.20.40.4;lr=on>,<sip:217.10.79.23;lr=on;ftag=as6f1f1d8a>
Content-Type: application/sdp
Content-Length: 410
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces

v=0
o=root 11504 11504 IN IP4 217.10.66.71
s=session
c=IN IP4 217.10.66.71
t=0 0
m=audio 16484 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

FullSIPTrace 11:33:38:372:
Request Sent (UDP): 77.67.57.195:5060->194.120.0.198:5060
INVITE sip:iporter@sip.voipcheap.co.uk SIP/2.0
Via: SIP/2.0/UDP 77.67.57.195:5060;branch=z9hG4bK45001261f7b64dadb44e85922cc0ad5
c
To: <sip:iporter@sip.voipcheap.co.uk>
From: <sip:iporter@sip.voipcheap.co.uk>;tag=1294943801
Call-ID: 6bce2d83df87472c92ceb178a3957994
CSeq: 1 INVITE
Contact: <sip:iporter@77.67.57.195:5060>
Max-Forwards: 70
User-Agent: www.sipsorcery.com
Content-Type: application/sdp
Content-Length: 410

v=0
o=root 11504 11504 IN IP4 217.10.66.71
s=session
c=IN IP4 217.10.66.71
t=0 0
m=audio 16484 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

FullSIPTrace 11:33:38:404:
Response Received (UDP): 77.67.57.195:5060<-194.120.0.198:5060
SIP/2.0 400 Bad request
Via: SIP/2.0/UDP 77.67.57.195:5060;branch=z9hG4bK45001261f7b64dadb44e85922cc0ad5
c
To: <sip:iporter@sip.voipcheap.co.uk>
From: <sip:iporter@sip.voipcheap.co.uk>;tag=1294943801
Call-ID: 6bce2d83df87472c92ceb178a3957994
CSeq: 1 INVITE
Contact: <sip:194.120.0.198:5060>
Server: (Very nice Sip Registrar/Proxy Server)
Allow: ACKBYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE


FullSIPTrace 11:33:38:404:
Request Sent (UDP): 77.67.57.195:5060->194.120.0.198:5060
ACK sip:iporter@sip.voipcheap.co.uk SIP/2.0
Via: SIP/2.0/UDP 77.67.57.195:5060;branch=z9hG4bK45001261f7b64dadb44e85922cc0ad5
c
To: <sip:iporter@sip.voipcheap.co.uk>
From: <sip:iporter@sip.voipcheap.co.uk>;tag=1294943801
Call-ID: 6bce2d83df87472c92ceb178a3957994
CSeq: 1 ACK
Max-Forwards: 70


FullSIPTrace 11:33:38:435:
Proxy Request Received (UDP): 213.200.94.182:5060<-217.10.79.23:5060
ACK sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK1f34.d8f749e3.0
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as6f1f1d8a
Call-ID: 0c39f2652c32397930fe7fc377fc1adc@sipgate.co.uk
CSeq: 102 ACK
Max-Forwards: 10
Record-Route: <sip:217.10.79.23;lr=on;ftag=as6f1f1d8a>


FullSIPTrace 11:33:38:435:
Proxy Request Sent (UDP): 213.200.94.182:5060->77.67.57.195:5060
ACK sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bKFD7071E3EFEF91A6F7195DBA28B9A
CC74ED9579
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK1f34.d8f749e3.0
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as6f1f1d8a
Call-ID: 0c39f2652c32397930fe7fc377fc1adc@sipgate.co.uk
CSeq: 102 ACK
Max-Forwards: 9
Record-Route: <sip:217.10.79.23;lr=on;ftag=as6f1f1d8a>


FullSIPTrace 11:33:38:435:
Request Received (UDP): 77.67.57.195:5060<-213.200.94.182:5060
ACK sip:iporter@213.200.94.182;switchtag=193345 SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bKFD7071E3EFEF91A6F7195DBA28B9A
CC74ED9579
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK1f34.d8f749e3.0
Via: SIP/2.0/UDP 172.20.40.4;branch=z9hG4bK1f34.d8f749e3.0
To: <sip:00441642919717@sipgate.co.uk>
From: "anonymous" <sip:anonymous@sipgate.co.uk>;tag=as6f1f1d8a
Call-ID: 0c39f2652c32397930fe7fc377fc1adc@sipgate.co.uk
CSeq: 102 ACK
Max-Forwards: 9
Record-Route: <sip:217.10.79.23;lr=on;ftag=as6f1f1d8a>
Ian

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest