It is already in the CVS but only partially tested.
Jan.
On 16-04 16:43, Mat Harris wrote:
fair enough. ok, any idea how long until ser supports this feature?
On Wed, Apr 16, 2003 at 05:38:44PM +0200, Jan Janak wrote:
If the proxy you mention can put public IP of the NAT int Record-Route and received parameter into Via then it could work, but I am not aware of such a proxy.
Jan.
On 16-04 16:28, Mat Harris wrote:
what about running some sort of sip proxy on the firewalls?
i have seen a few on freshmeat etc, but have no idea yes or no.
On Wed, Apr 16, 2003 at 05:21:32PM +0200, Jan Janak wrote:
OK, there is no addRecordRoute in your config script so you will have to add it in config files of BOTH SIP servers. Simply add addRecordRoute() just before line containing if(!t_relay()) {...
Without addRecordRoute() NOTIFY messages will be send directly from one UA to the other and your firewall will block it.
But it will still not handle responses properly. To do that you will have to put public IP of NAT box into Via and into Record-Route headers and this is currently under development, I recommend you to wait for the next release.
Jan.
On 16-04 15:09, Mat Harris wrote:
On Wed, Apr 16, 2003 at 03:58:37PM +0200, Jan Janak wrote:
Hello,
Do you have record routing enabled ? (You must have rewriteFromRoute() and addRecordRoute() in your script). Please send us as much information as possible (ser configs, ser logs, message dumps etc..)
Jan.
hi, thanks for the quick response, its great of you to help out :)
ok here's a summary of all the probs.
using msn messenger i can connect to the ser server at my house from my home lan. i cannot connect to the server at work nor can i connect from work to my house.
if i use sipsack from the server itself i get
[3:03pm]maiden:~% /usr/local/bin/sipsak-0.8.1/sipsak -T -s \ sip:matthewh@genestate.com warning: IP extract from warning activated to be more informational 0: 10.194.217.5 (0.972 ms) SIP/2.0 483 Too Many Hops 1: 10.194.217.5 (7.596 ms) SIP/2.0 483 Too Many Hops 2: 10.194.217.5 (11.760 ms) SIP/2.0 483 Too Many Hops 3: 10.194.217.5 (18.771 ms) SIP/2.0 483 Too Many Hops 4: 10.194.217.5 (26.441 ms) SIP/2.0 483 Too Many Hops 5: 10.194.217.5 (33.709 ms) SIP/2.0 483 Too Many Hops 6: 10.194.217.5 (53.847 ms) SIP/2.0 483 Too Many Hops 7: 10.194.217.5 (66.244 ms) SIP/2.0 483 Too Many Hops 8: 10.194.217.5 (76.296 ms) SIP/2.0 483 Too Many Hops 9: 10.194.217.5 (87.163 ms) SIP/2.0 483 Too Many Hops
and that goes on forever. it just times out if i do the -vv option.
all the while this is going on, i get messages like these in the message log:
Apr 16 14:33:56 maiden ./ser[2342]: ERROR: get_hdr_field: bad body for <User-Agent>(4194304) Apr 16 14:33:56 maiden ./ser[2342]: ERROR: bad header field Apr 16 14:33:56 maiden ./ser[2342]: ERROR: build_res_buf_from_sip_req: alas, parse_headers failed Apr 16 14:33:56 maiden ./ser[2345]: ERROR: get_hdr_field: bad body for <User-Agent>(4194304) Apr 16 14:33:56 maiden ./ser[2345]: ERROR: bad header field Apr 16 14:33:56 maiden ./ser[2345]: ERROR: build_res_buf_from_sip_req: alas, parse_headers failed Apr 16 14:33:58 maiden ./ser[2343]: ERROR: get_hdr_field: bad body for <User-Agent>(4194304) Apr 16 14:33:58 maiden ./ser[2343]: ERROR: bad header field Apr 16 14:33:58 maiden ./ser[2343]: ERROR: build_res_buf_from_sip_req: alas, parse_headers failed
i have posted my config to my site (http://www.genestate.com/debug/sip/ser.cfg)
i have not taken any special steps as far as firewall routing or anything like that other than forwarding port 5060 as i said previously.
I do not know anything about the config directives you just spoke of so I do not know how to answer you.
i think the beast thing would be for me to start from scratch and do it properly with help from someone who knows more that me as I have probably screwed this attemp :)
thanks again
-- Mat Harris OpenGPG Public Key ID: C37D57D9 mat.harris@genestate.com www.genestate.com
-- Mat Harris OpenGPG Public Key ID: C37D57D9 mat.harris@genestate.com www.genestate.com
-- Mat Harris OpenGPG Public Key ID: C37D57D9 mat.harris@genestate.com www.genestate.com