< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] repro - no targets for ...


I dug a little deeper and thought I'd try setting the routes for the
extension, that seemed to do the trick and I am able to dial in just fine
now. If anyone else runs into the issue, this is what I used for the route
settings: 

URI: ^sip:([0-9]+)@10\.100\.16\.212
Destination: sip:$1@xxxxxxxxxxxxx

Substituting your own IPs of course.

Thanks,
-ali

-----Original Message-----
From: resiprocate-users-bounces@xxxxxxxxxxxxxxx
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Ali Ziad
Sent: Thursday, November 20, 2008 6:15 PM
To: resiprocate-users@xxxxxxxxxxxxxxx
Subject: [reSIProcate-users] repro - no targets for ...

Hello, 

I've upgraded my install of resiprocate to 1.4 and I am now experiencing a
problem receiving incoming INVITEs with my own client based on resiprocate.
I can dial from my SIP client to another endpoint but not the other way
around.

The error I see in repro is "no targets for sip:202@xxxxxxxxxxxxx:5060 send
480..." and the caller gets a 480.

I tried to trace this in the repro source code and saw that it comes from a
hasTargets() check
Based on three conditions that all turned out to be false.

bool ResponseContext::hasTargets() const
{
        Return (hasCandidateTransactions() |
hasActiveTransactions()|hasTerminatedTransactions() );
}

Is this a new feature requiring a client to register differently ? Is there
a simple answer to this or should I dig further in the source code ? 

Thanks,
-ali

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/