Difference between revisions of "200 MOR can't determine who is calling"
From Kolmisoft Wiki
Jump to navigationJump to search
| Line 44: | Line 44: | ||
'''Most common reason why people get this error''' | '''Most common reason why people get this error''' | ||
The reason is, that very | The reason is, that very often MOR administrators forget about Trustrpid, Sendrpid, Insecure: port/invite options in device settings window. They must match incoming call settings. The image below shows usually correct settings. | ||
[[Image:note21.png]] | [[Image:note21.png]] | ||
Revision as of 10:37, 26 March 2009
Provider/Device is not authenticated.
- Check settings for Provider/Device
- For provider - make sure hostname and IP address have correct values.
- Both these fields should be filled
- If hostname is not assigned, then it should have IP address - same value as IP address field
- Check port setting.
- Maybe call is coming not through default SIP port 5060, but from 5061? Check it!
- Port is SOURCE port, that means FROM which port call is coming, NOT TO which port is coming.
- If you are using H323 in file h323.conf add UserByAlias=no
- If you are using ZAP/H323 provider - you could forget about accountcode=X setting (More info)
Main reason
You forget to describe IP in MOR from which call comes.
Example:
[Dec 17 08:37:42] WARNING[21726]: app_mor.c:3557 mor_get_user_by_acc: User not found by accountcode: [Dec 17 08:37:42] ERROR[21726]: app_mor.c:667 mor_authorize: MOR can't determine who is calling. Make sure accountcode is set for caller (Provider or Device). [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:692 mor_authorize: Caller type: Local [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:706 mor_authorize: Localized destination: 5143161536 [Dec 17 08:37:42] WARNING[21726]: app_mor.c:711 mor_authorize: This user is BLOCKED!!! [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3872 process_sipchaninfo: ============== SIPCHANINFO =============== [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3897 process_sipchaninfo: Peer IP: 64.34.135.88 [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3898 process_sipchaninfo: Source IP: 64.34.135.88 [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3899 process_sipchaninfo: From: sip:7052058393@64.34.164.254 [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3900 process_sipchaninfo: Contact: sip:7052058393@64.34.164.254 [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3901 process_sipchaninfo: Useragent: Voice Network Inc 1b [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3902 process_sipchaninfo: Peername: [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3903 process_sipchaninfo: T38Passthrough: 0 [Dec 17 08:37:42] NOTICE[21726]: app_mor.c:3907 process_sipchaninfo: ==========================================
That means that MOR does not know about IP 64.34.135.88.
SOLUTION: assign this IP to some Provider (or Device) in MOR.
Most common reason why people get this error
The reason is, that very often MOR administrators forget about Trustrpid, Sendrpid, Insecure: port/invite options in device settings window. They must match incoming call settings. The image below shows usually correct settings.
Related pages:
