Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

B179 not registering at all

Status
Not open for further replies.

BlackCuervo

Technical User
May 20, 2002
64
0
6
MX
Hi everybody!

I have this issue. We have an AVAYA AURA 6.0 COMMUNICATION MANAGER. There are many stations using a B179 SIP Conference working just fine. I need to add another station, but the B179 is simply not registering. But the weirdest thing is that, if I set up a profile of an existing and working station, it gets registered.

B179 is being programmed as DN 7439. It exists as an endpoint (Elements) and as a user. When the B179 is being restarted, it doesn't get registered.

LOG as DN 7439

Feb 11 09:06:30: Requesting restart
Feb 11 09:06:30: INF: ctl: Exit request
Feb 11 09:06:30: INF: mmi: Exit request
Feb 11 09:06:31: INF: sip_manager: Shutting down the SIP stack
Feb 11 09:06:31: INF: Unregistration sent
Feb 11 09:06:31: INF: <sip:5251@172.31.128.19;transport=tcp>: unregistration success
Feb 11 09:06:32: INF: main: exit 1
Feb 11 09:06:32: Need Restart
Feb 11 09:06:36: INF: sip_manager: ua_cfg.nameserver_count = 2
Feb 11 09:06:36: INF: sip_manager: ua_cfg.nameserver[0] = 127.0.0.1
Feb 11 09:06:36: INF: sip_manager: ua_cfg.nameserver[1] = 127.0.0.1
Feb 11 09:06:36: INF: sip_manager: ua_cfg.outbound_proxy_cnt = 0
Feb 11 09:06:36: INF: pjsua version 1.0-trunk for arm-926-linux-gnu initialized
Feb 11 09:06:37: WAR: Failed to send Request msg REGISTER/cseq=54225 (tdta0x328968)! err=120099 (Cannot assign requested address)
Feb 11 09:06:37: WAR: SIP registration failed, status=503 (Service Unavailable)
Feb 11 09:06:37: ERR: Unable to create/send REGISTER: Cannot assign requested address [status=120099]
Feb 11 09:06:37: INF: sip_manager: Setting codec G722, prio 4
Feb 11 09:06:37: INF: sip_manager: Setting codec PCMA, prio 3
Feb 11 09:06:37: INF: sip_manager: Setting codec PCMU, prio 2
Feb 11 09:06:37: INF: sip_manager: Setting codec G729, prio 1

Then, I simply change the Account Name from 7439 to 5251 (DN 5251 is a previously working B179) and it gets registered!

Feb 11 09:07:42: Requesting restart
Feb 11 09:07:42: INF: ctl: Exit request
Feb 11 09:07:42: INF: mmi: Exit request
Feb 11 09:07:42: INF: sip_manager: Shutting down the SIP stack
Feb 11 09:07:43: INF: main: exit 1
Feb 11 09:07:44: Need Restart
Feb 11 09:07:48: INF: sip_manager: ua_cfg.nameserver_count = 2
Feb 11 09:07:48: INF: sip_manager: ua_cfg.nameserver[0] = 127.0.0.1
Feb 11 09:07:48: INF: sip_manager: ua_cfg.nameserver[1] = 127.0.0.1
Feb 11 09:07:48: INF: sip_manager: ua_cfg.outbound_proxy_cnt = 0
Feb 11 09:07:48: INF: pjsua version 1.0-trunk for arm-926-linux-gnu initialized
Feb 11 09:07:48: INF: Registration sent
Feb 11 09:07:48: INF: sip_manager: Setting codec G722, prio 4
Feb 11 09:07:48: INF: sip_manager: Setting codec PCMA, prio 3
Feb 11 09:07:48: INF: sip_manager: Setting codec PCMU, prio 2
Feb 11 09:07:48: INF: sip_manager: Setting codec G729, prio 1
Feb 11 09:07:49: INF: <sip:5251@172.31.128.19;transport=tcp>: registration success, status=200 (OK), will re-register in 61 seconds
Feb 11 09:07:51: INF: mmi: Account '5251' registered

Then, again I make the change to 7439 and it doesn't register.

Feb 11 09:10:29: Requesting restart
Feb 11 09:10:29: INF: ctl: Exit request
Feb 11 09:10:29: INF: mmi: Exit request
Feb 11 09:10:29: INF: sip_manager: Shutting down the SIP stack
Feb 11 09:10:30: INF: Unregistration sent
Feb 11 09:10:30: INF: <sip:5251@172.31.128.19;transport=tcp>: unregistration success
Feb 11 09:10:31: INF: main: exit 1
Feb 11 09:10:31: Need Restart
Feb 11 09:10:35: INF: sip_manager: ua_cfg.nameserver_count = 2
Feb 11 09:10:35: INF: sip_manager: ua_cfg.nameserver[0] = 127.0.0.1
Feb 11 09:10:35: INF: sip_manager: ua_cfg.nameserver[1] = 127.0.0.1
Feb 11 09:10:35: INF: sip_manager: ua_cfg.outbound_proxy_cnt = 0
Feb 11 09:10:35: INF: pjsua version 1.0-trunk for arm-926-linux-gnu initialized
Feb 11 09:10:35: WAR: Failed to send Request msg REGISTER/cseq=28592 (tdta0x328968)! err=120099 (Cannot assign requested address)
Feb 11 09:10:35: WAR: SIP registration failed, status=503 (Service Unavailable)
Feb 11 09:10:35: ERR: Unable to create/send REGISTER: Cannot assign requested address [status=120099]
Feb 11 09:10:35: INF: sip_manager: Setting codec G722, prio 4
Feb 11 09:10:35: INF: sip_manager: Setting codec PCMA, prio 3
Feb 11 09:10:35: INF: sip_manager: Setting codec PCMU, prio 2
Feb 11 09:10:35: INF: sip_manager: Setting codec G729, prio 1

What I've done in System Manager 6.3 --> Elements --> Communication Manager, was to erase the endpoint 7439 and also the user 7439. Then beggining from zero, I duplicated the endpoint from 5251. And then, I duplicated also the user from 5251. But, then again, the B179 is not registering. I even tried using a new B179, but I got the same result. Any idea of what could be missing?

Thanks in advance!
 
b179-settings-sip-7439_fybjad.jpg


This is the same B179, and the only change I make is the DN number 7439 or 5251.

b179-settings-sip-5251_mqeccy.jpg


One is not registering, the other one does.
 
What does a traceSM show? Is your new endpoint configured like the other working endpoints as far as SM profile and CM profile go?
 
Hi kyle555!

The new B179 finally registered. Why? I don't know. I simply stopped trying before the weekend and, when I arrived this morning to the office, the B179 was registered. I knew it was well programmed, but I don't know what happens with the server. I think I will ask AVAYA for some answers. It leaves me kind of confused because, even when I knew I've done everything OK, the new station didn't registered until it wanted. Ha ha! Kind of weird. But thanks for your attention.

Best regards!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top