Hi all,
I am facing a strange problem with a UA I have been working on. While
making an outgoing call the SIP proxy sends me a SIP/2.0 404 Not Found
response with this UA. With X-Lite UA the call goes through.
I have the INVITE message here for both calls -
My UA -
INVITE
Hi Anshuman this is an Issue of Codec
Change the Codec type of your UA.
Regards,
Shardul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anshuman
Rawat
Sent: Wednesday, December 21, 2005 2:30 PM
To: sip-implementors@cs.columbia.edu
Subject:
Hi Shardul,
I am not sure I understand you here. My UA offers codecs 0, 8, 18.
X-Lite offers 0 and 101, and 0 are selected for RTP.
Another thing, I don't think proxy would look at the SDP information. If
the proxy is forwarding the called UA's response, what would a 404
response from a UAC
Anshuman,
I believe the difference in behavior comes from the difference in the INVITE
messages you present:
Your UA:
From: Staka sip:[EMAIL PROTECTED];tag=204320gsl
To: sip:[EMAIL PROTECTED]
X-Lite:
From: 19092661831 sip:[EMAIL PROTECTED]:5061;tag=592405187
To: sip:[EMAIL PROTECTED]
-
Hi *,
RFC 2833- passing DTMF digits thru RTP payload.
When trying to reach an IVR application, where in I select some option by
pressing the required digit.Now when does the digit get passed.Does it get
passed as on when the digit is pressed( early media) or it waits for 200 OK(for
INVITE)
404 would be sent by the UAS and would have been forwarded by the proxy
in between
this would have happened because the user 19494834600 is not configured
in server running @ 216.115.25.198..
just configure this user in this server...and there should not be any
problem of 404 response...
Hi,
As per Sec 25.1, RFC 3261, page 223, Syntax for header parameters in URI
is as follows
headers = ? header *( header )
header = hname = hvalue
hname = 1*( hnv-unreserved / unreserved / escaped )
hvalue = *( hnv-unreserved / unreserved / escaped )
The hvalue may not be present, but = is
Thanks all for your suggestions.
The actual problem was that I had loose routing enabled while the proxy
did not support loose routing. Disabling loose routing at my end solved
the problem.
Regards,
Anshuman S. Rawat
Software Group,
Conexant Systems India Private Ltd.
-Original Message-
Vinod
The digit can pass right afyer 183 also. It doesn't have to wait for 200OK.
There are cases of IVR where the application generates a 183 instead of a
200OK.
Manpreet
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 21, 2005 6:05 AM
Hi,
There exist valid empty headers (e.g. P-Associated-URI, RFC3455) but it is
true that they are rare. 'hname=' could perhaps be interpreted as saying
that the specified header should ~not~ be included in the request, but to my
knowledge this is not currently the case
Regards,
jeroen
-
Hi,
From RFC 3265.
UAC UAS
|-SUBSCRIBE| Request state subscription
|---200| Acknowledge subscription
|--NOTIFY- | Return current state information
|SUBSCRIBE-| Retransmitted state subscription
1) UAC is sending the SUBSCRIBE request
This depends on the UAC implementation as well the availability of the
Remote SDP(SDP of the IVR system).
If the provisional response (180/183 has an answer) for the Offer in Invite
and also if it results in two way communication (send/recv) on both sides
then the user can listen and press/say
Hi,
I would appreciate if someone can comment on the question related to following
callflow
UAS Proxy
---INVITE--
-100--
-180--
-200--
Hi Atul,
No, its not mandatory for UAS to stop responding to reINVITE, rather
it MUST respond to reINVITE; however, the UAS should respond with 487 than
200. You can refer
RFC 3261 Sec 15.1.2
The UAS MUST still respond to any pending requests received for that
dialog. It is
Thanks for your response.
In this case UAS keep sending reINVITE even though it has
replied to BYE message received from Proxy. I would like
to know:
1) whether the Proxy should send ACK or 487 here
2) Isn't the UAS supposed to stop retransmission because
the Session as well as the dialog
Hi,
Inline
Regards,
Manju
-Original Message-
From: Atul Edlabadkar [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 22, 2005 9:59 AM
To: [EMAIL PROTECTED]; sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] Call flow question
Thanks for your response.
In this
Hi,
As per Sec 25.1, RFC 3261, page 223, Syntax for header parameters in URI
is as follows
headers = ? header *( header )
header = hname = hvalue
hname = 1*( hnv-unreserved / unreserved / escaped )
hvalue = *( hnv-unreserved / unreserved / escaped )
The hvalue may not be present, but = is
Hi Jeroen,
Can UAS receive the same SUBSCRIBE request once again after responding to
the SUBSCRIBE? [Over TCP]
What can be the reason if UAS receives the same SUBSCRIBE once again ?
[Over TCP]
1) Transport layer [TCP] level retransmission?
2) Due to some network delay problem?
Regards,
Comments inline...
Thanks Regards,
Nataraju A.B.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of vimal
srivastava
Sent: Thursday, December 22, 2005 12:20 PM
To: sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] Bad Request Handling
Hi
19 matches
Mail list logo
