News & Reviews
More How-To's & Tips More News
More Reviews Device Configuration Tools
No account yet? Create one
Forgot your Username or Password?

Welcome to the Voxilla VoIP Forum.

Voxilla has been a trusted source for accurate, up-to-date information on the IP Communications industry since 2002. A dedicated staff of reporters and engineers produce feature articles and product reviews to keep industry watchers abreast of the people, companies, and trends driving a fast moving market.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact us.





Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old October 2nd, 2007, 06:05 PM
batlemonade batlemonade is offline
Junior Member
 
Join Date: Sep 2007
Posts: 16
batlemonade is on a distinguished road
Default SPA9000 (with SPA400) Inbound Fax

Hello,

I have a SPA 400 configured with four POTS lines all on Line1 of the SPA9000. I setup a analog fax on FXS2. The fax has been given ext.801.

The problem is that I can send outbound faxes just fine. However, I cannot get an inbound call to route to the fax. I have tried what I have seen written around the forums.

Setting the contact list with |<inbound line # with 1+areacode>:801
Resert FXO_Port_ID_4 to <inbound line # with 1+areacode> on SPA 400

This didn't work.

Please let me know what you think.

Thanks
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old October 2nd, 2007, 06:29 PM
humba3 humba3 is offline
Senior Member
 
Join Date: Jun 2006
Posts: 1,075
humba3 is an unknown quantity at this point
Default Re: SPA9000 (with SPA400) Inbound Fax

The only call routing options you have with FXO ports is send one port to a specific extension.. by using

FXO_Port_ID:extension

So, e.g. if your line 4 is the fax line, the call routing rules on the SPA9k line you use to connect to your SPA400 would need one additional element:

FXO_Port_ID_4:801

