[SIPForum-discussion] should UA accept SIP INVITE destined to a different domain than was initially registered to

Rohan Almeida almeida.rohan at gmail.com
Thu Oct 6 10:34:37 UTC 2011


Hi,

I have observerd such behavior of an UA, altough UA is registered with a
particular name, any INVITE coming to the port it is lintening to is
processed.



regards,
Rohan Almeida
On Thu, Oct 6, 2011 at 2:49 AM, tester voip <tester.voip1 at gmail.com> wrote:

> May reply with 400 Bad Request.
>
>
> On Thu, Oct 6, 2011 at 2:48 AM, tester voip <tester.voip1 at gmail.com>wrote:
>
>> I dont think it'll accept the INVITE.
>>
>>   On Tue, Oct 4, 2011 at 1:55 PM, Keith Lin <iamchiaweilin at gmail.com>wrote:
>>
>>>  Hi everyone,
>>>
>>>
>>> My question is "Should an UA accept SIP INVITE, whose "to header" field
>>> contains a different domain than
>>> the one that this UA initially registered with?"
>>>
>>> Let me use an example to illustrate my question again:
>>>
>>> (1) an UA registered with a proxy say a.com
>>>      let's say this UA has an URI of 111 at a.com
>>>
>>> (2) if this UA receives an INVITE with to header field 111 at b.com
>>> Should it accept this invite?
>>>
>>> because I initially registered with a.com, an incoming request is
>>> destined to b.com
>>> wouldn't there be a security problem if this request is accepted?
>>>
>>> Thank you guys~
>>>
>>>
>>>
>>> _______________________________________________
>>> This is the SIP Forum discussion mailing list
>>> TO UNSUBSCRIBE, or edit your delivery options, please visit
>>> http://sipforum.org/mailman/listinfo/discussion
>>> Post to the list at discussion at sipforum.org
>>>
>>>
>>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20111006/ba6c04f5/attachment-0002.html>


More information about the discussion mailing list