No "sip domain name" field in trunk configuration

[anthonydioulo]

Hello,

A customer' s UC320 throw a "sip 484" error,

Sep 22 16:10:44 UC320W user.debug voice: SIP/2.0 484 Address Incomplete

I think the problem is the lack of the  "sip domain name" field in the  trunk configuration as i can see one here;

https://supportforums.cisco.com/servlet/JiveServlet/showImage/102-15041-40-10
https://supportforums.cisco.com/docs/DOC-15041#UC_320_SIP_Trunk_Configuration

See attached the screenshot of the state of the trun, it misses his domain after the @

The UC320 is upgraded to 2.2.2 .

[anthonydioulo]

Upgraded to 2.2.3 and still no field where to fill the domain name for the  sip trunk.

[janickle]

Hi Anthony,

It looks like some of the SIP information is missing from the configuration of your registration info.  Can you provide additional information on the provider or what device you are trying to register to.

Thank you,

Jason Nickle

[anthonydioulo]

Thanks for youre response.

Yes an information is missing it's the provider's domain name.

So the Uc just never send Register becaus the URI is incomplete; "sip:xxxx@"

A issue is opened on the TAC the tech had no succes triyng to register the trunk by abou 1 hour so it' s not a configuration mistake.

I will post the results of the TAC they actually makes test they call me back soon.

[janickle]

Sounds Good.  Im sure the TAC will be able to help resolve this issue for you. 

Jason Nickle

[anthonydioulo]

Hope so my customer is upset cause he can' t phone since wednesday now !

I make a bet they will find that the unit is in defect ... wait and see

[anthonydioulo]

At this poin TAC did not resolve the case.

They say the problem is from the provider and of course the provider say they are  100% sip RFCxxxx and the problem is the UC.

As i can see i can succesfult register with Xlite or a SnomONE PBX on my provider trunk.

But i also can register my UC320 on another provider ...

[Christopher Edgeworth]

Hi Anthony,

To understand what is happening here we will need the request and the response.  Can you please provide the SBSC case number so we can look at the messaging?

Thanks,

Chris

[anthonydioulo]

The case number is; 623254153

This is what the provider can see, (they say they cant handle "notify" requests);

U 2012/09/21 14:18:28.183877 IP.IP.IP.IP:5060 -> ip.ip.ip.ip:5060

NOTIFY sip:sip.myprovider.net SIP/2.0.

Via: SIP/2.0/UDP IP.IP.IP.IP:5060;branch=z9hG4bK-d56a8b2a.

From: "NIT" <>MYSIPID@sip.myprovider.net>;tag=d78ae5c25878b8eco5.

To: .

Call-ID: 2726181a-1c436a74@IP.IP.IP.IP.

CSeq: 211 NOTIFY.

Max-Forwards: 70.

Contact: "NIT" <>MYSIPID@IP.IP.IP.IP:5060;ref=MYSIPID>.

Event: keep-alive.

User-Agent: Cisco/UC320W-2.2.2(1).

Allow-Events: talk, hold, conference, x-spa-cti.

Content-Length: 0.

.

U 2012/09/21 14:18:28.184243 ip.ip.ip.ip:5060 -> IP.IP.IP.IP:5060

SIP/2.0 484 Address Incomplete.

Via: SIP/2.0/UDP IP.IP.IP.IP:5060;branch=z9hG4bK-d56a8b2a.

From: "NIT" <>MYSIPID@sip.myprovider.net>;tag=d78ae5c25878b8eco5.

To: ;tag=696c4aa18cbb1138a6b8a116e3582f18.6a97.

Call-ID: 2726181a-1c436a74@IP.IP.IP.IP.

CSeq: 211 NOTIFY.

Server: Alphalink SIP Proxy 2.0.

Content-Length: 0.

[Christopher Edgeworth]

Hi Anthony,

The REGISTER method is what we are interested in.  While the SIP provider may not support the NOTIFY message, I suspect your system is configured for NAT keep alive and is sending the SIP Notify.  The UC320W sending notfiy is ok.

What I do see in the messaging is the TO: field doesn't look correct. 

To:    should be in the format:  

To: <>user@sip.myprovider.net>       Where user is the account username.  This is typically a phone number, but could be an alpha numeric username. 

Make sure you have configured a username on the SIP/BRI page.

Chris

[anthonydioulo]

Thx for explanation on notify, the UC320 never throw REGISTER requests,i saw the problem on the to

(thx to confirm it' s not normal)   but i have configured a name on the SIP page it's could be the cause of the 484 error.

So it' s a "no user name" error?