Hi,
I have two proxies. One is Communigate Pro and another is Openser. Both
handle calls fine independently of each other. So if UA1 and UA2 are
registered to the same proxy, calls work fine. I need to call from UA1
registered to communigate pro proxy to UA2 registered to Openser. How can I
achiev
> UA1 is registered to proxy 1 and UA2 is registered to proxy 2, I need to
> make a call from UA1 to UA2. Proxy 1 and Proxy 2 are in the same LAN but
> they do not know of each other. Then when UA1 dials the number of UA2, the
> proxy 1 is currently rejecting the call with 480-No address found. Ho
Hi all,
We have two proxies.. Both are working fine independently..all the UAs can
register to each proxy and am able to make calls among the UAs registered to
the same proxy. I now need to test a situation like the one below:
UA1--->Proxy1Proxy2<-
From: "Amit P. Ahuja" <[EMAIL PROTECTED]>
Considering the behavior of UAS-2, my question is: whether any SIP
standard suggests guidelines on whether it is advisable to send out
responses from a UDP port which is different from the one on which
the request was received? RFC 3261 - 18
Because a brandname IP PBX that we are integrating our product (which involves
flow based decisions, much like a port restricted cone NAT) with behaves this
way. Could you please point me to the guideline in the SIP standards that
suggests against this.
Thanks and Regards,
Amit
- Original
It was certainly my intention, when writing the CPL RFC, that
should match whenever any previous condition did not -- i.e., it would be
the equivalent of a default: rule in a C switch statement. In a switch rule
with an output, the processor's default action should never be
invoked.
In other wo
see comments inline
>
>Hi All,
>
>I have few queries about Session Timer mechanism (RFC 4028), please
> clarify it.
>Thanks in advance.
>
> 1) If in the initial session establishment (INVITE 200 OK ACK), there
> was no session timer info got exchanged and both the end
> 2) If support for Session Timer (ST) is not enabled at User Agent (UA) and
> User Agent (UA) sends INVITE with Support header with value as 'timer' to
> other end point.
> And end point responds with 2xx response with Require header with value
> 'timer'.
>
This is faulty implementation. Why
Hi All,
I have few queries about Session Timer mechanism (RFC 4028), please clarify
it.
Thanks in advance.
1) If in the initial session establishment (INVITE 200 OK ACK), there was
no session timer info got exchanged and both the end points (User Agents)
supports Session