(that's assuming the default port identifiers on the SPA400)

You cannot route calls based on the caller, or called number (you don't have that on analog lines).
__________________
There are two essential pieces to tracking down a problem with your VoIP equipment:
  • The configuration of every device involved
  • SIP protocol traces
And don't forget: there's no such thing as giving too much information when describing a problem.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old October 2nd, 2007, 07:16 PM
batlemonade batlemonade is offline
Junior Member
 
Join Date: Sep 2007
Posts: 16
batlemonade is on a distinguished road
Default Re: SPA9000 (with SPA400) Inbound Fax

I did have the line setup as you showed in your post. The difference being that I had changed the name of the port identifier on the SPA400 to the actual POTS line number. That was suggested in another post somewhere. I reset the SPA400 port identifier to the default value and tried again. Again no luck. Below is a copy of the contact list on the Line1 tab of the SPA9000

301,cfwd=aa|FXO_Port_ID_4:801

I have also tried

FXO_Port_ID_4:801|301,cfwd=aa <same result as above>

and

FXO_Port_ID_4:801,301,cfwd=aa <bad idea, but a shot in the dark. Dropped all incoming calls>

Should I be doing this through a usage of hunt groups?
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old October 2nd, 2007, 09:00 PM
humba3 humba3 is offline
Senior Member
 
Join Date: Jun 2006
Posts: 1,075
humba3 is an unknown quantity at this point
Default Re: SPA9000 (with SPA400) Inbound Fax

Well, huntgroups use the same syntax - but you never know.
However, if your second DP dropped all calls, that effectively means your SPA9k doesn't get any calls with that caller id you're looking for. Have you power cycled both units after making the change on the SPA400? Can you attach sip traces (if that doesn't ring a bell.. search for a recent post of mine that explains it all.. I requested a sticky but eric seems to be preoccupied these days) that shows the INVITE from the SPA400?
__________________
There are two essential pieces to tracking down a problem with your VoIP equipment:
  • The configuration of every device involved
  • SIP protocol traces
And don't forget: there's no such thing as giving too much information when describing a problem.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old October 3rd, 2007, 05:50 PM
batlemonade batlemonade is offline
Junior Member
 
Join Date: Sep 2007
Posts: 16
batlemonade is on a distinguished road
Default Re: SPA9000 (with SPA400) Inbound Fax

Hello,

I found the SIP trace info you posted. I'm not fully sure if I've set it up correctly. Attached is the SIP log of me calling in on the POTS line to which I want to set the fax. The main desk answered and I had her transfer me to ext 801 (the fax on FXS2).

I didn't have the contact list setup in the mode that drops calls as we are running with this system currently. I could set it up that way after hours and get you a SIP trace of later.

Let me know if there is any additional information that would be helpful.
(NOTE: the ###.###.2.12 in the SIP trace is the SPA400)

Thanks
Attached Files
File Type: txt Batlemonade SIP Trace.txt (1.8 KB, 4 views)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Old October 3rd, 2007, 05:50 PM
  #6 (permalink)  
Old October 3rd, 2007, 11:33 PM
humba3 humba3 is offline
Senior Member
 
Join Date: Jun 2006
Posts: 1,075
humba3 is an unknown quantity at this point
Default Re: SPA9000 (with SPA400) Inbound Fax

This seems to be the output of debug level set to 0. Can you do the same again with debug level set to 3? I need to see the full messages. For instance, here's how a call is set up between SPA400 and SPA9k:

Code:
pri-->INVITE-->pub
[3]<<192.168.1.7:5060(757)
[3]<<192.168.1.7:5060(757)
INVITE sip:SPA9000@192.168.1.4 SIP/2.0
From: Anonymous<sip:a0000@192.168.1.7>;tag=701a8c0-13c4-3d7b4911-33aa5d-17ce1e8e

To: <sip:FXO_Port_ID_3@192.168.1.7>
Call-ID: 10182da8-701a8c0-13c4-3d7b4911-33aa5d-1d9a2590@192.168.1.7
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.1.7:5060;branch=z9hG4bK-3d7b4911-33aa5d-1fe676af
Max-Forwards: 70
Supported: replaces,timer,100rel
Contact: <sip:FXO_Port_ID_3@192.168.1.7:5060;transport=UDP>
Content-Type: application/SDP
Content-Length: 271

v=0
o=a0002 8645 6672 IN IP4 192.168.1.7
s=SIP Call
c=IN IP4 192.168.1.7
t=0 0
m=audio 10000 RTP/AVP 8 101 0 18
a=fmtp:101 0-15
a=fmtp:18 annexb=yes
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=sendrecv
As you can see, this is an incoming call on FXO port 3, and no caller ID was detected (that's because the SPA400 doesn't support European caller id)
__________________
There are two essential pieces to tracking down a problem with your VoIP equipment:
  • The configuration of every device involved
  • SIP protocol traces
And don't forget: there's no such thing as giving too much information when describing a problem.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old October 4th, 2007, 02:17 PM
batlemonade batlemonade is offline
Junior Member
 
Join Date: Sep 2007
Posts: 16
batlemonade is on a distinguished road
Default Re: SPA9000 (with SPA400) Inbound Fax

Here is the SIP again. I thought that I had set it up correctly. I hope this trace is at debug level 3. It should be set at that point. Hopefully.

This log traces an external call I made in on the POTS line that I wish to use for the fax. I let the aa answer and then dialed extention 302. The extention rang and the went to voicemail.

I then called again and the time answered at the first station in the contact list (EXT 301). I transfered my call to extention (302). This call was routed back to the auto attendent without going to the voicemail on ext302.

Thanks for all your help humba3
Attached Files
File Type: txt Batlemonade SIP Trace2.txt (189.9 KB, 2 views)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old October 4th, 2007, 02:48 PM
batlemonade batlemonade is offline
Junior Member
 
Join Date: Sep 2007
Posts: 16
batlemonade is on a distinguished road
Default Re: SPA9000 (with SPA400) Inbound Fax

Humba3,

The attached SIP trace labeled batlemonade SIP trace2 I think that I might have left too many objects in. So I reran a trace and this time it was run with the debug options set to: full excl. OPT|NTFY|REG

This new trace is attached below.

Thanks Again,
Attached Files
File Type: txt Batlemonade SIP Trace(excld)3.txt (131.5 KB, 3 views)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:



Similar Threads for: SPA9000 (with SPA400) Inbound Fax
Thread Thread Starter Forum Replies Last Post
FAX and SPA9000 gerasimos Linksys (Sipura) VoIP Support Forum 2 August 7th, 2007 07:02 PM
How to redirect fax call to analog extension of the SPA9000 pmoniz Linksys SPA9000/SPA400 Support Forum 5 February 15th, 2007 07:27 PM
SPA9000 and SPA400 registration toddj Linksys SPA9000/SPA400 Support Forum 1 February 10th, 2007 11:01 AM
problems with SPA400 inbound and outbound calls cgbayon Linksys SPA9000/SPA400 Support Forum 3 November 27th, 2006 08:09 PM
FWD, IPKall, and inbound fax kitonne Other Providers 1 January 12th, 2005 07:18 PM



All times are GMT. The time now is 08:17 AM.


vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd. SEO by vBSEO 3.0.0 ©2007, Crawlability, Inc. Logos and trademarks are the property of Voxilla or their respective owner. All other content © 2003-2007 by Voxilla, Inc.