link did number -->pbxes.org-->voipcheap-->UM mobile

Grampa · 25-10-2007, 21:15

bbob, thanks for all your suggestions, but I still cannot get this to work with PBXes. I have confirmed that each leg of the connection is working:

I can dial my IPKall number from any phone, and it rings in to my FWD account using the FWD softphone. Audio is fine.

I can dial in and talk from my FWD softphone to my VoipCheap softphone using my VoipCheap SIP address.

I can dial out and talk from my VoipCheap softphone to any phone, including my UM+ number.

However, when I try to do this through PBXes, I get a busy signal. This happens even when the extension is my home PSTN number or my home VoIP number.

My PBXes configuration is as follows:

Classical extension 100 is my home PSTN number (for testing); all other fields are the defaults.

Ring group 1 uses extension 100. Ring strategy is ringall, ring time is 60. All other fields are the defaults.

Two SIP trunks: FWD and VoipCheap. The General Settings for both are the defaults. Account information is correct (username, password, sip server), as indictated by the Status page, which has grayed icons when the information is incorrect. The FWD trunk registers for both inbound and outbound calls, the VoipCheap trunk is also set for both inbound and outbound, although I have tried it both ways. No dial rules or other optional settings for either trunk.

The Inbound Route uses the FWD trunk, with the Destination Ring Group #1. All other fields are the defaults.

Outbound Route 0 has the name Outbound, Dial Pattern XX, Trunk Sequence SIP/VoipCheap. All other fields are the defaults.

All other settings are the defaults.

I've tried variations on this configuration, but usually I just get a busy signal. On the inbound route, you can set the destination as an extension, a ring group, or Callthru. I've tried all of them. I believe I got a dial tone rather than a busy signal when I used Callthru, but I couldn't dial anything from that dial tone. On the Incoming Route page, you need to enter the name of the trunk rather than select it from a drop-down list, so it's possible I didn't identify it properly. However, I also tried the FWD username in identifying the trunk, and that didn't work either. On the Trunk page for FWD, it says that the trunk is not used by any routes. However, since that statement appears to refer to OUTBOUND routes, I didn't think it was a problem.

The best hint about what is going wrong is probably on the Call Monitor page. The incoming call is usually correctly identified. Depending on the configuration, the destination might be identified as "s" (whatever that means), or 1 (for Ring Group 1), or 100 (for Extension 100), or it might give the number of the extension. The only trunk that is identified in that log is fwd.pulver.com. I do not see sip.voipcheap.com anywhere on the log, even though PBXes appears to be registering properly -- the Status page shows the trunk as lit, and if I put in an incorrect password, it goes gray.

I've done a lot of troubleshooting, but at this point I'm stumped. Any advice would be appreciated.

	(#13)
Grampa (Offline) Member Advanced Member Posts: 97 Join Date: 01 Oct 2007 Country:	25-10-2007, 21:15 bbob, thanks for all your suggestions, but I still cannot get this to work with PBXes. I have confirmed that each leg of the connection is working: I can dial my IPKall number from any phone, and it rings in to my FWD account using the FWD softphone. Audio is fine. I can dial in and talk from my FWD softphone to my VoipCheap softphone using my VoipCheap SIP address. I can dial out and talk from my VoipCheap softphone to any phone, including my UM+ number. However, when I try to do this through PBXes, I get a busy signal. This happens even when the extension is my home PSTN number or my home VoIP number. My PBXes configuration is as follows: Classical extension 100 is my home PSTN number (for testing); all other fields are the defaults. Ring group 1 uses extension 100. Ring strategy is ringall, ring time is 60. All other fields are the defaults. Two SIP trunks: FWD and VoipCheap. The General Settings for both are the defaults. Account information is correct (username, password, sip server), as indictated by the Status page, which has grayed icons when the information is incorrect. The FWD trunk registers for both inbound and outbound calls, the VoipCheap trunk is also set for both inbound and outbound, although I have tried it both ways. No dial rules or other optional settings for either trunk. The Inbound Route uses the FWD trunk, with the Destination Ring Group #1. All other fields are the defaults. Outbound Route 0 has the name Outbound, Dial Pattern XX, Trunk Sequence SIP/VoipCheap. All other fields are the defaults. All other settings are the defaults. I've tried variations on this configuration, but usually I just get a busy signal. On the inbound route, you can set the destination as an extension, a ring group, or Callthru. I've tried all of them. I believe I got a dial tone rather than a busy signal when I used Callthru, but I couldn't dial anything from that dial tone. On the Incoming Route page, you need to enter the name of the trunk rather than select it from a drop-down list, so it's possible I didn't identify it properly. However, I also tried the FWD username in identifying the trunk, and that didn't work either. On the Trunk page for FWD, it says that the trunk is not used by any routes. However, since that statement appears to refer to OUTBOUND routes, I didn't think it was a problem. The best hint about what is going wrong is probably on the Call Monitor page. The incoming call is usually correctly identified. Depending on the configuration, the destination might be identified as "s" (whatever that means), or 1 (for Ring Group 1), or 100 (for Extension 100), or it might give the number of the extension. The only trunk that is identified in that log is fwd.pulver.com. I do not see sip.voipcheap.com anywhere on the log, even though PBXes appears to be registering properly -- the Status page shows the trunk as lit, and if I put in an incorrect password, it goes gray. I've done a lot of troubleshooting, but at this point I'm stumped. Any advice would be appreciated.