[OpenSIPS-Users] OpenSIPS B2BUA Refer Scenario
bogdan at opensips.org
Fri Nov 1 12:13:25 CET 2013
The XML scenario is correct, also the REFER b2b scenario is know to work
- for sure you have some routing issues in our opensips script.
Do you do any routing in local_routing ? Do you have a pcap I can look
over (send it off list) ?
OpenSIPS Founder and Developer
On 10/31/2013 05:50 PM, Rus Hughes wrote:
> I'm trying to configure OpenSIPS 1.8.2 to handle the REFER scenario
> but when we receive the REFER message, rather than send an INVITE to
> the destination in the Refer-To header, the INVITE flows back up the
> SIP path to the caller. I've attached the OpenSIPS config, the call
> flow and the refer.xml to this mail.
> The platform in question has an OpenSIPS instance listening on port
> 5060 that handles NAT, when this receives a call it then calls a
> second OpenSIPS B2B instance (the one I am having trouble with) that
> listens on port 5080, the OpenSIPS B2B instance then initiates the
> b2b_init_request("refer"); causing it to send an INVITE to itself,
> then it does some load balancing and makes a call to our UAS which
> sends out a REFER telling OpenSIPS B2B to talk to a different UAS.
> OpenSIPS B2B then replies with a 202 and hangs up the leg to our UAS.
> Everything works up until this point. Rather than send an INVITE out
> to the address in the Refer-To header which looks like :
> <sip:+44818118181 at 192.168.46.103
> <mailto:sip%3A%2B44818118181 at 192.168.46.103>;moshxfer=beta_mosh_111111;prefs=1_s6~2_s7~3_h1~4_h2~5_hh~6_s5~7_s8~8_h3~9_..;mode=client;calluid=alphapapa-415f-11e3-9d31-939a1e091c8b;custref=beta;anncset=default;trace=false;suffix=00>
> it sends an INVITE out to the Contact URI of the incoming call.
> If someone could please tell me what I'm doing wrong I'd appreciate it
> as I'm beating my head against the keyboard at the moment :)
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users