-------- Original Message --------
Subject: 	Re: asterisk <--> zap
Date: 	Sun, 05 Feb 2006 21:41:38 +0000
From: 	Alex Fritze <alex(at)croczilla.com>
To: 	jan(at)henkins.za.net
References: 	<43E0AB24.1070904(at)croczilla.com> 
<1139171034.10778.16.camel(at)localhost>



Hi Jan,

First of all: Would you mind if we continue these discussions on the 
zap-devel mailinglist (http://www.croczilla.com/lists/zap-devel),
so 
that other people can benefit from your testing insights? Mind if I 
forward this email to the list as a starting point?


Jan Henkins wrote:
[...]
Great!
[...]
When you say the old registration confuses zap, how does that manifest 
itself? In theory zap should just pick up the zombie registration again, 
or if e.g. the outbound port has changed for some reason, it should 
create a new registration alongside the old registration. Either way 
everything should work fine... calls should still be routed correctly 
etc. Is that not the case for you?

I know that the zap doesn't shutdown cleanly at the moment. I'll have to 
fix this at some point. Old registrations shouldn't be a problem though 
- after all a registration might be zombied for other reasons 
(disconnecting from the network; laptop sleeping, etc.).
[...][...][...][...][...][...][...]
Yes, Route 1 should look something like this:

<sip:myAsteriskServer.mydomain.com;lr>

(In my earlier mail this got swallowed somehow, because of some html 
'<'/'>' translation.)

The 'lr' stands for 'loose router': a proxy that complies with the 'new' 
SIP standard (RFC3261).
[...]
Damn. Ok, I better fix it then :-)
[...]
works...

[...]
Thanks a lot!
Alex