[OpenSIPS-Users] Problem with prefix() during call forwarding
Bogdan-Andrei Iancu
bogdan at voice-system.ro
Wed Dec 9 18:17:34 CET 2009
Hi Andrew,
Just to refresh me - what is the failure that trigger the failure_route?
a timeout on the ongoing branch?
I can take a look in TM to see how difficult will be to revert the
CANCEL and the INVITE, but I was not sure about the failure scenario you
had (to investigate).
Regards,
Bogdan
Andrew Pogrebennyk wrote:
> Bogdan,
>
> Thanks. I'm using 1.5.3. I sort of got stuck with this serial forking
> scenario. I mean, OpenSIPS does what is supposed to do. The problems is
> the call needs to be sent to (and is originated by) the Cisco AS5300.
> When one destination fails OpenSIPS sends the call to the next
> destination, but since new INVITE is part of the same dialog for
> OpenSIPS is carries the same Call-ID and From tag the Cisco gets
> confused and sends 482 Loop Detected or 500 Internal Server Error.
> Perhaps delaying new INVITE by a few ms for the Cisco to invalidate the
> call state would have helped, but I can't find my way around this.
>
> Regards,
> Andrew
>
> Bogdan-Andrei Iancu wrote:
>
>> Hi Andrew,
>>
>> Noticed you fixed the problem, but here are some ideas/questions:
>>
>> 1) what version on opensips do you use?
>>
>> 2) keep in mind that all the changes you do before creating the
>> transaction (which is typically done by the first t_relay()) are
>> inherited by all the following branched (you create via failure route).
>> If you want to do changes to affect only a specific branch, you should
>> use the onbranch route (see
>> http://www.opensips.org/Resources/DocsCoreRoutes#toc2)
>>
>> Regards,
>> Bogdan
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
--
Bogdan-Andrei Iancu
www.voice-system.ro
More information about the Users
mailing list