SIPSwitch Troubleshooting

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

Post by Aaron » Thu Sep 11, 2008 1:07 pm

Hi Ian,

That's perfect, with a SIP trace we have something to work from rather than having to go back and forwards.

Your call from sipgate is going through to voipcheap and there it is getting rejected with a response of 400 Bad Request. I checked a call to voipcheap (this time I just used my voipstunt details instead of signing up for yet another Betamax account and they worked which was great) and the call got through fine. This means that there is no SIP interoperability issue between voipcheap and mss.

I suspect your problem is that the "number" you are trying to dial at voipcheap is iporter, i.e. sip:iporter@sip.voipcheap.co.uk. That doesn't look right to me. Are you trying to forward your call to a PSTN number through voipcheap? If so your dialplan command should be of the form.

Code: Select all

sys.Dial("004412345678@voipcheap")
Regards,

Aaron

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

Post by iporter » Thu Sep 11, 2008 2:16 pm

Aaron,

Many thanks for your speedy reply.

sip:iporter@voicheap.co.uk is my SIP address for my voipcheap account. I do have a DID associated with my voipcheap account but I don't want to 'hop' onto the PSTN as that will involve a charged call from Sipgate.

Interestingly I am forwarding my USA DID (Ipkall) to sip:iporter@voipcheap.co.uk

Any other ideas?
Ian

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

Post by Aaron » Thu Sep 11, 2008 2:32 pm

Hi Ian,

Maybe the server wants it as @voipcheap.co.uk instead of sip.voipcheap.co.uk? You could try tweaking that in your provider setitngs.

Regards,

Aaron

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

Post by iporter » Thu Sep 11, 2008 2:32 pm

Success! I used the info you provided in your last post to give me the hint.

The answer lay in the user name which indeed I had only set to iporter in the user name field. It should have been sip:username@voipcheap.co.uk

It's working now.

Thanks (I'll be back for more help on outbound dial plans!).
Ian

justhisonce
Posts: 6
Joined: Sat Jan 17, 2009 12:05 pm

Post by justhisonce » Sat Jan 17, 2009 4:17 pm

I have followed these instructions carefully and am not getting any results back.

Here is what is on my screen:
username=> justthisonce
password=> *****************
welcome justthisonce

filter=> event full
filter=ipaddress=*, user=*, event=full, request=*, serveripaddress=*, server=*, regex=:justthisonce@.
Nothing changes after this.

I was hoping to see what happens when MySIPSwitch tries to register to voipmk.my-home-phone.com as registration timed out.

Is there any way of seeing the registration details?

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

Post by Aaron » Sun Jan 18, 2009 8:12 am

We'd turned off log messages from the SIP Proxy as they were pretty verbose. However a few times they have been required including yours so I've turned them back on. See if you get anything now.

Regards,

Aaron

justhisonce
Posts: 6
Joined: Sat Jan 17, 2009 12:05 pm

Post by justhisonce » Sun Jan 18, 2009 8:17 am

Thanks for the reply!

I again didn't see anything other than that described previously.

I did notice the format of what was returned after entering "event full" change. Was this expected?
OLD
filter=> event full
filter=ipaddress=*, user=*, event=full, request=*, serveripaddress=*, server=*, regex=:justthisonce@.

NEW
filter=> event full
filter=ipaddress=*, user=justthisonce, event=full, request=*, serveripaddress=*, server=*, regex=.*.
Hmm, it's now back to the original (or "old") format.

Update: Now I'm seeing something. Let me capture and I'll post back here soon.

justhisonce
Posts: 6
Joined: Sat Jan 17, 2009 12:05 pm

Post by justhisonce » Sun Jan 18, 2009 8:36 am

OK, here it is.
FullSIPTrace 08:29:36:994:
Proxy Request Received (UDP): 213.200.94.182:5060<-213.200.94.182:5004
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5004;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
Route: <sip:93.95.65.5:5060;lr>
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:37:009:
Proxy Request Sent (UDP): 213.200.94.182:5060->93.95.65.5:5060
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:37:728:
Proxy Request Received (UDP): 213.200.94.182:5060<-213.200.94.182:5004
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5004;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
Route: <sip:93.95.65.5:5060;lr>
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:37:728:
Proxy Request Sent (UDP): 213.200.94.182:5060->93.95.65.5:5060
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:39:228:
Proxy Request Received (UDP): 213.200.94.182:5060<-213.200.94.182:5004
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5004;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
Route: <sip:93.95.65.5:5060;lr>
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:39:228:
Proxy Request Sent (UDP): 213.200.94.182:5060->93.95.65.5:5060
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:46:227:
Proxy Request Received (UDP): 213.200.94.182:5060<-213.200.94.182:5004
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5004;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
Route: <sip:93.95.65.5:5060;lr>
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:46:227:
Proxy Request Sent (UDP): 213.200.94.182:5060->93.95.65.5:5060
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:54:726:
Proxy Request Received (UDP): 213.200.94.182:5060<-213.200.94.182:5004
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5004;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
Route: <sip:93.95.65.5:5060;lr>
User-Agent: www.mysipswitch.com
Expires: 3600


FullSIPTrace 08:29:54:726:
Proxy Request Sent (UDP): 213.200.94.182:5060->93.95.65.5:5060
REGISTER sip:voipmk.my-home-phone.com SIP/2.0
Via: SIP/2.0/UDP 213.200.94.182:5060;branch=z9hG4bK7ff65c5f3692481bb9bd710c68dce9d1
To: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>
From: <sip:XXXXXXXXXX@voipmk.my-home-phone.com>;tag=1363849918
Call-ID: 9f969b99-eaa6-4a52-aee2-8e92b080adff
CSeq: 198 REGISTER
Contact: <sip:justthisonce@sip.mysipswitch.com;switchtag=117209>
Max-Forwards: 70
User-Agent: www.mysipswitch.com
Expires: 3600
Can any of you SIP experts decipher that and tell me what is causing this timeout?

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

Post by Aaron » Sun Jan 18, 2009 10:54 am

Hi justhisonce,

It's not really possible to sya what's causing the timeout as all the trace shows is that the requests are being sent out to 93.95.65.5:5060 but no response is ever received.

It looks like that address could be a service you are running on your own network so it would be worth checking your firewall and NAT port forwarding rules to make sure the request will be allowed in.

Regards,

Aaron

justhisonce
Posts: 6
Joined: Sat Jan 17, 2009 12:05 pm

Post by justhisonce » Sun Jan 18, 2009 11:17 am

Thanks Aaron.

I can assure you that service is not running on my own network. It's running on that of MyHomePhone which I've paid to connect to.

I can ask them to look at why they are not accepting these requests, but to sniff their network they'll need your SIP server's IP address. I'm guessing this is 213.200.94.182. Is that correct?

This is incredibly frustrating - but certainly no fault of MySIPSwitch.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest