| < Previous by Date | Date Index | Next by Date > |
| Thread Index | Next in Thread > |
|
We have a problem with reSIProcate when operating as a B2BUA
between UACs and a proxy IP PBX such as SipX. The scenario is: The standard INVITE call flow is from (1) UAC1 ->
(2) B2BUA -> (3) SipX -> (4) B2BUA -> (5) UAC2 Our B2BUA is registrar for UAC1 and UAC2, and the B2BUA also
registers to SipX with the ids of UAC1 and UAC2. SipX therefore believes both
UAC1 and UAC2 are at the B2BUA … There is only one B2BUA, (2) and (4)
represent flows through the B2BUA. This works ok for a normal call. However if at step 4, the
INVITE from SIPX to B2BUA is rejected with a 302 to redirect the call to UAC3
(also registered through our B2BUA) , SipX then sends another INVITE to the
B2BUA with an updated URI for UAC3 but with the To & From headers
unchanged. reSIProcate then returns an error 482 request merged to SipX
… there was some commented out code in MergedRequestKey which
appeared to check for a change in the request URI but adding this check again
did not resolve the issue, 482 was still returned. We are wondering whether the problem is caused because we
haven’t cancelled stage (5) before returning the 302 to SipX … Any ideas as to why this happens? I have an ethereal
trace available if that helps! Steve
Coule Envox Worldwide Envox
Worldwide – A Global Leader in Voice
Solutions |