Howto:Why does the Gateway fail to route an incoming SIP call?: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 11: | Line 11: | ||
Plain telephone number can be roueted and mapped as usual. | Plain telephone number can be roueted and mapped as usual. | ||
<!-- federation error sip local domain Unallocated Unassigned URI --> | <!-- federation error sip local domain Unallocated Unassigned URI hf4 hotfix4 gateway --> | ||
[[Category:Faq|{{PAGENAME}}]] | [[Category:Faq|{{PAGENAME}}]] | ||
Revision as of 12:38, 22 March 2012
Since v9hf4 the Gateway supports federation (call by URI). That's why we do not cut-off domain part of incoming calls automatically. This may result in "Unallocated (unassigned) number" errors. Like this:
LOG CALL 0 No-Route ->:0372806124@10.24.100.218 / GW3::->*:: Cause: Unallocated (unassigned) number
Gateway cuts-off domain part only if domain part matches the local domain. There's a new config option on the gateway interface called "Local Domain". If you enter "10.24.100.218" here, called URI is truncated into "0372806124" (plain telephone number). Plain telephone number can be roueted and mapped as usual.