I'm not suggesting that t_next_contacts deviates from the README. I'm
looking for its specific use case when combined with the outbound module.
At the very least, the example registrar configuration here:
http://www.kamailio.org/docs/modules/4.4.x/modules/outbound.html is
incomplete, in that it
Colin Morelli writes:
> When there's one registration binding in the locations table,
> t_load_contacts doesn't seem to do anything and as a result
> t_next_contacts fails.
t_next_contacts() does work as specified in README:
Function returns 1 if contacts_avp was not empty and a destination
Juha,
I changed the message between when I copied the code and the logs. Those
lines are the lines that produce the error message.
As I mentioned in the original message - I'm aware that there's only one
branch in the set. That is the case that this doesn't work. When there's
one registration
Colin Morelli writes:
> 8(27) DEBUG: tm [t_serial.c:191]: t_load_contacts(): nr_branches is 0
> 8(27) DEBUG: tm [t_serial.c:194]: t_load_contacts(): nothing to do - only
> one contact!
> 8(27) DEBUG: tm [t_serial.c:455]: t_next_contacts(): no contacts in
> contacts_avp - we are done!
> 8(27)
Hey all,
I've got two layers of Kamailio proxies running. One set of edge proxies
that are parking outbound connections and doing load balancing to a set of
registrar/proxies. This is working well with one exception:
I can't seem to get t_load_contacts/t_next_contacts working correctly for
On 4/29/11 8:45 PM, Iñaki Baz Castillo wrote:
2011/4/29 Juha Heinanenj...@tutpro.com:
Yes. I know that the IETF produces lot of garbage, but RFC 5626
(Managing Client-Initiated Connections) is a good stuff (and needed,
specially in SIP scenarios which mobile clients).
the rfc looks ok, but
Iñaki Baz Castillo writes:
By use of SIP outbound and re-registration using the same reg-id the
proxy would be able to replace the old registration with the new
registration. Further, if Kamailio would have a mapping from
registrations to TCP connections it could also close the dead TCP
2011/4/29 Juha Heinanen j...@tutpro.com:
Yes. I know that the IETF produces lot of garbage, but RFC 5626
(Managing Client-Initiated Connections) is a good stuff (and needed,
specially in SIP scenarios which mobile clients).
the rfc looks ok, but are there any sip UAs that could be used in
Hi!
IIRC we recently had a discussion about SIP outbound [1] and the
benefits of an implementation in Kamailio. Just playing around with a
SIP client on an iphone I discovered a usecase. Whenever the iphone gets
a new IP address (quite often as it often changes between WiFi and 3G)
the client
2011/4/28 Klaus Darilion klaus.mailingli...@pernau.at:
IIRC we recently had a discussion about SIP outbound [1] and the
benefits of an implementation in Kamailio. Just playing around with a
SIP client on an iphone I discovered a usecase. Whenever the iphone gets
a new IP address (quite often
10 matches
Mail list logo
