outbound proxy

New features you'd like see on SIP Sorcery
Martin
Posts: 6
Joined: Mon Jul 16, 2007 4:38 am

Post by Martin » Mon Sep 03, 2007 12:55 pm

Aaron wrote:
nederfox wrote:
; Example extensions
exten = 100,1,Switch(anon,,303@sip.blueface.ie)
exten = 101,1,Switch(anon,,612@fwd.pulver.com)
Hi nederfox,

The above dialpan won't work as the 100 extension does not exist for Blueface and I'm pretty sure 101 does not exist for FreeWorldDialup either.
Hi Aaron,
I think the above (100&101) should work alright as 100 is the number sent to Mysipswitch and 303 is sent on to blueface from the sipswitch (which should be valid).
I think nederfox's problems might be related to something else.
Martin

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Post by Aaron » Mon Sep 03, 2007 1:24 pm

Hi Martin,

You're correct, my mistake. I must have missed looking at the forwarded number.

Regards,

Aaron

nederfox
Posts: 5
Joined: Sun Aug 26, 2007 11:13 am

Post by nederfox » Mon Sep 03, 2007 8:26 pm

Today I got more close to a possible solution: tried to register and make a call through mysipswitch with Ekiga softphone on Centos linux: no problems, calling works as expected!

After that i tried to call with xlite on a windoze box in the same subnet, and all calls fail: 404 notfound.

Thus, the dialplan at mysipswitch should be correct, and the problem possibly has something to do with internal ip address or something. "Monitor" shows another possible clue:

Code: Select all

Trying Xlite or Sipura ATA:

15:53:48:672: Dialplan load and compilation time 78.125ms.
15:54:03:706: Destination sip:@sip.mysipswitch.com not found in dial plan.
15:55:44:320: Destination sip:@sip.mysipswitch.com not found in dial plan.
15:57:45:072: Destination sip:@sip.mysipswitch.com not found in dial plan.


Trying Ekiga:

16:14:41:322: Dialplan load and compilation time 78.125ms.
16:14:41:480: Switching sip:101@sip.mysipswitch.com:5060->sip:612@fwd.pulver.com:5060 via fwd.pulver.com.
16:14:44:555: Response OK from fwd.pulver.com.
16:14:57:183: Switching sip:100@sip.mysipswitch.com:5060->sip:303@sip.blueface.ie:5060 via sip.blueface.ie.
16:15:00:195: Response OK from sip.blueface.ie.
16:15:34:879: Destination sip:0031725618441@sip.mysipswitch.com not found in dial plan.
16:16:20:763: Switching sip:*10031725616438@sip.mysipswitch.com:5060->sip:0031725616438@sip1.voipbuster.com:5060 via sip1.voipbuster.com.
16:16:20:842: Response Unauthorized from sip1.voipbuster.com.
16:16:29:215: Response Ok from sip1.voipbuster.com.

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Post by Aaron » Mon Sep 03, 2007 10:41 pm

Hi nederfox,

From that info it looks like your xten is sending an empty call destination:

15:54:03:706: Destination sip:@sip.mysipswitch.com not found in dial plan.

sip:@sip.mysipswitch.com is not right, there should always be something in between the : and the @ as it represents the number you are trying to call.

sip:100@sip.mysipswitch.com is a valid example.

Try opening the xten and pressing the space bar. It switches the inout mode on the xten between numeric and alphabetic. It could be that you're in alphabetic and attmepting to enter a number. Of course it could be something else entirely including a bug although the xten is the main SIP device I use with the sipswitch so I don't believe there is a SIP issue between them.

Hth,

Aaron

nederfox
Posts: 5
Joined: Sun Aug 26, 2007 11:13 am

Post by nederfox » Sat Sep 08, 2007 8:44 am

I'm giving up. The space bar does not solve the puzzle.
My Ekiga client is able to call with mysipswitch, Xlite (1103a, build13985) and ATA aren't. Therefore, the dialplan should be correct.
Past days I spent some time studying the logs of both clients, seeing no real clue. Maybe the old Xlite version creates some problem, although this will not solve the ATA connection problems.

Aaron and Martin, if you would like to receive the diagnostic logs, pls let me know. I'd like to thank you for the support anyway!

pablo
Posts: 54
Joined: Thu Jul 12, 2007 11:01 pm

Post by pablo » Sat Sep 08, 2007 10:50 pm

Since the sipswitch dial plan is working with Ekiga, perhaps there is some dial plan entry in XLite or in the ATA that is not passing the proper dialing sequence to the sipswitch account. Just a thought .........

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Post by Aaron » Mon Sep 10, 2007 7:06 am

nederfox wrote:I'm giving up. The space bar does not solve the puzzle.
My Ekiga client is able to call with mysipswitch, Xlite (1103a, build13985) and ATA aren't. Therefore, the dialplan should be correct.
Past days I spent some time studying the logs of both clients, seeing no real clue. Maybe the old Xlite version creates some problem, although this will not solve the ATA connection problems.

Aaron and Martin, if you would like to receive the diagnostic logs, pls let me know. I'd like to thank you for the support anyway!
Hi nederfox,

I've never encountered a problem with the xlite softphone or Bria when using them with the sipswitch. Just to double check I've downloaded the latest version of the xlite softphone (verson 3.0 build 41150) and am able to make calls correctly.

If you send me or post up the diagnostic logs I will certainly have a look.

Regards,

Aaron

Post Reply