DID lenght

This site is best viewed in a modern browser with JavaScript enabled.

enioeltz

Hello

I could successfully run an Issabel free PBX. SIP trunks and extensions has been created and are working.
Later, I have tried to configure Issabel with my Alcatel OXO PBX. I can call from both PBX to any extension at the other side.
But I have realized a situation with Inbound Routes on Issabel. It does not work with DID with more than 4 digits. Issabel extensions have 7 digits long, 0101XXX.
Example 1: Inbound Route with DID 0101001 and destination extension 0101001. In this case, to call from OXO to Issabel, OXO sends an INVITE just with the Issabel extension number, for example 0101001. It does not work.
Then, I have tried another way where I have configured DID with 3 digits long.
Example 2: Inbound Route with DID 001 and destination extension 0101001. In this case, to call from OXO to Issabel, OXO sends an INVITE just with 001. It works.
With these tests, I have realized Issabel is not accepting DID with more than 4 digits.

Does anybody know any configuration to increase DID lenght? For exemple 8 digits.

Thanks in advance.

Enio Eltz Filho.

venturinog

enioeltz Hi, DIDs and extensions are in different contexts, if can call to Issabel extensions then you can't call to Issabel DIDs (without a tweak). What context is defined in issabel trunk?

regards,

enioeltz

Hi venturinog

Thanks for your post.
I understand I do not have context in Issabel trunk. At least in Incoming Configurations of the SIP Trunk. Could you explain where I see it?
I check and post here.

Best regards.

Enio Eltz Filho.

venturinog

enioeltz You have to config the context parameter in trunks, context=from-trunk or context=from-internal for example.

enioeltz

Yes, I was looking for some examples about this and now I can see the context parameter in the SIP trunk is context=from-trunk.
Then I understand there is a context in the SIP trunk. But I am not sure this is the right context to do what I want. I am still looking for information on the web. I found this information at https://wiki.freepbx.org/display/FPG/Trunk+Sample+Configurations

"from-trunk" means that incoming calls from this trunk will be treated as if they are coming from an outside line, and will be routed using the rules that you setup in the Inbound Routes Module. If there is no matching Inbound Route, Asterisk will deliver a "not in service message." "from-pstn-e164-us" is the same as "from-trunk," except that any leading + in the Caller ID will be removed. "from-pstn-toheader" is the same as "from-trunk," but that the called number (the DID) will be derived from the to: header instead of the From-DID header. "from-internal" means that incoming calls from this trunk will be treated as if they were made by an internal phone, and will be routed directly to an extension number, a feature code, or through the outbound routes module."

I am trying to find examples for context=from-pstn-toheader. I think this might be the context I need to use and configure in extensions.conf.

Best regards

Enio Eltz Filho.

enioeltz

I was checking extension.conf where I could find context from-pstn-toheader. I configured it and in the SIP Trunk Peer I configured context=from-pstn-toheader. I also configured an Inbound Route with DID 0101003 and destination extension 0101003. But it did not work yet.

Checking Wireshark traces it seems Issabel rejects the call.
Now I am looking for a command in Issabel to see traces like this:

NOTICE[6659] chan_sip.c: Call from '6125551999' to extension '6125553944' rejected because extension not found in context 'from-pstn-toheader'.

extensions.conf:

[from-pstn-toheader]
exten => .,1,Goto(from-pstn,${CUT(CUT(SIP_HEADER(To),@,1),:,2)},1)
exten => s,1,Goto(from-pstn,${CUT(CUT(SIP_HEADER(To),@,1),:,2)},1)
exten => X.,1,Goto(from-pstn,${CUT(CUT(SIP_HEADER(To),@,1),:,2)},1)

Best regards.

Enio Eltz Filho.

enioeltz

After configuring SIP Trunk Peer context=from-pstn-toheader, as I said I configured an inbound route with DID 0101003 and destination extension 0101003. I did not work.
Then I changed the inbound route to DID 003 and destination extension 0101003. It worked.
Therefore, context from-pstn-toheader is working, but it is still working with just 4 digits at DID field.

Trying to understand the context command, I understand the rule Goto sends to from-pstn, that is the same context I had in the SIP Trunk.

OK, I think I need to change the command a little bit. Let's search again.

Best regards.

Enio Eltz Filho.

enioeltz

I did not find any information about DID limit at 4 digits. I understand Issabel must receive DID with more than 4 digits.
Has anybody already seen this kind of issue?

Best regards.

Enio Eltz Filho.

Alfio

Hi, is so weird, because you can have any DID length in inbound route, if you create an inbound route yo can point it to any extension without problems. In the context [from-pstn-toheader] you hav this error "NOTICE[6659] chan_sip.c: Call from '6125551999' to extension '6125553944' rejected because extension not found in context 'from-pstn-toheader'." because the context "[from-internal](this is the context of all your extensions by default), is not part of the context "from-pstn-toheader".

enioeltz

Hi Alfio

This is just an error I got from internet as an example. It is not from my Issabel. I did not found a way to see this kind of error in my Issabel yet.

Rex

@enioeltz Hi enioeltz solved? I encountered the same problem DID did not work....sad