Hi Brian, There is a misunderstanding from your side in what the b2b scenario documents are concerned ( please read carefully the documentation - http://www.opensips.org/Resources/B2buaTutorial ). The important thing is that there should only be rules in the scenario for requests that need a special handling. In the prepaid scenario - when the BYE from the media server is received the caller must be connected to a human operator, so we have a rule for this. All the other requests need only simple pass forward - so if an ACK is received from one side it only need to be forwarded to the other. 'pass forward' is the implicit action and it will be applied to all requests that don't match a rule.
I see that you say that the prepaid scenario does not work for you. What version are you testing with? Regards, -- Anca Vamanu www.voice-system.ro [email protected] wrote: > Hello list, > > According to the example: > > http://www.opensips.org/Resources/B2buaTutorial#toc13 > > ...implementing the prepaid service should handle INVITE, ACK, and > BYE. Strangely the XML file includes only the BYE scenario: > > <rules> > <request> > <bye> > > I don't know enough about the B2BUA modules to say for sure, but it > would seem that the online example is missing 'ACK' at least. > > When I copy the XML code and config code 1:1, my B2BUA > implementation of the prepaid service sends the initial INVITE, > receives the OK, but as the UAC (caller in the diagram) sends the > ACK the B2B (green line in the diagram) does not pass it onto the > media server. > > Is there a bug in the online XML code for the prepaid scenario? > > Regards, > Brian > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
